Re: [PATCH] dmaengine: omap-dma: Enable burst and data pack for SG

On Fri, Sep 16, 2016 at 01:53:15PM +0300, Peter Ujfalusi wrote: > From: Misael Lopez Cruz > > Enable the burst and data pack modes for the scatter-gather > in order to improve the throughput of the data transfers. > > The improvement has been verified with MMC HS200 mode in

Re: [PATCH] dmaengine: omap-dma: Enable burst and data pack for SG

On Fri, Sep 16, 2016 at 01:53:15PM +0300, Peter Ujfalusi wrote: > From: Misael Lopez Cruz > > Enable the burst and data pack modes for the scatter-gather > in order to improve the throughput of the data transfers. > > The improvement has been verified with MMC HS200 mode in > the DRA72 EVM

Re: [PATCH] perf sched: kill time stamp discrepancy between script and latency

Hi Joonwoo, On Wed, Sep 28, 2016 at 07:25:26PM -0700, Joonwoo Park wrote: > Perf sched latency is handy to find out the maximum sched latency and > the time stamp of the event. After running sched latency, if a found > latency looks suspicious it's quite reasonable to run perf script >

Re: [PATCH] perf sched: kill time stamp discrepancy between script and latency

Hi Joonwoo, On Wed, Sep 28, 2016 at 07:25:26PM -0700, Joonwoo Park wrote: > Perf sched latency is handy to find out the maximum sched latency and > the time stamp of the event. After running sched latency, if a found > latency looks suspicious it's quite reasonable to run perf script >

Re: [PATCH RESEND] perf diff: Introduce the new rules of colored printing of delta.

Hi SeongSoo, On Fri, Sep 30, 2016 at 8:44 AM, SeongSoo Cho wrote: > As you know, there are the common colored printing of percents so overhead(%) > can be colored with the rule. > But Delta means difference percents from percents of overhead between two > files e.g.

Re: [PATCH RESEND] perf diff: Introduce the new rules of colored printing of delta.

Hi SeongSoo, On Fri, Sep 30, 2016 at 8:44 AM, SeongSoo Cho wrote: > As you know, there are the common colored printing of percents so overhead(%) > can be colored with the rule. > But Delta means difference percents from percents of overhead between two > files e.g. perf.data and

[PATCH] power: bq27xxx_battery: don't update poll_interval param if same

To avoid canceling the delayed workqueue needlessly, and scheduling an immediate polling. Check if the new poll_interval value is different than the previous setting. Cc: Tony Lindgren Cc: Sebastian Reichel Signed-off-by: Matt Ranostay

[PATCH] power: bq27xxx_battery: don't update poll_interval param if same

To avoid canceling the delayed workqueue needlessly, and scheduling an immediate polling. Check if the new poll_interval value is different than the previous setting. Cc: Tony Lindgren Cc: Sebastian Reichel Signed-off-by: Matt Ranostay --- drivers/power/supply/bq27xxx_battery.c | 3 ++- 1

[PATCH v4 2/2] Dcumentation/filesystems/proc.txt: Add more description for maps/smaps

Add some more description on the limitations for smaps/maps readings, as well as some guaruntees we can make. Changelog: v2: Adopt Dave Hansen's revision from v1 as the description. Signed-off-by: Robert Ho --- Documentation/filesystems/proc.txt | 12

[PATCH v4 1/2] mm, proc: Fix region lost in /proc/self/smaps

Recently, Redhat reported that nvml test suite failed on QEMU/KVM, more detailed info please refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1365721 Actually, this bug is not only for NVDIMM/DAX but also for any other file systems. This simple test case abstracted from nvml can easily

[PATCH v4 2/2] Dcumentation/filesystems/proc.txt: Add more description for maps/smaps

Add some more description on the limitations for smaps/maps readings, as well as some guaruntees we can make. Changelog: v2: Adopt Dave Hansen's revision from v1 as the description. Signed-off-by: Robert Ho --- Documentation/filesystems/proc.txt | 12 1 file changed, 12

[PATCH v4 1/2] mm, proc: Fix region lost in /proc/self/smaps

Recently, Redhat reported that nvml test suite failed on QEMU/KVM, more detailed info please refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1365721 Actually, this bug is not only for NVDIMM/DAX but also for any other file systems. This simple test case abstracted from nvml can easily

Re: [PATCH 1/3] proc: Stop reporting eip and esp in /proc/PID/stat

