Moving Rafael from Cc to To.
Hi Rafael,
can you please help here?
I need your ACK or NACK for this patch.
On Fri, May 04, 2018 at 01:49:56PM -0700, Andrew Morton wrote:
> On Fri, 4 May 2018 20:50:52 +0200 Oleksij Rempel
> wrote:
>
> > Hallo Andrew,
> > I need your
Hi Maxime,
On Thu, 3 May 2018 16:33:19 +0200
Maxime Ripard wrote:
> > +struct sun4i_codec_quirks {
> > + const struct regmap_config *regmap_config;
> > + const struct snd_soc_component_driver *codec;
> > + struct snd_soc_card * (*create_card)(struct device
In _ctl_ioctl_main(), 'ioctl_header' is first copied from the userspace
pointer 'arg'. 'ioctl_header.ioc_number' is then verified by
_ctl_verify_adapter(). If the verification is failed, an error code -ENODEV
is returned. Otherwise, the verification result, i.e., the MPT3SAS adapter
that matches
Hi Maxime,
On Thu, 3 May 2018 16:46:19 +0200
Maxime Ripard wrote:
> Doesn't that mean that the controls will be shared between the right
> and left mixers now, which wasn't the case before?
Yes. However Chen-Yu said that except for debugfs that cannot be
observed by
* Sebastian Andrzej Siewior wrote:
> On 2018-05-04 20:51:32 [+0200], Peter Zijlstra wrote:
> > On Fri, May 04, 2018 at 08:45:39PM +0200, Sebastian Andrzej Siewior wrote:
> > > On 2018-05-04 20:32:49 [+0200], Peter Zijlstra wrote:
> > > > On Fri, May 04, 2018 at 07:51:44PM
On Fri, May 04, 2018 at 09:18:41AM +0200, 'Antoine Tenart' wrote:
>
> In this driver we need to perform in certain cases an invalidation,
> which is done thanks to invalidation requests. To do this we create
> dummy requests, using SKCIPHER_REQUEST_ON_STACK and
> AHASH_REQUEST_ON_STACK for ciphers
]
url:
https://github.com/0day-ci/linux/commits/zhangq95/Add-a-file-named-cgroup-procs_stat-in-cgroup/20180505-115518
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>
From: Nick Milner
There are several typos, references to non existent files, grammar and
punctuation mistakes in the rk3399_dmc.txt binding. This patch tries
to improve the binding documentation and fix these mistakes.
Signed-off-by: Nick Milner
On Sat, May 05, 2018 at 11:47:53AM +0200, Jörg Otte wrote:
> Patch doesn't hurt me. For me it´s ok.
>
> Thanks, Jörg
Good, thanks for testing!
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
* Ingo Molnar wrote:
> If that's too then there's a few more things we could do - for example the
^--too much
> attached patch renames a (very minor) misnomer to a shorter name and thus
> saves on
> the longest lines, the column histogram now looks like this:
According to current implementation of acpi_pad driver,
it does not make sense to spawn any power saving threads
on the cpus which are already idle - it might bring
unnecessary overhead on these idle cpus and causes power
waste. So verify the condition that if the number of 'busy'
cpus exceeds the
If various stall reports regarding loop_set_fd() are hitting below sequence, a
patch
was proposed at
https://groups.google.com/d/msg/syzkaller-bugs/5pzXJ8yQFR0/vWeRytaQBAAJ .
--
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
const int fd =
In i2c_smbus_xfer_emulated(), the function i2c_transfer() is invoked to
transfer i2c messages. The number of actual transferred messages is
returned and saved to 'status'. If 'status' is negative, that means an
error occurred during the transfer process. In that case, the value of
'status' is an
Christoph Hellwig writes:
> The driver proc file hasn't been writeable for a long time, so this is
> just dead code.
It is possible to chmod this file to get at the write method. Not that
I think anyone does.
It looks like this code was merged in 2.3.99-pre1 with permissions
No, your fix is in next, but needs to go to Linus via the fixes branch. I have
2 to send on to him. I am traveling and was planning to do it this weekend.
On May 4, 2018 8:27:00 PM GMT+02:00, mario.limoncie...@dell.com wrote:
>Darren,
>
>Is this with that fix of mine merged?
>
>> -Original
://github.com/0day-ci/linux/commits/zhangq95/Add-a-file-named-cgroup-procs_stat-in-cgroup/20180505-115518
config: i386-randconfig-x076-201817 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors
On Mon, Apr 23, 2018 at 08:25:13AM +0100, Gilad Ben-Yossef wrote:
> Small cleanup and add support for CryptoCell hardware keys.
>
> Changes from v1:
> - The cleanup patch is new, as Herbert took the previous one :-)
> - Hardware key API uses the "paes" designator to indicate a protected key,
>
://github.com/0day-ci/linux/commits/zhangq95/Add-a-file-named-cgroup-procs_stat-in-cgroup/20180505-115518
config: i386-randconfig-x014-201817 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All error
Hi Maxime,
I love your patch! Perhaps something to improve:
[auto build test WARNING on ]
url:
https://github.com/0day-ci/linux/commits/Maxime-Ripard/drm-panel-Add-Ilitek-ILI9881c-controller-driver/20180505-104031
base:
reproduce:
# apt-get install sparse
make ARCH
Hi lkp,
Thanks for your advise. I will improve in next version.
Best Regards,
卢小通 Xiaotong Lu
CPSD Dept.
Unigroup Spreadtrum Technologies Co.,Ltd.
Tel: 86-21-20360600 Ext. 2496
Fax: 86-21-20360700
E-mail: xiaotong...@unisoc.com
Http://www.spreadtrum.com
-Original Message-
From:
On Thu, Apr 26, 2018 at 07:57:28PM -0700, Kees Cook wrote:
> In the quest to remove all stack VLA usage from the kernel[1], this
> allocates the return code buffers before starting jiffie timers, rather
> than using stack space for the array. Additionally cleans up some exit
> paths and make sure
Hi Maxime,
I love your patch! Yet something to improve:
[auto build test ERROR on ]
url:
https://github.com/0day-ci/linux/commits/Maxime-Ripard/drm-panel-Add-Ilitek-ILI9881c-controller-driver/20180505-104031
base:
config: arm-at91_dt_defconfig (attached as .config)
compiler: arm-linux
On Fri, Apr 27, 2018 at 07:08:05PM +0100, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in module description text
>
> Signed-off-by: Colin Ian King
Patch applied. Thanks.
--
Email: Herbert Xu
In the quest to remove VLAs from the kernel[1], this moves the
allocation of coefs and blocks from the stack to being kmalloc()ed.
[1] https://lkml.org/lkml/2018/3/7/621
Signed-off-by: Kyle Spiers
---
Forgot to add slab.h
---
crypto/async_tx/async_pq.c | 18
On Fri, May 04, 2018 at 10:01:44AM -0500, Kangjie Lu wrote:
> > There is nothing preventing the user from using struct lov_mds_md_v3 but
> > filling in lmm_magic = LOV_MAGIC_V1 from the beginning, no need for a race.
> >
>
> Right. No need for users to race. There might be a type confusion issue
Hello!
On 5/4/2018 10:05 PM, Mylène Josserand wrote:
From: Doug Berger
The constants defined in this file are equally useful in assembly and C
source files. The arm64 architecture version of this file allows
inclusion in both assembly and C source files, so this this
The values are extraced from the "AM335x SitaraTM Processors Technical
Reference Manual", Section 9.3.1 CONTROL_MODULE Registers, based on the
file autogenerated by TI PinMux.
The register conf_rtc_kaldo_enn was removed from the Control Module
Registers table with Revision M.
Signed-off-by:
This patchset replaces the register offsets for am335x with macro defines.
The values are extraced from the "AM335x SitaraTM Processors Technical
Reference Manual".
The TRM lists AM3351, AM3352, AM3354, AM3356, AM3357, AM3358 and AM3359 on page
173.
So I would assume the registers are the same
On Fri, May 04, 2018 at 08:24:22PM +0200, Peter Zijlstra wrote:
> On Fri, May 04, 2018 at 07:09:09PM +0100, Mark Rutland wrote:
> > On Fri, May 04, 2018 at 08:01:05PM +0200, Peter Zijlstra wrote:
> > > On Fri, May 04, 2018 at 06:39:32PM +0100, Mark Rutland wrote:
>
> > > >
On Fri, May 04, 2018 at 01:54:14PM +1000, NeilBrown wrote:
> This "feature" is unused, undocumented, and untested and so
> doesn't really belong. If a use for the nulls marker
> is found, all this code would need to be reviewed to
> ensure it works as required. It would be just as easy to
> just
On Fri, May 04, 2018 at 01:54:14PM +1000, NeilBrown wrote:
> This function has a somewhat confused behavior that is not properly
> described by the documentation.
> Sometimes is returns the previous object, sometimes it returns the
> next one.
> Sometimes it changes the iterator, sometimes it
* Ingo Molnar wrote:
> * Peter Zijlstra wrote:
>
> > > So we could do the following simplification on top of that:
> > >
> > > #ifndef atomic_fetch_dec_relaxed
> > > # ifndef atomic_fetch_dec
> > > # define atomic_fetch_dec(v)
Hi Greg,
On 05/04/2018 11:15 PM, Greg KH wrote:
On Tue, May 01, 2018 at 11:26:04AM +0100, Suzuki K Poulose wrote:
commit ece1397cbc89c51914fae1aec729539cfd8bd62b upstream
...
Note: The upstream commit is on top of a reworked capability
infrastructure for arm64 heterogeneous systems,
Thread AThread BThread C
- f2fs_remount
- stop_gc_thread
- f2fs_sbi_store
- issue_discard_thread
sbi->gc_thread = NULL;
Introduce GC_I to replace sbi->gc_thread for cleanup, no logic changes.
Signed-off-by: Chao Yu
---
fs/f2fs/debug.c | 2 +-
fs/f2fs/f2fs.h| 5 +
fs/f2fs/gc.c | 14 +++---
fs/f2fs/segment.c | 4 ++--
fs/f2fs/super.c | 4 ++--
fs/f2fs/sysfs.c | 8
/linux/commits/Wenwen-Wang/i2c-core-smbus-fix-a-potential-uninitialization-bug/20180505-164208
base: https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git
i2c/for-next
config: x86_64-randconfig-x013-201817 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce
Christoph Hellwig writes:
> The shole seq_file sequence already operates under a single RCU lock pair,
> so move the pid namespace lookup into it, and stop grabbing a reference
> and remove all kinds of boilerplate code.
This is wrong.
Move task_active_pid_ns(current) from open to
Christoph Hellwig writes:
> Use remove_proc_subtree to remove the whole subtree on cleanup, and
> unwind the registration loop into individual calls. Switch to use
> proc_create_seq where applicable.
Can you please explain why you are removing the error handling when
you are
On 2018-04-26 16:08, Michal Simek wrote:
Hi,
this series is trying to address discussion I had with Alan in past
https://patchwork.kernel.org/patch/9738445/.
It is moving uart_register_driver() to probe function like it is done
in
pl011 driver.
And also introducing new function for alias
On Sat, May 05, 2018 at 03:27:51PM +0200, Ingo Molnar wrote:
>
> * Boqun Feng wrote:
>
> > > May I suggest the patch below? No change in functionality, but it
> > > documents the
> > > lack of the cmpxchg_release() APIs and maps them explicitly to the full
> > >
Hi Lorenzo,
On 05/04/2018 07:44 PM, Lorenzo Pieralisi wrote:
> On Thu, May 03, 2018 at 10:18:24AM +0300, Vladimir Zapolskiy wrote:
>> Hi Jan,
>>
>> On 04/30/2018 08:48 AM, Jan Kiszka wrote:
>>> From: Jan Kiszka
>>>
>>> Straightforward for all of them, no more leaks
* Mark Rutland wrote:
> On Fri, May 04, 2018 at 08:01:05PM +0200, Peter Zijlstra wrote:
> > On Fri, May 04, 2018 at 06:39:32PM +0100, Mark Rutland wrote:
> > > Currently only instruments the fully
> > > ordered variants of atomic functions, ignoring the
> > >
* Ingo Molnar wrote:
> Before:
>
> #ifndef atomic_fetch_dec_relaxed
>
> #ifndef atomic_fetch_dec
> #define atomic_fetch_dec(v) atomic_fetch_sub(1, (v))
> #define atomic_fetch_dec_relaxed(v) atomic_fetch_sub_relaxed(1, (v))
> #define atomic_fetch_dec_acquire(v)
On 2018-05-05 01:44, Wanpeng Li wrote:
> ping,
> 2018-05-01 7:35 GMT+08:00 Wanpeng Li :
>> From: Wanpeng Li
>>
>> Anthoine reported:
>> The period used by Windows change over time but it can be 1 milliseconds
>> or less. I saw the
* Ingo Molnar wrote:
> Note that the simplest definition block is now:
>
> #ifndef atomic_cmpxchg_relaxed
> # define atomic_cmpxchg_relaxed atomic_cmpxchg
> # define atomic_cmpxchg_acquire atomic_cmpxchg
> # define
On Sat, May 05, 2018 at 11:09:03AM +0200, Ingo Molnar wrote:
> > > # ifndef atomic_fetch_dec_acquire
> > > # define atomic_fetch_dec_acquire(...)
> > > __atomic_op_acquire(atomic_fetch_dec, __VA_ARGS__)
> > > # endif
> > > # ifndef atomic_fetch_dec_release
> > > # define
On Fri, May 04, 2018 at 01:54:14PM +1000, NeilBrown wrote:
> Rather than borrowing one of the bucket locks to
> protect ->future_tbl updates, use cmpxchg().
> This gives more freedom to change how bucket locking
> is implemented.
>
> Signed-off-by: NeilBrown
This looks nice.
>
On Fri, May 04, 2018 at 01:54:14PM +1000, NeilBrown wrote:
> If two threads run nested_table_alloc() at the same time
> they could both allocate a new table.
> Best case is that one of them will never be freed, leaking memory.
> Worst case is hat entry get stored there before it leaks,
> and the
On Fri, May 04, 2018 at 01:54:14PM +1000, NeilBrown wrote:
> rhashtable_try_insert() currently hold a lock on the bucket in
> the first table, while also locking buckets in subsequent tables.
> This is unnecessary and looks like a hold-over from some earlier
> version of the implementation.
>
>
On Fri, May 04, 2018 at 01:54:14PM +1000, NeilBrown wrote:
> rhashtable_walk_prev() returns the object returned by
> the previous rhashtable_walk_next(), providing it is still in the
> table (or was during this grace period).
> This works even if rhashtable_walk_stop() and rhashtable_talk_start()
/linux/commits/Wenwen-Wang/i2c-core-smbus-fix-a-potential-uninitialization-bug/20180505-164208
base: https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git
i2c/for-next
config: i386-randconfig-a0-201817 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
# save
Hi.
CONFIG_HAVE_UNDERSCORE_SYMBOL_PREFIX was selected
by BLACKFIN and METAG.
Now that both architectures removed in the previous
merge window, there is no more user of this CONFIG option.
My question is,
is it OK to remove CONFIG_HAVE_UNDERSCORE_SYMBOL_PREFIX entirely?
In other words,
-
* Boqun Feng wrote:
> On Sat, May 05, 2018 at 11:38:29AM +0200, Ingo Molnar wrote:
> >
> > * Ingo Molnar wrote:
> >
> > > * Peter Zijlstra wrote:
> > >
> > > > > So we could do the following simplification on top of that:
> > >
2018-03-13 21:06 GMT+01:00 Florian Fainelli :
> On 03/13/2018 12:58 PM, Vivien Didelot wrote:
>> Hi Salvatore,
>>
>> Salvatore Mesoraca writes:
>>
>>> dsa_switch's num_ports is currently fixed to DSA_MAX_PORTS. So we avoid
>>> 2 VLAs[1] by using
2018-04-27 6:41 GMT+09:00 Nick Desaulniers :
> Hi Masahiro and Michal,
>
> The reporter has asked for their email address to be updated to:
>
> psoda...@codeaurora.org
>
> if you're ok with this version of the patch and choose to apply it, can you
> please update the
On Fri, May 04, 2018 at 04:08:42PM +0800, Chen Yu wrote:
> According to current implementation of acpi_pad driver,
> it does not make sense to spawn any power saving threads
> on the cpus which are already idle - it might bring
> unnecessary overhead on these idle cpus and causes power
> waste. So
In i2c_smbus_xfer_emulated(), there are two buffers: msgbuf0 and msgbuf1,
which are used to save a series of messages, as mentioned in the comment.
According to the value of the variable 'size', msgbuf0 is initialized to
various values. In contrast, msgbuf1 is left uninitialized until the
function
On Fri, Apr 27, 2018 at 11:40:11AM +0300, Horia Geantă wrote:
> Fix a typo where size of RSA prime factor q is using the size of
> prime factor p.
>
> Cc: # 4.13+
> Fixes: 52e26d77b8b3 ("crypto: caam - add support for RSA key form 2")
> Fixes: 4a651b122adb ("crypto: caam
On Mon, Apr 23, 2018 at 05:04:24PM +0200, Lionel Debieve wrote:
> This series are fixing the default build state for stm32-rng that
> activate the driver with arm multi_v7_defconfig.
> Second patch is fixing the power suspend/resume behavior which was
> not working.
>
> Lionel Debieve (2):
>
> @@ -656,18 +656,18 @@ static int dvb_dmxdev_start_feed(struct dmxdev *dmxdev,
> tsfeed->priv = filter;
>
> ret = tsfeed->set(tsfeed, feed->pid, ts_type, ts_pes, timeout);
> - if (ret < 0) {
> - dmxdev->demux->release_ts_feed(dmxdev->demux, tsfeed);
> -
i.MX6SX Sabre Auto board has GPIO1_IO13 pin can be
MUXed as WDOG output to reset PMIC, add this function
support.
Signed-off-by: Anson Huang
---
arch/arm/boot/dts/imx6sx-sabreauto.dts | 12
1 file changed, 12 insertions(+)
diff --git
i.MX6SX Sabre Auto board has two max7310 IO expander on I2C3 bus, add
support for them.
Signed-off-by: Dong Aisheng
Signed-off-by: Anson Huang
---
changes since V5:
improve pinctrl node name.
arch/arm/boot/dts/imx6sx-sabreauto.dts | 28
Hi Mark,
> > And maybe this could be used here, too? Introduce this flag for very
> > late/early messages. If they have it, messages are even sent in
> > suspend_noirq() phase with the master_xfer_irqless() callback, otherwise
> > we will have the WARNing printed out.
>
> It feels like it'd be
There is a debug LED(D11) connected to GPIO1_IO24,
add support for it.
Signed-off-by: Anson Huang
---
arch/arm/boot/dts/imx6sx-sabreauto.dts | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts
Add FEC support on i.MX6SX Sabre Auto board.
Signed-off-by: Fugang Duan
Signed-off-by: Anson Huang
---
changes since V5:
use "gpios" instead of "enable-gpio".
arch/arm/boot/dts/imx6sx-sabreauto.dts | 80 ++
1
Add pfuze100 support on i.MX6SX Sabre Auto board.
Signed-off-by: Robin Gong
Signed-off-by: Anson Huang
---
changes since V5:
improve node name and unit-address format.
arch/arm/boot/dts/imx6sx-sabreauto.dts | 116
Add MAX7322 IO expander support.
Signed-off-by: Fugang Duan
Signed-off-by: Anson Huang
---
arch/arm/boot/dts/imx6sx-sabreauto.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts
Add egalax touch screen support on i2c2 bus.
Signed-off-by: Haibo Chen
Signed-off-by: Anson Huang
---
changes since V5:
improve pinctrl node name and touchscreen node name.
arch/arm/boot/dts/imx6sx-sabreauto.dts | 16
1
On Sat, May 5, 2018 at 10:47 AM, Peter Zijlstra wrote:
> On Sat, May 05, 2018 at 10:11:00AM +0200, Ingo Molnar wrote:
>
>> Before:
>>
>> #ifndef atomic_fetch_dec_relaxed
>>
>> #ifndef atomic_fetch_dec
>> #define atomic_fetch_dec(v) atomic_fetch_sub(1, (v))
>>
* Peter Zijlstra wrote:
> > So we could do the following simplification on top of that:
> >
> > #ifndef atomic_fetch_dec_relaxed
> > # ifndef atomic_fetch_dec
> > # define atomic_fetch_dec(v) atomic_fetch_sub(1, (v))
> > # define
On Sat, May 05, 2018 at 11:05:51AM +0200, Dmitry Vyukov wrote:
> On Sat, May 5, 2018 at 10:47 AM, Peter Zijlstra wrote:
> > And I seriously hate this one:
> >
> > ba1c9f83f633 ("locking/atomic/x86: Un-macro-ify atomic ops
> > implementation")
> >
> > and will likely undo
On Friday 04 May 2018 09:59 PM, Lorenzo Pieralisi wrote:
> On Tue, Apr 10, 2018 at 09:04:06PM +0800, Jia-Ju Bai wrote:
>> pci_epf_test_write() is never called in atomic context.
>>
>> The call chain ending up at pci_epf_test_write() is:
>> [1] pci_epf_test_write() <- pci_epf_test_cmd_handler()
On 05/03/2018 09:25 PM, Mathieu Poirier wrote:
On 3 May 2018 at 11:31, Mathieu Poirier wrote:
On Tue, May 01, 2018 at 10:10:34AM +0100, Suzuki K Poulose wrote:
Add the initial support for Coresight Address Translation Unit, which
augments the TMC in Coresight
i_current_depth is used only for directory inode, but its space is
shared with i_gc_failures field used for regular inode, in order to
avoid affecting i_gc_failures' value, this patch fixes to initialize
the union's fields according to inode type.
Signed-off-by: Chao Yu
---
f2fs doesn't allow abuse on atomic write class interface, so except
limiting in-mem pages' total memory usage capacity, we need to limit
atomic-write usage as well when filesystem is seriously fragmented,
otherwise we may run into infinite loop during foreground GC because
target blocks in victim
* Peter Zijlstra wrote:
> On Sat, May 05, 2018 at 11:09:03AM +0200, Ingo Molnar wrote:
> > > > # ifndef atomic_fetch_dec_acquire
> > > > # define atomic_fetch_dec_acquire(...)
> > > > __atomic_op_acquire(atomic_fetch_dec, __VA_ARGS__)
> > > > # endif
> > > > #
On Thu, Apr 26, 2018 at 7:19 PM, Phil Edworthy
wrote:
Sotty fo a late response. Consider follow up fixes for below.
> if (!pp->irq_shared) {
> + int i;
> +
> + for (i = 0; i < pp->ngpio; i++) {
> + if
From: Wanpeng Li
Anthoine reported:
The period used by Windows change over time but it can be 1
milliseconds or less. I saw the limit_periodic_timer_frequency
print so 500 microseconds is sometimes reached.
As suggested by Paolo, lower the default timer frequency
2018-05-05 16:36 GMT+08:00 Jan Kiszka :
> On 2018-05-05 01:44, Wanpeng Li wrote:
>> ping,
>> 2018-05-01 7:35 GMT+08:00 Wanpeng Li :
>>> From: Wanpeng Li
>>>
>>> Anthoine reported:
>>> The period used by Windows change over time but
On Sat, May 05, 2018 at 12:35:50PM +0200, Ingo Molnar wrote:
>
> * Boqun Feng wrote:
>
> > On Sat, May 05, 2018 at 11:38:29AM +0200, Ingo Molnar wrote:
> > >
> > > * Ingo Molnar wrote:
> > >
> > > > * Peter Zijlstra wrote:
> > >
On Sat, May 5, 2018 at 5:28 AM, Peter Rosin wrote:
> On 2018-05-05 03:43, Wenwen Wang wrote:
>> In i2c_smbus_xfer_emulated(), there are two buffers: msgbuf0 and msgbuf1,
>> which are used to save a series of messages, as mentioned in the comment.
>> According to the value of the
Hi,
will there be an announcement that Linux 3.2 is EOL or will there be
another release which announces it as the last release of this stable
series? The kernel release page
https://www.kernel.org/category/releases.html lists it as EOL for this
month.
Charlemagne
On Fri, 2018-05-04 at 21:46 +0200, Mike Galbraith wrote:
> Tentatively, I suspect you've just fixed the nasty stalls I reported a
> while back.
Oh well, so much for optimism. It took a lot, but just hung.
On Sat, May 05, 2018 at 10:11:00AM +0200, Ingo Molnar wrote:
> Before:
>
> #ifndef atomic_fetch_dec_relaxed
>
> #ifndef atomic_fetch_dec
> #define atomic_fetch_dec(v) atomic_fetch_sub(1, (v))
> #define atomic_fetch_dec_relaxed(v) atomic_fetch_sub_relaxed(1, (v))
> #define
On Fri, May 04, 2018 at 01:54:14PM +1000, NeilBrown wrote:
> print_ht in rhashtable_test calls rht_dereference() with neither
> RCU protection or the mutex. This triggers an RCU warning.
> So take the mutex to silence the warning.
>
> Signed-off-by: NeilBrown
I don't think the
On Sat, May 05, 2018 at 11:04:03AM +0200, Ingo Molnar wrote:
>
> * Peter Zijlstra wrote:
>
> > > So we could do the following simplification on top of that:
> > >
> > > #ifndef atomic_fetch_dec_relaxed
> > > # ifndef atomic_fetch_dec
> > > # define atomic_fetch_dec(v)
DDR3 SDRAM Standard (JESD79-3F) defines some standard speed bins for
DDR3 memories. The rk3399_dmc driver allows you to pass these values via
the device tree. For that purpose the devfreq/rk3399_dmc.txt binding
refers to a ddr.h file which does not exist. This patch adds the missing
defines in a
In ATF we already wait for DDR DVFS finish, so move the interrupts properties
to be optional.
Signed-off-by: Enric Balletbo i Serra
Reviewed-by: Chanwoo Choi
---
Changes in v3:
- [4/6] Move interrupts to be optional instead of remove.
Dear all,
These patches is an attempt to improve a little bit the rk3399_dmc
driver and it's documentation in order to have all in a better shape for
a future work I am doing. My final intention is add ddrfreq support for
rockchip drm driver, but the patches for this are still
work-in-progress.
From: Lin Huang
We just return -EPROBE_DEFER error code to caller and do not
print error message when try to get center logic regulator
and DMC clock defer.
Signed-off-by: Lin Huang
Signed-off-by: Enric Balletbo i Serra
We have already wait dcf done in ATF, so don't need wait dcf irq
in kernel, besides, clear dcf irq in kernel will import competiton
between kernel and ATF, only handle dcf irq in ATF is a better way.
Signed-off-by: Lin Huang
Signed-off-by: Enric Balletbo i Serra
2018-05-04 18:18 GMT+02:00 Borislav Petkov :
> On Wed, May 02, 2018 at 02:20:52PM +0200, Thomas Gleixner wrote:
>> Thanks for confirming. Still need to find a way which is less fragile, but
>> that's probably too much of churn for rc4
>>
>> At least I know exactly what's
* Ingo Molnar wrote:
> > So there's no loss in arch flexibility.
>
> BTW., PowerPC for example is already in such a situation, it does not define
> atomic_cmpxchg_release(), only the other APIs:
>
> #define atomic_cmpxchg(v, o, n) (cmpxchg(&((v)->counter), (o), (n)))
>
Hi Ingo,
On Sat, May 05, 2018 at 12:00:55PM +0200, Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
> > > So there's no loss in arch flexibility.
> >
> > BTW., PowerPC for example is already in such a situation, it does not
> > define
> > atomic_cmpxchg_release(), only the
Hi Anson,
On Sat, May 5, 2018 at 5:29 AM, Anson Huang wrote:
> Add egalax touch screen support on i2c2 bus.
>
> Signed-off-by: Haibo Chen
Is Haibo the author of this patch? If so, his name should appear in
the From field.
> Signed-off-by: Anson
Christoph,
I bisected the following kernel panic to the patch "PCI: Remove NULL
device handling from PCI DMA API". It seems we
still need NULL checking for some older drivers, in my case the 3c59x
driver for PCI/EISA cards.
I am pretty sure the panic arises in the driver here
* Boqun Feng wrote:
> > May I suggest the patch below? No change in functionality, but it documents
> > the
> > lack of the cmpxchg_release() APIs and maps them explicitly to the full
> > cmpxchg()
> > version. (Which the generic code does now in a rather roundabout
Em Thu, 19 Apr 2018 22:00:07 +0200
Wolfram Sang escreveu:
> This header only contains platform_data. Move it to the proper directory.
>
> Signed-off-by: Wolfram Sang
> ---
> MAINTAINERS | 2 +-
>
On 5/4/18 9:51 PM, Matthew Wilcox wrote:
> On Fri, May 04, 2018 at 04:22:16PM -0700, Andrew Morton wrote:
>> I'm feeling a bit hostile toward lib/percpu_ida.c in general ;) It has
>> very few users and seems rather complicated (what's with that
>> schedule() in percpu_ida_alloc?). I'm suspecting
Masami Hiramatsu wrote:
On Fri, 4 May 2018 12:06:42 -0400
Steven Rostedt wrote:
On Sat, 5 May 2018 00:48:28 +0900
Masami Hiramatsu wrote:
> > Also, when looking at the kprobe code, I was looking at this
> > function:
> >
> > > /* Ftrace callback
1 - 100 of 462 matches
Mail list logo