On Fri, Sep 30, 2016 at 7:01 PM, Andy Lutomirski wrote: > > Peter, how nasty would it be to add some lightish-weight lock that > lets us pin a task in a non-running state? Maybe we could take the rq > lock, do something to the task to make it sleepy (steal it off the >

Re: [PATCH 1/3] proc: Stop reporting eip and esp in /proc/PID/stat

On Fri, Sep 30, 2016 at 7:01 PM, Andy Lutomirski wrote: > > Peter, how nasty would it be to add some lightish-weight lock that > lets us pin a task in a non-running state? Maybe we could take the rq > lock, do something to the task to make it sleepy (steal it off the > queue?), unlock the lock,

Re: [RFC PATCH v1 2/2] printk: external log buffer (CONFIG_LOGBUFFER)

On 9/30/2016 7:39 AM, Petr Mladek wrote: > On Thu 2016-09-29 19:55:56, Sean Hudson wrote: >> This debug feature provides a convenient way to collect log entries across >> multiple, warmboot cycles and to share those entries with a boot loader. >> It allows the kernel to use an external buffer for

Re: [RFC PATCH v1 2/2] printk: external log buffer (CONFIG_LOGBUFFER)

On 9/30/2016 7:39 AM, Petr Mladek wrote: > On Thu 2016-09-29 19:55:56, Sean Hudson wrote: >> This debug feature provides a convenient way to collect log entries across >> multiple, warmboot cycles and to share those entries with a boot loader. >> It allows the kernel to use an external buffer for

[PATCH] md/dm-stats: Use kmalloc_array() in parse_histogram()

From: Markus Elfring Date: Sat, 1 Oct 2016 05:55:05 +0200 * A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was

[PATCH] md/dm-stats: Use kmalloc_array() in parse_histogram()

From: Markus Elfring Date: Sat, 1 Oct 2016 05:55:05 +0200 * A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was detected by using the Coccinelle

[PATCH v2 1/2] Input: synaptics-rmi4 - Fix error handling in I2C transport driver

Instantiating the rmi4 I2C transport driver without interrupts assigned (for example using manual i2c instantiation from the command line) caused the driver to fail to load, but it does not clean up its regulator or transport device registrations. Result is a crash at a later time, for example

[PATCH v2 2/2] Input: synaptics-rmi4 - Fix error handling in SPI transport driver

Instantiating the rmi4 SPI transport driver without an interrupt assigned caused the driver to fail to load, but it does not clean up its transport device registration. Result may be a crash at a later time, for example when rebooting the system. Fixes: 8d99758dee31 ("Input: synaptics-rmi4 - add

[PATCH v2 1/2] Input: synaptics-rmi4 - Fix error handling in I2C transport driver

Instantiating the rmi4 I2C transport driver without interrupts assigned (for example using manual i2c instantiation from the command line) caused the driver to fail to load, but it does not clean up its regulator or transport device registrations. Result is a crash at a later time, for example

[PATCH v2 2/2] Input: synaptics-rmi4 - Fix error handling in SPI transport driver

Instantiating the rmi4 SPI transport driver without an interrupt assigned caused the driver to fail to load, but it does not clean up its transport device registration. Result may be a crash at a later time, for example when rebooting the system. Fixes: 8d99758dee31 ("Input: synaptics-rmi4 - add

Re: [PATCH] Input: synaptics-rmi4 - Fix error handling in I2C transport driver

On 09/30/2016 04:02 PM, Dmitry Torokhov wrote: On Fri, Sep 30, 2016 at 03:54:03PM -0700, Dmitry Torokhov wrote: On Thu, Sep 29, 2016 at 10:55:40AM -0700, Bjorn Andersson wrote: On Wed 28 Sep 17:37 PDT 2016, Guenter Roeck wrote: Instantiating the rmi4 I2C transport driver without interrupts

Re: [PATCH] Input: synaptics-rmi4 - Fix error handling in I2C transport driver

On 09/30/2016 04:02 PM, Dmitry Torokhov wrote: On Fri, Sep 30, 2016 at 03:54:03PM -0700, Dmitry Torokhov wrote: On Thu, Sep 29, 2016 at 10:55:40AM -0700, Bjorn Andersson wrote: On Wed 28 Sep 17:37 PDT 2016, Guenter Roeck wrote: Instantiating the rmi4 I2C transport driver without interrupts

Re: [PATCH 2/2] mlxsw: spectrum_router: avoid potential uninitialized data usage

On Friday 30 September 2016, Ido Schimmel wrote: > BTW, which flags did you pass to generate this error? I can only > reproduce this with EXTRA_CFLAGS="-Wmaybe-uninitialized -Werror", but > for some reason EXTRA_CFLAGS="-Wall -Werror" is silent. Any idea why? I > would like to add this to my git

Re: [PATCH 2/2] mlxsw: spectrum_router: avoid potential uninitialized data usage

On Friday 30 September 2016, Ido Schimmel wrote: > BTW, which flags did you pass to generate this error? I can only > reproduce this with EXTRA_CFLAGS="-Wmaybe-uninitialized -Werror", but > for some reason EXTRA_CFLAGS="-Wall -Werror" is silent. Any idea why? I > would like to add this to my git

Re: [PATCH] rxrpc: split up rxrpc_send_call_packet()

On Saturday 01 October 2016, David Howells wrote: > commit 35510eefc29e2757c1ac46218cded2e505093fc2 > Author: David Howells > Date: Sat Oct 1 00:35:15 2016 +0100 > > rxrpc: Split rxrpc_send_call_packet() > > Split rxrpc_send_data_packet() to separate ACK

Re: [PATCH] rxrpc: split up rxrpc_send_call_packet()

On Saturday 01 October 2016, David Howells wrote: > commit 35510eefc29e2757c1ac46218cded2e505093fc2 > Author: David Howells > Date: Sat Oct 1 00:35:15 2016 +0100 > > rxrpc: Split rxrpc_send_call_packet() > > Split rxrpc_send_data_packet() to separate ACK generation (which is more

[PATCH -next 2/2] Input: synaptics-rmi4 - Propagate correct number of rx and tx electrodes to F54

F54 diagnostics report functions provide data based on the number of enabled rx and tx electrodes, which is not identical to the number of electrodes reported with F54:Query0 and F54:Query1. Those values report the number of supported electrodes, not the number of enabled electrodes. The number of

[PATCH -next 1/2] Input: synaptics-rmi4 - add support for F55 sensor tuning

receiver assignment) and F55:Ctrl2 (sensor transmitter assignment). Support for additional sensor tuning functions may be added later. Signed-off-by: Guenter Roeck <li...@roeck-us.net> --- This patch applies to next-20160930. drivers/input/rmi4/Kconfig | 9 +++ drivers/input/rmi4/Ma

[PATCH -next 2/2] Input: synaptics-rmi4 - Propagate correct number of rx and tx electrodes to F54

F54 diagnostics report functions provide data based on the number of enabled rx and tx electrodes, which is not identical to the number of electrodes reported with F54:Query0 and F54:Query1. Those values report the number of supported electrodes, not the number of enabled electrodes. The number of

[PATCH -next 1/2] Input: synaptics-rmi4 - add support for F55 sensor tuning

receiver assignment) and F55:Ctrl2 (sensor transmitter assignment). Support for additional sensor tuning functions may be added later. Signed-off-by: Guenter Roeck --- This patch applies to next-20160930. drivers/input/rmi4/Kconfig | 9 +++ drivers/input/rmi4/Makefile | 1

[PATCH] Input: synaptics-rmi4 - Fix error handling in SPI transport driver

Instantiating the rmi4 SPI transport driver without an interrupt assigned caused the driver to fail to load, but it does not clean up its transport device registration. Result may be a crash at a later time, for example when rebooting the system. Fixes: 8d99758dee31 ("Input: synaptics-rmi4 - add

[PATCH] Input: synaptics-rmi4 - Fix error handling in SPI transport driver

Instantiating the rmi4 SPI transport driver without an interrupt assigned caused the driver to fail to load, but it does not clean up its transport device registration. Result may be a crash at a later time, for example when rebooting the system. Fixes: 8d99758dee31 ("Input: synaptics-rmi4 - add

Re: [RFC][PATCH 0/7] printk: use alt_printk to handle printk() recursive calls

On (09/30/16 13:27), Petr Mladek wrote: > > > > This patch set extends a lock-less NMI per-cpu buffers idea to > > > > handle recursive printk() calls. The basic mechanism is pretty much the > > > > same -- at the beginning of a deadlock-prone section we switch to > > > > lock-less > > >

Re: [PATCH] Input: synaptics-rmi4 - Fix error handling in I2C transport driver

On 09/30/2016 03:54 PM, Dmitry Torokhov wrote: On Thu, Sep 29, 2016 at 10:55:40AM -0700, Bjorn Andersson wrote: On Wed 28 Sep 17:37 PDT 2016, Guenter Roeck wrote: Instantiating the rmi4 I2C transport driver without interrupts assigned (for example using manual i2c instantiation from the

Re: [RFC][PATCH 0/7] printk: use alt_printk to handle printk() recursive calls

On (09/30/16 13:27), Petr Mladek wrote: > > > > This patch set extends a lock-less NMI per-cpu buffers idea to > > > > handle recursive printk() calls. The basic mechanism is pretty much the > > > > same -- at the beginning of a deadlock-prone section we switch to > > > > lock-less > > >

Re: [PATCH] Input: synaptics-rmi4 - Fix error handling in I2C transport driver

On 09/30/2016 03:54 PM, Dmitry Torokhov wrote: On Thu, Sep 29, 2016 at 10:55:40AM -0700, Bjorn Andersson wrote: On Wed 28 Sep 17:37 PDT 2016, Guenter Roeck wrote: Instantiating the rmi4 I2C transport driver without interrupts assigned (for example using manual i2c instantiation from the

[x86] 811565123a: BUG: kernel hang in early-boot stage, last printk: Probing EDD (edd=off to disable)... ok

-03-16.cgz-811565123a194d9cc0b490719bef761e1730dbf4-20160930-107145-1d180kz-0.yaml ARCH=i386 kconfig=i386-randconfig-sb0-09262308 branch=linux-devel/devel-hourly-2016092605 commit=811565123a194d9cc0b490719bef761e1730dbf4 BOOT_IMAGE=/pkg/linux/i386-randconfig-sb0-0926

[x86] 811565123a: BUG: kernel hang in early-boot stage, last printk: Probing EDD (edd=off to disable)... ok

-03-16.cgz-811565123a194d9cc0b490719bef761e1730dbf4-20160930-107145-1d180kz-0.yaml ARCH=i386 kconfig=i386-randconfig-sb0-09262308 branch=linux-devel/devel-hourly-2016092605 commit=811565123a194d9cc0b490719bef761e1730dbf4 BOOT_IMAGE=/pkg/linux/i386-randconfig-sb0-0926

Re: [RFC][PATCH 6/7] printk: use alternative printk buffers

On (09/30/16 13:15), Petr Mladek wrote: [..] > > and the decision was to keep `unsigned long flags' on stack in the > > alt_enter/exit caller. besides in most of the cases we already have > > it (in vprintk_emit() and console_unlock()). > > I would pass the pointer to flags as alt_enter()

Re: [RFC][PATCH 6/7] printk: use alternative printk buffers

On (09/30/16 13:15), Petr Mladek wrote: [..] > > and the decision was to keep `unsigned long flags' on stack in the > > alt_enter/exit caller. besides in most of the cases we already have > > it (in vprintk_emit() and console_unlock()). > > I would pass the pointer to flags as alt_enter()

Re: [RFC PATCH v1 0/2] printk: Shared kernel logging

On Fri, Sep 30, 2016 at 6:56 PM, Sean Hudson wrote: > On 9/29/2016 8:36 PM, Kees Cook wrote: >> On Thu, Sep 29, 2016 at 5:55 PM, Sean Hudson >> wrote: >>> This patch set is based on Linus' v4.8-rc8 tag. >>> >>> This debug feature allows the

Re: [RFC PATCH v1 0/2] printk: Shared kernel logging

On Fri, Sep 30, 2016 at 6:56 PM, Sean Hudson wrote: > On 9/29/2016 8:36 PM, Kees Cook wrote: >> On Thu, Sep 29, 2016 at 5:55 PM, Sean Hudson >> wrote: >>> This patch set is based on Linus' v4.8-rc8 tag. >>> >>> This debug feature allows the kernel to use an external buffer and >>> control block

Re: [RFC][PATCHv2 3/7] printk: introduce per-cpu alt_print seq buffer

On (10/01/16 00:17), Sergey Senozhatsky wrote: [..] > +void alt_printk_enter(void) > +{ > + unsigned long flags; - > + local_irq_save(flags); > + if (!(this_cpu_read(alt_printk_ctx) & ALT_PRINTK_CONTEXT_MASK)) > + this_cpu_write(alt_printk_irq_flags, flags); > +

Re: [RFC][PATCHv2 3/7] printk: introduce per-cpu alt_print seq buffer

On (10/01/16 00:17), Sergey Senozhatsky wrote: [..] > +void alt_printk_enter(void) > +{ > + unsigned long flags; - > + local_irq_save(flags); > + if (!(this_cpu_read(alt_printk_ctx) & ALT_PRINTK_CONTEXT_MASK)) > + this_cpu_write(alt_printk_irq_flags, flags); > +

Re: [PATCH 1/3] proc: Stop reporting eip and esp in /proc/PID/stat

[cc: PeterZ] On Fri, Sep 30, 2016 at 11:56 AM, Jann Horn wrote: > On Fri, Sep 30, 2016 at 10:58:56AM -0700, Andy Lutomirski wrote: >> Reporting these fields on a non-current task is dangerous. If the >> task is in any state other than normal kernel code, they may contain >>

Re: [PATCH 1/3] proc: Stop reporting eip and esp in /proc/PID/stat

[cc: PeterZ] On Fri, Sep 30, 2016 at 11:56 AM, Jann Horn wrote: > On Fri, Sep 30, 2016 at 10:58:56AM -0700, Andy Lutomirski wrote: >> Reporting these fields on a non-current task is dangerous. If the >> task is in any state other than normal kernel code, they may contain >> garbage or even

Re: [RFC PATCH v1 0/2] printk: Shared kernel logging

On 9/29/2016 8:36 PM, Kees Cook wrote: > On Thu, Sep 29, 2016 at 5:55 PM, Sean Hudson > wrote: >> This patch set is based on Linus' v4.8-rc8 tag. >> >> This debug feature allows the kernel to use an external buffer and >> control block for kernel log messages. The feature

Re: [RFC PATCH v1 0/2] printk: Shared kernel logging

On 9/29/2016 8:36 PM, Kees Cook wrote: > On Thu, Sep 29, 2016 at 5:55 PM, Sean Hudson > wrote: >> This patch set is based on Linus' v4.8-rc8 tag. >> >> This debug feature allows the kernel to use an external buffer and >> control block for kernel log messages. The feature is controlled by >> an

Re: Ping: [PATCH v15 00/13] support "task_isolation" mode

On 9/27/2016 10:35 AM, Frederic Weisbecker wrote: On 8/16/2016 5:19 PM, Chris Metcalf wrote: Here is a respin of the task-isolation patch set. Again, I have been getting email asking me when and where this patch will be upstreamed so folks can start using it. I had been thinking the obvious

Re: Ping: [PATCH v15 00/13] support "task_isolation" mode

On 9/27/2016 10:35 AM, Frederic Weisbecker wrote: On 8/16/2016 5:19 PM, Chris Metcalf wrote: Here is a respin of the task-isolation patch set. Again, I have been getting email asking me when and where this patch will be upstreamed so folks can start using it. I had been thinking the obvious

[git pull] Input updates for 4.8-rc8

Hi Linus, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus to receive updates for the input subsystem. One small change to make joydev (which is used by older games) to bind to devices that export Z axis but not X or Y (such as TRC rudder).

[git pull] Input updates for 4.8-rc8

Hi Linus, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus to receive updates for the input subsystem. One small change to make joydev (which is used by older games) to bind to devices that export Z axis but not X or Y (such as TRC rudder).

[PATCH] f2fs: introduce update_ckpt_flags to clean up

This patch add update_ckpt_flags() to clean up the flow. Signed-off-by: Jaegeuk Kim --- fs/f2fs/checkpoint.c | 56 +++- 1 file changed, 33 insertions(+), 23 deletions(-) diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c

Re: [f2fs-dev] [PATCH 1/2 v2] f2fs: use crc and cp version to determine roll-forward recovery

On Sat, Oct 01, 2016 at 08:26:20AM +0800, Chao Yu wrote: > On 2016/10/1 1:10, Jaegeuk Kim wrote: > > @@ -1089,6 +1079,9 @@ static int do_checkpoint(struct f2fs_sb_info *sbi, > > struct cp_control *cpc) > > if (is_sbi_flag_set(sbi, SBI_NEED_FSCK)) > > set_ckpt_flags(ckpt,

[PATCH] f2fs: introduce update_ckpt_flags to clean up

This patch add update_ckpt_flags() to clean up the flow. Signed-off-by: Jaegeuk Kim --- fs/f2fs/checkpoint.c | 56 +++- 1 file changed, 33 insertions(+), 23 deletions(-) diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c index

Re: [f2fs-dev] [PATCH 1/2 v2] f2fs: use crc and cp version to determine roll-forward recovery

On Sat, Oct 01, 2016 at 08:26:20AM +0800, Chao Yu wrote: > On 2016/10/1 1:10, Jaegeuk Kim wrote: > > @@ -1089,6 +1079,9 @@ static int do_checkpoint(struct f2fs_sb_info *sbi, > > struct cp_control *cpc) > > if (is_sbi_flag_set(sbi, SBI_NEED_FSCK)) > > set_ckpt_flags(ckpt,

RE: [RFC PATCH v3 2/2] usb: typec: Type-C Port Controller Interface driver (tcpci)

Hi, > -Original Message- > From: Guenter Roeck [mailto:gro...@google.com] > Sent: Saturday, October 01, 2016 2:45 AM > To: Jun Li > Cc: Guenter Roeck ; Felipe Balbi > ; Chandra Sekhar Anagani >

RE: [RFC PATCH v3 2/2] usb: typec: Type-C Port Controller Interface driver (tcpci)

Hi, > -Original Message- > From: Guenter Roeck [mailto:gro...@google.com] > Sent: Saturday, October 01, 2016 2:45 AM > To: Jun Li > Cc: Guenter Roeck ; Felipe Balbi > ; Chandra Sekhar Anagani > ; Bruce Ashfield > ; Bin Gao ; Pranav Tipnis > ; Heikki Krogerus > ;

Re: Question on ext4 directory hashes in combination with file name encryption

On Fri, Sep 30, 2016 at 04:09:09PM +0200, Richard Weinberger wrote: > > if I read the ext4 code correctly, you pass encrypted filenames to > ext4fs_dirhash(). > These filenames are not encoded and therefore binary gibberish. That's correct. > Isn't this a problem for the ext4 hash functions?

Re: Question on ext4 directory hashes in combination with file name encryption

On Fri, Sep 30, 2016 at 04:09:09PM +0200, Richard Weinberger wrote: > > if I read the ext4 code correctly, you pass encrypted filenames to > ext4fs_dirhash(). > These filenames are not encoded and therefore binary gibberish. That's correct. > Isn't this a problem for the ext4 hash functions?

Re: [f2fs-dev] [PATCH 1/2 v2] f2fs: use crc and cp version to determine roll-forward recovery

On 2016/10/1 1:10, Jaegeuk Kim wrote: > @@ -1089,6 +1079,9 @@ static int do_checkpoint(struct f2fs_sb_info *sbi, > struct cp_control *cpc) > if (is_sbi_flag_set(sbi, SBI_NEED_FSCK)) > set_ckpt_flags(ckpt, CP_FSCK_FLAG); > > + /* set this flag to activate crc|cp_ver for

Re: [f2fs-dev] [PATCH 1/2 v2] f2fs: use crc and cp version to determine roll-forward recovery

On 2016/10/1 1:10, Jaegeuk Kim wrote: > @@ -1089,6 +1079,9 @@ static int do_checkpoint(struct f2fs_sb_info *sbi, > struct cp_control *cpc) > if (is_sbi_flag_set(sbi, SBI_NEED_FSCK)) > set_ckpt_flags(ckpt, CP_FSCK_FLAG); > > + /* set this flag to activate crc|cp_ver for

Re: [PATCH 1/4] Input: elan_i2c - fix return tests of i2c_smbus_read_block_data()

On Wed, Sep 28, 2016 at 04:34:01PM +0200, Benjamin Tissoires wrote: > i2c_smbus_read_block_data() returns negative errno else the number of > data bytes in the slave's response. > > Checking for error not null means the function always fails if the device > answers properly. > > So given that we

Re: [PATCH 1/4] Input: elan_i2c - fix return tests of i2c_smbus_read_block_data()

On Wed, Sep 28, 2016 at 04:34:01PM +0200, Benjamin Tissoires wrote: > i2c_smbus_read_block_data() returns negative errno else the number of > data bytes in the slave's response. > > Checking for error not null means the function always fails if the device > answers properly. > > So given that we

Re: [PATCH] jiffies: add time comparison functions for 64 bit jiffies

Nudge, poke. On Thu, Sep 29, 2016 at 5:33 AM, Jason A. Donenfeld wrote: > Though the time_before and time_after family of functions were nicely > extended to support jiffies64, so that the interface would be > consistent, it was forgotten to also extend the before/after jiffies

Re: [PATCH] jiffies: add time comparison functions for 64 bit jiffies

Nudge, poke. On Thu, Sep 29, 2016 at 5:33 AM, Jason A. Donenfeld wrote: > Though the time_before and time_after family of functions were nicely > extended to support jiffies64, so that the interface would be > consistent, it was forgotten to also extend the before/after jiffies > functions to

Re: [PATCH 3/4] Input: elan_i2c - add Host Notify support

On Wed, Sep 28, 2016 at 04:34:03PM +0200, Benjamin Tissoires wrote: > The Thinkpad series 13 uses Host Notify to report the interrupt. > Add elan_smb_alert() to handle those interrupts and disable the irq > handling on this case. > > Signed-off-by: Benjamin Tissoires

Re: [PATCH 3/4] Input: elan_i2c - add Host Notify support

On Wed, Sep 28, 2016 at 04:34:03PM +0200, Benjamin Tissoires wrote: > The Thinkpad series 13 uses Host Notify to report the interrupt. > Add elan_smb_alert() to handle those interrupts and disable the irq > handling on this case. > > Signed-off-by: Benjamin Tissoires > --- >

Re: [PATCH] rxrpc: split up rxrpc_send_call_packet()

Something like the attached. David --- commit 35510eefc29e2757c1ac46218cded2e505093fc2 Author: David Howells Date: Sat Oct 1 00:35:15 2016 +0100 rxrpc: Split rxrpc_send_call_packet() Split rxrpc_send_data_packet() to separate ACK generation (which is more

Re: [PATCH 2/4] Input: elan_i2c - always output the device information

On Wed, Sep 28, 2016 at 04:34:02PM +0200, Benjamin Tissoires wrote: > it's always easier to retrieve these information in bug reports when > it is always printed in the dmesg. > > Signed-off-by: Benjamin Tissoires > --- > drivers/input/mouse/elan_i2c_core.c | 2 +-

Re: [PATCH] rxrpc: split up rxrpc_send_call_packet()

Something like the attached. David --- commit 35510eefc29e2757c1ac46218cded2e505093fc2 Author: David Howells Date: Sat Oct 1 00:35:15 2016 +0100 rxrpc: Split rxrpc_send_call_packet() Split rxrpc_send_data_packet() to separate ACK generation (which is more complicated) from

Re: [PATCH 2/4] Input: elan_i2c - always output the device information

On Wed, Sep 28, 2016 at 04:34:02PM +0200, Benjamin Tissoires wrote: > it's always easier to retrieve these information in bug reports when > it is always printed in the dmesg. > > Signed-off-by: Benjamin Tissoires > --- > drivers/input/mouse/elan_i2c_core.c | 2 +- > 1 file changed, 1

Re: [PATCH] rxrpc: split up rxrpc_send_call_packet()

Arnd Bergmann wrote: > A number of reworks went into rxrpc_send_call_packet() recently, which > introduced another warning when built with -Wmaybe-uninitialized: > > In file included from ../net/rxrpc/output.c:20:0: > net/rxrpc/output.c: In function 'rxrpc_send_call_packet': >

Re: [PATCH] rxrpc: split up rxrpc_send_call_packet()

Arnd Bergmann wrote: > A number of reworks went into rxrpc_send_call_packet() recently, which > introduced another warning when built with -Wmaybe-uninitialized: > > In file included from ../net/rxrpc/output.c:20:0: > net/rxrpc/output.c: In function 'rxrpc_send_call_packet': >

Re: [PATCH 0/2] powerpc: stack protector (-fstack-protector) support

On Fri, 2016-09-30 at 18:38 +0200, Christophe LEROY wrote: > I don't have any ppc64 target, I only have mpc8xx and mpc83xx which > both  > are ppc32 That's what qemu is for :-) Cheers, Ben.

Re: [PATCH 0/2] powerpc: stack protector (-fstack-protector) support

On Fri, 2016-09-30 at 18:38 +0200, Christophe LEROY wrote: > I don't have any ppc64 target, I only have mpc8xx and mpc83xx which > both  > are ppc32 That's what qemu is for :-) Cheers, Ben.

[PATCH] staging: android: ion: fix warning found by checkpatch.pl

Fix checkpatch.pl warning: WARNING: braces {} are not necessary for single statement blocks Signed-off-by: Wayne Porter --- drivers/staging/android/ion/hisilicon/hi6220_ion.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH] staging: android: ion: fix warning found by checkpatch.pl

Fix checkpatch.pl warning: WARNING: braces {} are not necessary for single statement blocks Signed-off-by: Wayne Porter --- drivers/staging/android/ion/hisilicon/hi6220_ion.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [PATCH] Input: synaptics-rmi4 - Fix error handling in I2C transport driver

On Fri, Sep 30, 2016 at 03:54:03PM -0700, Dmitry Torokhov wrote: > On Thu, Sep 29, 2016 at 10:55:40AM -0700, Bjorn Andersson wrote: > > On Wed 28 Sep 17:37 PDT 2016, Guenter Roeck wrote: > > > > > Instantiating the rmi4 I2C transport driver without interrupts assigned > > > (for example using

Re: [PATCH] Input: synaptics-rmi4 - Fix error handling in I2C transport driver

On Fri, Sep 30, 2016 at 03:54:03PM -0700, Dmitry Torokhov wrote: > On Thu, Sep 29, 2016 at 10:55:40AM -0700, Bjorn Andersson wrote: > > On Wed 28 Sep 17:37 PDT 2016, Guenter Roeck wrote: > > > > > Instantiating the rmi4 I2C transport driver without interrupts assigned > > > (for example using

[PATCH] staging: android: ion: fix checks found by checkpatch.pl

Alignment fixes Signed-off-by: Wayne Porter --- drivers/staging/android/ion/hisilicon/hi6220_ion.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/android/ion/hisilicon/hi6220_ion.c

[PATCH] staging: android: ion: fix checks found by checkpatch.pl

Alignment fixes Signed-off-by: Wayne Porter --- drivers/staging/android/ion/hisilicon/hi6220_ion.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/android/ion/hisilicon/hi6220_ion.c b/drivers/staging/android/ion/hisilicon/hi6220_ion.c index

Re: [PATCH] leds: leds-pca963x: add power management support

On Fri, Sep 30, 2016 at 2:23 PM, Jacek Anaszewski wrote: > Hi Matt, > > Thanks for the patch. > > > On 09/30/2016 09:27 PM, Matt Ranostay wrote: >> >> Turn off LEDS on suspend and put device in low power state, and restore >> settings on resume. >> >> Cc: Tony Lindgren

Re: [PATCH] leds: leds-pca963x: add power management support

On Fri, Sep 30, 2016 at 2:23 PM, Jacek Anaszewski wrote: > Hi Matt, > > Thanks for the patch. > > > On 09/30/2016 09:27 PM, Matt Ranostay wrote: >> >> Turn off LEDS on suspend and put device in low power state, and restore >> settings on resume. >> >> Cc: Tony Lindgren >> Cc: Richard Purdie >>

Re: [PATCH] Input: synaptics-rmi4 - Fix error handling in I2C transport driver

On Thu, Sep 29, 2016 at 10:55:40AM -0700, Bjorn Andersson wrote: > On Wed 28 Sep 17:37 PDT 2016, Guenter Roeck wrote: > > > Instantiating the rmi4 I2C transport driver without interrupts assigned > > (for example using manual i2c instantiation from the command line) > > caused the driver to fail

Re: [PATCH] Input: synaptics-rmi4 - Fix error handling in I2C transport driver

On Thu, Sep 29, 2016 at 10:55:40AM -0700, Bjorn Andersson wrote: > On Wed 28 Sep 17:37 PDT 2016, Guenter Roeck wrote: > > > Instantiating the rmi4 I2C transport driver without interrupts assigned > > (for example using manual i2c instantiation from the command line) > > caused the driver to fail

[PATCH] ion_test: remove extra line per checkpatch.pl

Cleanup extra line found by checkpatch.pl Signed-off-by: Wayne Porter --- drivers/staging/android/uapi/ion_test.h | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/android/uapi/ion_test.h b/drivers/staging/android/uapi/ion_test.h index ffef06f..480242e

[PATCH] ion_test: remove extra line per checkpatch.pl

Cleanup extra line found by checkpatch.pl Signed-off-by: Wayne Porter --- drivers/staging/android/uapi/ion_test.h | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/android/uapi/ion_test.h b/drivers/staging/android/uapi/ion_test.h index ffef06f..480242e 100644 ---

Re: [PATCH] Input: eKTF2127: mark PM functions as __maybe_unused

On Fri, Sep 30, 2016 at 06:22:33PM +0200, Arnd Bergmann wrote: > The newly added ektf2127 driver uses the SIMPLE_DEV_PM_OPS macro > to conditionally refer to the resume/suspend functions, which > causes a warning when CONFIG_PM_SLEEP is disabled: > > drivers/input/touchscreen/ektf2127.c:168:12:

Re: [PATCH] Input: eKTF2127: mark PM functions as __maybe_unused

On Fri, Sep 30, 2016 at 06:22:33PM +0200, Arnd Bergmann wrote: > The newly added ektf2127 driver uses the SIMPLE_DEV_PM_OPS macro > to conditionally refer to the resume/suspend functions, which > causes a warning when CONFIG_PM_SLEEP is disabled: > > drivers/input/touchscreen/ektf2127.c:168:12:

Re: [PATCH v2 3/3] net: make net namespace sysctls belong to container's owner

On Fri, Sep 30, 2016 at 01:21:27AM -0400, David Miller wrote: > From: Dmitry Torokhov > Date: Thu, 29 Sep 2016 08:46:05 -0700 > > > Hi David, > > > > On Wed, Aug 10, 2016 at 2:36 PM, Dmitry Torokhov > > wrote: > >> If net namespace is

Re: [PATCH v2 3/3] net: make net namespace sysctls belong to container's owner

On Fri, Sep 30, 2016 at 01:21:27AM -0400, David Miller wrote: > From: Dmitry Torokhov > Date: Thu, 29 Sep 2016 08:46:05 -0700 > > > Hi David, > > > > On Wed, Aug 10, 2016 at 2:36 PM, Dmitry Torokhov > > wrote: > >> If net namespace is attached to a user namespace let's make container's > >>

mmotm 2016-09-30-15-24 uploaded

The mm-of-the-moment snapshot 2016-09-30-15-24 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

mmotm 2016-09-30-15-24 uploaded

The mm-of-the-moment snapshot 2016-09-30-15-24 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

[PATCH] net: Use ns_capable_noaudit() when determining net sysctl permissions

From: Tyler Hicks The capability check should not be audited since it is only being used to determine the inode permissions. A failed check does not indicate a violation of security policy but, when an LSM is enabled, a denial audit message was being generated. The denial

[PATCH] net: Use ns_capable_noaudit() when determining net sysctl permissions

From: Tyler Hicks The capability check should not be audited since it is only being used to determine the inode permissions. A failed check does not indicate a violation of security policy but, when an LSM is enabled, a denial audit message was being generated. The denial audit message caused

Re: [PATCH v5 3/3] pci:aer: add support aer interrupt with none MSI/MSI-X/INTx mode

On Wed, Sep 21, 2016 at 06:54:59AM +, Po Liu wrote: > > > > Will the new kernel work with existing/old DTB? I'm trying to > > > > understand the dependency between driver and DTS changes. > > > > > > Yes, We've never use name 'intr' before. So we remove it is ok. > > > 'aer' is a dts

Re: [PATCH v5 3/3] pci:aer: add support aer interrupt with none MSI/MSI-X/INTx mode

On Wed, Sep 21, 2016 at 06:54:59AM +, Po Liu wrote: > > > > Will the new kernel work with existing/old DTB? I'm trying to > > > > understand the dependency between driver and DTS changes. > > > > > > Yes, We've never use name 'intr' before. So we remove it is ok. > > > 'aer' is a dts

  1   2   3   4   5   6   7   8   9   10   >