[GIT PULL] extcon next for v4.16

Dear Greg, This is extcon-next pull request for v4.16. I add detailed description of this pull request on below. Please pull extcon with following updates. Best Regards, Chanwoo Choi The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323: Linux 4.15-rc1 (2017-11-26

[GIT PULL] extcon next for v4.16

Dear Greg, This is extcon-next pull request for v4.16. I add detailed description of this pull request on below. Please pull extcon with following updates. Best Regards, Chanwoo Choi The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323: Linux 4.15-rc1 (2017-11-26

RE: [PATCH 2/2] cpufreq: imx6q: add 696MHz operating point for i.mx6ul

Post the discussion mail to arm kernel mail list, since last mail is rejected due to incorrect format, sorry for the confusion. Best Regards! Anson Huang > -Original Message- > From: Fabio Estevam [mailto:feste...@gmail.com] > Sent: 2018-01-02 11:33 PM > To: Anson Huang

Re: About the try to remove cross-release feature entirely by Ingo

On 12/31/2017 7:40 AM, Theodore Ts'o wrote: On Sat, Dec 30, 2017 at 12:44:17PM -0800, Matthew Wilcox wrote: I'm not sure I agree with this part. What if we add a new TCP lock class for connections which are used for filesystems/network block devices/...? Yes, it'll be up to each user to set

Re: About the try to remove cross-release feature entirely by Ingo

On 12/31/2017 7:40 AM, Theodore Ts'o wrote: On Sat, Dec 30, 2017 at 12:44:17PM -0800, Matthew Wilcox wrote: I'm not sure I agree with this part. What if we add a new TCP lock class for connections which are used for filesystems/network block devices/...? Yes, it'll be up to each user to set

RE: [PATCH 2/2] cpufreq: imx6q: add 696MHz operating point for i.mx6ul

Post the discussion mail to arm kernel mail list, since last mail is rejected due to incorrect format, sorry for the confusion. Best Regards! Anson Huang > -Original Message- > From: Fabio Estevam [mailto:feste...@gmail.com] > Sent: 2018-01-02 11:33 PM > To: Anson Huang > Cc:

Re: ACPI issues on cold power on [bisected]

On Tue, Jan 02, 2018 at 11:25:01AM +0100, Rafael J. Wysocki wrote: > On Tue, Jan 2, 2018 at 3:54 AM, Joonsoo Kim wrote: > > On Fri, Dec 29, 2017 at 04:36:59PM +, Jonathan McDowell wrote: > >> On Fri, Dec 22, 2017 at 09:21:09AM +0900, Joonsoo Kim wrote: > >> > On Fri,

Re: ACPI issues on cold power on [bisected]

On Tue, Jan 02, 2018 at 11:25:01AM +0100, Rafael J. Wysocki wrote: > On Tue, Jan 2, 2018 at 3:54 AM, Joonsoo Kim wrote: > > On Fri, Dec 29, 2017 at 04:36:59PM +, Jonathan McDowell wrote: > >> On Fri, Dec 22, 2017 at 09:21:09AM +0900, Joonsoo Kim wrote: > >> > On Fri, Dec 08, 2017 at

RE: [PATCH 1/2] ARM: dts: imx6ul: add 696MHz operating point

Post this discussion mail to kernel mail list, since last mail is rejected due to incorrect format, sorry for confusion. Best Regards! Anson Huang > -Original Message- > From: Fabio Estevam [mailto:feste...@gmail.com] > Sent: 2018-01-02 11:32 PM > To: Anson Huang

RE: [PATCH 1/2] ARM: dts: imx6ul: add 696MHz operating point

Post this discussion mail to kernel mail list, since last mail is rejected due to incorrect format, sorry for confusion. Best Regards! Anson Huang > -Original Message- > From: Fabio Estevam [mailto:feste...@gmail.com] > Sent: 2018-01-02 11:32 PM > To: Anson Huang > Cc: moderated

Re: [PATCH] ext4: Remove repeated test in ext4_file_read_iter.

On Wed, Dec 27, 2017 at 04:19:58PM +0800, Sean Fu wrote: > generic_file_read_iter has done the count test. > So ext4_file_read_iter don't need to test the count repeatedly. Huh? You do realize that generic_file_read_iter() is not the only variant possible there, right? static ssize_t

Re: [PATCH] ext4: Remove repeated test in ext4_file_read_iter.

On Wed, Dec 27, 2017 at 04:19:58PM +0800, Sean Fu wrote: > generic_file_read_iter has done the count test. > So ext4_file_read_iter don't need to test the count repeatedly. Huh? You do realize that generic_file_read_iter() is not the only variant possible there, right? static ssize_t

Re: [lkp-robot] [mm/cma] 2b0f904a5a: fio.read_bw_MBps -16.1% regression

Hello! On Tue, Jan 02, 2018 at 02:35:28PM +0800, kernel test robot wrote: > > Greeting, > > FYI, we noticed a -16.1% regression of fio.read_bw_MBps due to commit: > > > commit: 2b0f904a5a8781498417d67226fd12c5e56053ae ("mm/cma: manage the memory > of the CMA area by using the ZONE_MOVABLE")

Re: [lkp-robot] [mm/cma] 2b0f904a5a: fio.read_bw_MBps -16.1% regression

Hello! On Tue, Jan 02, 2018 at 02:35:28PM +0800, kernel test robot wrote: > > Greeting, > > FYI, we noticed a -16.1% regression of fio.read_bw_MBps due to commit: > > > commit: 2b0f904a5a8781498417d67226fd12c5e56053ae ("mm/cma: manage the memory > of the CMA area by using the ZONE_MOVABLE")

[PATCH] f2fs: enable quota at remount from r to w

We have to enable quota only when remounting from read to write. Otherwise, we'll get remount failure. (e.g., write to write case) Signed-off-by: Jaegeuk Kim --- fs/f2fs/super.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/f2fs/super.c

[PATCH] f2fs: enable quota at remount from r to w

We have to enable quota only when remounting from read to write. Otherwise, we'll get remount failure. (e.g., write to write case) Signed-off-by: Jaegeuk Kim --- fs/f2fs/super.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c index

Re: About the try to remove cross-release feature entirely by Ingo

On 12/31/2017 12:40 AM, Theodore Ts'o wrote: On Fri, Dec 29, 2017 at 10:16:24PM -0800, Matthew Wilcox wrote: I disagree here. As Ted says, it's the interactions between the subsystems that leads to problems. Everything's goig to work great until somebody does something in a way that's never

Re: About the try to remove cross-release feature entirely by Ingo

On 12/31/2017 12:40 AM, Theodore Ts'o wrote: On Fri, Dec 29, 2017 at 10:16:24PM -0800, Matthew Wilcox wrote: I disagree here. As Ted says, it's the interactions between the subsystems that leads to problems. Everything's goig to work great until somebody does something in a way that's never

Re: [PATCH v3 net-next 2/5] net: tracepoint: replace tcp_set_state tracepoint with inet_sock_set_state tracepoint

On Wed, Jan 3, 2018 at 3:46 AM, Brendan Gregg wrote: > On Sat, Dec 30, 2017 at 7:06 PM, Yafang Shao wrote: >> On Sun, Dec 31, 2017 at 6:33 AM, Brendan Gregg >> wrote: >>> On Tue, Dec 19, 2017 at 7:12 PM, Yafang Shao

Re: [PATCH v3 net-next 2/5] net: tracepoint: replace tcp_set_state tracepoint with inet_sock_set_state tracepoint

On Wed, Jan 3, 2018 at 3:46 AM, Brendan Gregg wrote: > On Sat, Dec 30, 2017 at 7:06 PM, Yafang Shao wrote: >> On Sun, Dec 31, 2017 at 6:33 AM, Brendan Gregg >> wrote: >>> On Tue, Dec 19, 2017 at 7:12 PM, Yafang Shao wrote: As sk_state is a common field for struct sock, so the state

Re: [PATCH v7 5/5] clk: aspeed: Add reset controller

On 12/22, Joel Stanley wrote: > There are some resets that are not associated with gates. These are > represented by a reset controller. > > Reviewed-by: Andrew Jeffery > Signed-off-by: Joel Stanley > --- Applied to clk-next -- Qualcomm Innovation Center,

Re: [PATCH v7 3/5] clk: aspeed: Add platform driver and register PLLs

On 12/22, Joel Stanley wrote: > This registers a platform driver to set up all of the non-core clocks. > > The clocks that have configurable rates are now registered. > > Reviewed-by: Andrew Jeffery > Signed-off-by: Joel Stanley > -- > v6: > - Add Andrew's

Re: [PATCH v7 5/5] clk: aspeed: Add reset controller

On 12/22, Joel Stanley wrote: > There are some resets that are not associated with gates. These are > represented by a reset controller. > > Reviewed-by: Andrew Jeffery > Signed-off-by: Joel Stanley > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a member of Code Aurora

Re: [PATCH v7 3/5] clk: aspeed: Add platform driver and register PLLs

On 12/22, Joel Stanley wrote: > This registers a platform driver to set up all of the non-core clocks. > > The clocks that have configurable rates are now registered. > > Reviewed-by: Andrew Jeffery > Signed-off-by: Joel Stanley > -- > v6: > - Add Andrew's reviewed-by > v5: > - Remove eclk

Re: [RFC PATCH] input: Add disable sysfs entry for every input device

On Tue, 2018-01-02 at 22:54 +0100, Pali Rohár wrote: > On Wednesday 04 January 2017 15:37:35 Bastien Nocera wrote: > > I don't doubt that the use cases should be catered for, I > > essentially > > did that same work without kernel changes for GNOME. What I doubt > > is > > the fuzzy semantics, the

Re: [PATCH v7 4/5] clk: aspeed: Register gated clocks

On 12/22, Joel Stanley wrote: > The majority of the clocks in the system are gates paired with a reset > controller that holds the IP in reset. > > This borrows from clk_hw_register_gate, but registers two 'gates', one > to control the clock enable register and the other to control the reset >

Re: [PATCH v7 1/5] clk: Add clock driver for ASPEED BMC SoCs

On 12/22, Joel Stanley wrote: > This adds the stub of a driver for the ASPEED SoCs. The clocks are > defined and the static registration is set up. > > Reviewed-by: Andrew Jeffery > Signed-off-by: Joel Stanley > --- Applied to clk-next -- Qualcomm Innovation

Re: [RFC PATCH] input: Add disable sysfs entry for every input device

On Tue, 2018-01-02 at 22:54 +0100, Pali Rohár wrote: > On Wednesday 04 January 2017 15:37:35 Bastien Nocera wrote: > > I don't doubt that the use cases should be catered for, I > > essentially > > did that same work without kernel changes for GNOME. What I doubt > > is > > the fuzzy semantics, the

Re: [PATCH v7 4/5] clk: aspeed: Register gated clocks

On 12/22, Joel Stanley wrote: > The majority of the clocks in the system are gates paired with a reset > controller that holds the IP in reset. > > This borrows from clk_hw_register_gate, but registers two 'gates', one > to control the clock enable register and the other to control the reset >

Re: [PATCH v7 1/5] clk: Add clock driver for ASPEED BMC SoCs

On 12/22, Joel Stanley wrote: > This adds the stub of a driver for the ASPEED SoCs. The clocks are > defined and the static registration is set up. > > Reviewed-by: Andrew Jeffery > Signed-off-by: Joel Stanley > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a member of Code

Re: [PATCH v7 2/5] clk: aspeed: Register core clocks

On 12/22, Joel Stanley wrote: > This registers the core clocks; those which are required to calculate > the rate of the timer peripheral so the system can load a clocksource > driver. > > Reviewed-by: Andrew Jeffery > Signed-off-by: Joel Stanley > --- Applied

Re: [PATCH v7 2/5] clk: aspeed: Register core clocks

On 12/22, Joel Stanley wrote: > This registers the core clocks; those which are required to calculate > the rate of the timer peripheral so the system can load a clocksource > driver. > > Reviewed-by: Andrew Jeffery > Signed-off-by: Joel Stanley > --- Applied to clk-next -- Qualcomm

Re: [PATCH v3 1/9] ufs: sysfs: device descriptor

On 01/02, Stanislav Nijnikov wrote: > > > > -Original Message- > > From: Jaegeuk Kim [mailto:jaeg...@kernel.org] > > Sent: Thursday, December 28, 2017 9:37 PM > > To: Stanislav Nijnikov > > Cc: linux-s...@vger.kernel.org; linux-kernel@vger.kernel.org; > >

Re: [RFC PATCH] input: Add disable sysfs entry for every input device

On Tue, 2018-01-02 at 22:48 +0100, Pali Rohár wrote: > On Tuesday 03 January 2017 12:21:21 Bastien Nocera wrote: > > On Mon, 2017-01-02 at 18:09 +0100, Pali Rohár wrote: > > > On Monday 02 January 2017 16:27:05 Bastien Nocera wrote: > > > > On Sun, 2016-12-25 at 11:04 +0100, Pali Rohár wrote: > >

Re: [PATCH v3 1/9] ufs: sysfs: device descriptor

On 01/02, Stanislav Nijnikov wrote: > > > > -Original Message- > > From: Jaegeuk Kim [mailto:jaeg...@kernel.org] > > Sent: Thursday, December 28, 2017 9:37 PM > > To: Stanislav Nijnikov > > Cc: linux-s...@vger.kernel.org; linux-kernel@vger.kernel.org; > > gre...@linuxfoundation.org;

Re: [RFC PATCH] input: Add disable sysfs entry for every input device

On Tue, 2018-01-02 at 22:48 +0100, Pali Rohár wrote: > On Tuesday 03 January 2017 12:21:21 Bastien Nocera wrote: > > On Mon, 2017-01-02 at 18:09 +0100, Pali Rohár wrote: > > > On Monday 02 January 2017 16:27:05 Bastien Nocera wrote: > > > > On Sun, 2016-12-25 at 11:04 +0100, Pali Rohár wrote: > >

[PATCH v3 1/2] kprobes: propagate error from arm_kprobe_ftrace()

Improve error handling when arming ftrace-based kprobes. Specifically, if we fail to arm a ftrace-based kprobe, register_kprobe()/enable_kprobe() should report an error instead of success. Previously, this has lead to confusing situations where register_kprobe() would return 0 indicating success,

Re: [PATCHv6 1/1] ima: re-introduce own integrity cache lock

[might as well cc linux-xfs] On Thu, Dec 14, 2017 at 12:22:37AM +0200, Dmitry Kasatkin wrote: > Hi, > > Could I ask FS maintainers to test IMA with this patch additionally > and provide ack/tested. > We tested but may be you have and some special testing. Super-late to this party, but unless

[PATCH v3 1/2] kprobes: propagate error from arm_kprobe_ftrace()

Improve error handling when arming ftrace-based kprobes. Specifically, if we fail to arm a ftrace-based kprobe, register_kprobe()/enable_kprobe() should report an error instead of success. Previously, this has lead to confusing situations where register_kprobe() would return 0 indicating success,

Re: [PATCHv6 1/1] ima: re-introduce own integrity cache lock

[might as well cc linux-xfs] On Thu, Dec 14, 2017 at 12:22:37AM +0200, Dmitry Kasatkin wrote: > Hi, > > Could I ask FS maintainers to test IMA with this patch additionally > and provide ack/tested. > We tested but may be you have and some special testing. Super-late to this party, but unless

[PATCH v3 2/2] kprobes: propagate error from disarm_kprobe_ftrace()

Improve error handling when disarming ftrace-based kprobes. Like with arm_kprobe_ftrace(), propagate any errors from disarm_kprobe_ftrace() so that we do not disable/unregister kprobes that are still armed. In other words, unregister_kprobe() and disable_kprobe() should not report success if the

[PATCH v3 2/2] kprobes: propagate error from disarm_kprobe_ftrace()

Improve error handling when disarming ftrace-based kprobes. Like with arm_kprobe_ftrace(), propagate any errors from disarm_kprobe_ftrace() so that we do not disable/unregister kprobes that are still armed. In other words, unregister_kprobe() and disable_kprobe() should not report success if the

[PATCH v3 0/2] kprobes: improve error handling when arming/disarming kprobes

Hi, This patchset attempts to improve error handling when arming or disarming ftrace-based kprobes. The current behavior is to simply WARN when ftrace (un-)registration fails, without propagating the error code. This can lead to confusing situations where, for example,

[PATCH v3 0/2] kprobes: improve error handling when arming/disarming kprobes

Hi, This patchset attempts to improve error handling when arming or disarming ftrace-based kprobes. The current behavior is to simply WARN when ftrace (un-)registration fails, without propagating the error code. This can lead to confusing situations where, for example,

Re: [PATCHv3 1/2] capability: introduce sysctl for controlled user-ns capability whitelist

On Sat, Dec 30, 2017 at 12:50 AM, Michael Kerrisk (man-pages) wrote: > Hello Mahesh, > > On 12/05/2017 11:31 PM, Mahesh Bandewar wrote: >> From: Mahesh Bandewar >> >> Add a sysctl variable kernel.controlled_userns_caps_whitelist. This >> takes input as

Re: [PATCHv3 1/2] capability: introduce sysctl for controlled user-ns capability whitelist

On Sat, Dec 30, 2017 at 12:50 AM, Michael Kerrisk (man-pages) wrote: > Hello Mahesh, > > On 12/05/2017 11:31 PM, Mahesh Bandewar wrote: >> From: Mahesh Bandewar >> >> Add a sysctl variable kernel.controlled_userns_caps_whitelist. This >> takes input as capability mask expressed as two comma

Re: [RFC PATCH] input: Add disable sysfs entry for every input device

On Tue, 2017-01-17 at 12:07 +0100, Pavel Machek wrote: > > We'd really like it to work on plain old text console, too, because > that's what > I'm using on n900, and with old maemo userspace, because that's what > everyone > else uses. > > You mentioned you think X.org can do this kind of

[GIT PULL] pid bug fix for v4.15-rc7

Linus, Please pull the for-linus branch from the git tree: git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git for-linus HEAD: c0ee554906c3d6554fbddf95ae664cd9f817082b pid: Handle failure to allocate the first pid in a pid namespace The replacement of the pid

Re: [RFC PATCH] input: Add disable sysfs entry for every input device

On Tue, 2017-01-17 at 12:07 +0100, Pavel Machek wrote: > > We'd really like it to work on plain old text console, too, because > that's what > I'm using on n900, and with old maemo userspace, because that's what > everyone > else uses. > > You mentioned you think X.org can do this kind of

[GIT PULL] pid bug fix for v4.15-rc7

Linus, Please pull the for-linus branch from the git tree: git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git for-linus HEAD: c0ee554906c3d6554fbddf95ae664cd9f817082b pid: Handle failure to allocate the first pid in a pid namespace The replacement of the pid

[PATCH 3/5] arch: Remove clkdev.h asm-generic from Kbuild

Now that every architecture is using the generic clkdev.h file and we no longer include asm/clkdev.h anywhere in the tree, we can remove it. Cc: Russell King Cc: Arnd Bergmann Cc: Signed-off-by: Stephen Boyd

[PATCH 5/5] clk: Move __clk_{get,put}() into private clk.h API

We can move these APIs into the private header file now that we don't have any users of the __clk_get() and __clk_put() APIs outside of clkdev.c and clk.c. Cc: Russell King Signed-off-by: Stephen Boyd --- drivers/clk/clk.h | 4

[PATCH 5/5] clk: Move __clk_{get,put}() into private clk.h API

We can move these APIs into the private header file now that we don't have any users of the __clk_get() and __clk_put() APIs outside of clkdev.c and clk.c. Cc: Russell King Signed-off-by: Stephen Boyd --- drivers/clk/clk.h | 4 include/linux/clkdev.h | 8 2 files changed, 4

[PATCH 3/5] arch: Remove clkdev.h asm-generic from Kbuild

Now that every architecture is using the generic clkdev.h file and we no longer include asm/clkdev.h anywhere in the tree, we can remove it. Cc: Russell King Cc: Arnd Bergmann Cc: Signed-off-by: Stephen Boyd --- arch/alpha/include/asm/Kbuild | 1 - arch/arc/include/asm/Kbuild|

[PATCH 1/5] blackfin: Use generic clkdev.h header

The generic header file is equivalent to the blackfin version, so just use the generic one. Signed-off-by: Stephen Boyd --- arch/blackfin/include/asm/Kbuild | 1 + arch/blackfin/include/asm/clkdev.h | 17 - 2 files changed, 1 insertion(+), 17

[PATCH 1/5] blackfin: Use generic clkdev.h header

The generic header file is equivalent to the blackfin version, so just use the generic one. Signed-off-by: Stephen Boyd --- arch/blackfin/include/asm/Kbuild | 1 + arch/blackfin/include/asm/clkdev.h | 17 - 2 files changed, 1 insertion(+), 17 deletions(-) delete mode 100644

[PATCH 4/5] clk: sunxi: Use CLK_IS_CRITICAL flag for critical clks

We'd like to privatize __clk_get(), but the sunxi clk driver is calling this function to keep a reference held on the clk and call clk_prepare_enable() on it. We support this design in the clk core now with the CLK_IS_CRITICAL flag, so let's just use that instead. Cc: Maxime Ripard

[PATCH 4/5] clk: sunxi: Use CLK_IS_CRITICAL flag for critical clks

We'd like to privatize __clk_get(), but the sunxi clk driver is calling this function to keep a reference held on the clk and call clk_prepare_enable() on it. We support this design in the clk core now with the CLK_IS_CRITICAL flag, so let's just use that instead. Cc: Maxime Ripard Cc: Chen-Yu

[PATCH 2/5] clk: Prepare to remove asm-generic/clkdev.h

Now that all the users of asm/clkdev.h have been replaced with the generic file we can get rid of the asm-generic file as well and implement that code directly where it's used. We only have one caller of __clkdev_alloc(), in clkdev.c so we can easily remove that and drop the include of

[PATCH 2/5] clk: Prepare to remove asm-generic/clkdev.h

Now that all the users of asm/clkdev.h have been replaced with the generic file we can get rid of the asm-generic file as well and implement that code directly where it's used. We only have one caller of __clkdev_alloc(), in clkdev.c so we can easily remove that and drop the include of

Re: [PATCHv3 0/2] capability controlled user-namespaces

Hello Michael, I really don't want to turn this into how-to-hack guide but I do see few points in your argument to make the case clearer. Please see the comments inline. On Sat, Dec 30, 2017 at 12:50 AM, Michael Kerrisk (man-pages) wrote: > Hello Mahesh, > > On

Re: [PATCHv3 0/2] capability controlled user-namespaces

Hello Michael, I really don't want to turn this into how-to-hack guide but I do see few points in your argument to make the case clearer. Please see the comments inline. On Sat, Dec 30, 2017 at 12:50 AM, Michael Kerrisk (man-pages) wrote: > Hello Mahesh, > > On 12/28/2017 01:45 AM, Mahesh

Re: [PATCH 2/4] extcon: axp288: Remove unused platform data

Dear Lee, On 2018년 01월 02일 18:16, Lee Jones wrote: > On Tue, 02 Jan 2018, Chanwoo Choi wrote: > >> + MFD Maintainer (Lee Jones ) >> >> Hi Hans, >> >> You better to use the scripts/get_maintainer.pl for the mailing list. >> I added the MFD maintainer. >> >> This patch looks

Re: [PATCH 2/4] extcon: axp288: Remove unused platform data

Dear Lee, On 2018년 01월 02일 18:16, Lee Jones wrote: > On Tue, 02 Jan 2018, Chanwoo Choi wrote: > >> + MFD Maintainer (Lee Jones ) >> >> Hi Hans, >> >> You better to use the scripts/get_maintainer.pl for the mailing list. >> I added the MFD maintainer. >> >> This patch looks good to me. >>

[PATCH 0/5] Remove asm/clkdev.h and privatize __clk{get,put}()

These patches remove the asm-generic/clkdev.h header file and fold it into the linux/clkdev.h file. I'd like to merge this into the clk tree for the upcoming merge window, so please ack if things look good. The later patches I also want to drop the slab.h include from clkdev.h, but that will

[PATCH 0/5] Remove asm/clkdev.h and privatize __clk{get,put}()

These patches remove the asm-generic/clkdev.h header file and fold it into the linux/clkdev.h file. I'd like to merge this into the clk tree for the upcoming merge window, so please ack if things look good. The later patches I also want to drop the slab.h include from clkdev.h, but that will

Re: [PATCHv3 0/2] capability controlled user-namespaces

On Sat, Dec 30, 2017 at 12:31 AM, James Morris wrote: > On Wed, 27 Dec 2017, Mahesh Bandewar (महेश बंडेवार) wrote: > >> Hello James, >> >> Seems like I missed your name to be added into the review of this >> patch series. Would you be willing be pull this into the

Re: [PATCHv3 0/2] capability controlled user-namespaces

On Sat, Dec 30, 2017 at 12:31 AM, James Morris wrote: > On Wed, 27 Dec 2017, Mahesh Bandewar (महेश बंडेवार) wrote: > >> Hello James, >> >> Seems like I missed your name to be added into the review of this >> patch series. Would you be willing be pull this into the security >> tree? Serge Hallyn

Re: [PATCH 1/4] extcon: axp288: Remove unused extcon_nb struct member

Hi Hans, On 2017년 12월 22일 21:36, Hans de Goede wrote: > Remove the unused extcon_nb struct member. > > Signed-off-by: Hans de Goede > --- > drivers/extcon/extcon-axp288.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/drivers/extcon/extcon-axp288.c

Re: [PATCH 1/4] extcon: axp288: Remove unused extcon_nb struct member

Hi Hans, On 2017년 12월 22일 21:36, Hans de Goede wrote: > Remove the unused extcon_nb struct member. > > Signed-off-by: Hans de Goede > --- > drivers/extcon/extcon-axp288.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/drivers/extcon/extcon-axp288.c b/drivers/extcon/extcon-axp288.c >

Re: platform/x86/thinkpad_acpi: Adjustments for four function implementations

On Tue, Jan 02, 2018 at 04:49:43PM -0800, Joe Perches wrote: > On Tue, 2018-01-02 at 16:10 -0800, Darren Hart wrote: > > > > Leave those pr_ messages alone, please, > [] > > Andy and Henrique raised a few reasons why these patches should not be > > accepted: > > > > 1. This is init code (so any

Re: platform/x86/thinkpad_acpi: Adjustments for four function implementations

On Tue, Jan 02, 2018 at 04:49:43PM -0800, Joe Perches wrote: > On Tue, 2018-01-02 at 16:10 -0800, Darren Hart wrote: > > > > Leave those pr_ messages alone, please, > [] > > Andy and Henrique raised a few reasons why these patches should not be > > accepted: > > > > 1. This is init code (so any

Re: [PATCH 3/4] extcon: axp288: Redo charger type dection a couple of seconds after probe()

Hi Hans, On 2018년 01월 03일 09:58, Chanwoo Choi wrote: > Hi Hans, > > On 2018년 01월 03일 07:44, Hans de Goede wrote: >> Hi, >> >> On 02-01-18 01:54, Chanwoo Choi wrote: >>> Hi Hans, >>> >>> s/dection/detection on patch title. >> >> Thank you for all the reviews. >> >> I've fixed the typo in my

Re: [PATCH 3/4] extcon: axp288: Redo charger type dection a couple of seconds after probe()

Hi Hans, On 2018년 01월 03일 09:58, Chanwoo Choi wrote: > Hi Hans, > > On 2018년 01월 03일 07:44, Hans de Goede wrote: >> Hi, >> >> On 02-01-18 01:54, Chanwoo Choi wrote: >>> Hi Hans, >>> >>> s/dection/detection on patch title. >> >> Thank you for all the reviews. >> >> I've fixed the typo in my

Re: [PATCH v5 01/78] xfs: Rename xa_ elements to ail_

On Fri, Dec 15, 2017 at 02:03:33PM -0800, Matthew Wilcox wrote: > From: Matthew Wilcox > > This is a simple rename, except that xa_ail becomes ail_head. > > Signed-off-by: Matthew Wilcox That was an eyeful, Reviewed-by: Darrick J. Wong

Re: [PATCH v5 01/78] xfs: Rename xa_ elements to ail_

On Fri, Dec 15, 2017 at 02:03:33PM -0800, Matthew Wilcox wrote: > From: Matthew Wilcox > > This is a simple rename, except that xa_ail becomes ail_head. > > Signed-off-by: Matthew Wilcox That was an eyeful, Reviewed-by: Darrick J. Wong > --- > fs/xfs/xfs_buf_item.c| 10 ++-- >

Re: [PATCH v6 00/11] Intel SGX Driver

On Dec 27, 9:46pm, Pavel Machek wrote: } Subject: Re: [PATCH v6 00/11] Intel SGX Driver > Hi! Good evening Pavel et.al., I hope the New Year has started well for everyone. > > > Would you list guarantees provided by SGX? > > > > Obviously, confidentiality and integrity. SGX was designed to

Re: [PATCH v6 00/11] Intel SGX Driver

On Dec 27, 9:46pm, Pavel Machek wrote: } Subject: Re: [PATCH v6 00/11] Intel SGX Driver > Hi! Good evening Pavel et.al., I hope the New Year has started well for everyone. > > > Would you list guarantees provided by SGX? > > > > Obviously, confidentiality and integrity. SGX was designed to

Re: [PATCH 3/4] extcon: axp288: Redo charger type dection a couple of seconds after probe()

Hi Hans, On 2018년 01월 03일 07:44, Hans de Goede wrote: > Hi, > > On 02-01-18 01:54, Chanwoo Choi wrote: >> Hi Hans, >> >> s/dection/detection on patch title. > > Thank you for all the reviews. > > I've fixed the typo in my personal tree. > >> On 2017년 12월 22일 21:36, Hans de Goede wrote: >>>

Re: [PATCH 3/4] extcon: axp288: Redo charger type dection a couple of seconds after probe()

Hi Hans, On 2018년 01월 03일 07:44, Hans de Goede wrote: > Hi, > > On 02-01-18 01:54, Chanwoo Choi wrote: >> Hi Hans, >> >> s/dection/detection on patch title. > > Thank you for all the reviews. > > I've fixed the typo in my personal tree. > >> On 2017년 12월 22일 21:36, Hans de Goede wrote: >>>

Re: linux-next: manual merge of the usb tree with the usb.current tree

Hi Greg, On Wed, 20 Dec 2017 10:36:15 +0100 Greg KH wrote: > > Thanks for the fixup, I'll do it when these trees converge in a week or > so. Unfortunately, it looks like when you back merged Linus' tree (to get commit 8272d099d05f) you lost the spelling fix in commit

Re: linux-next: manual merge of the usb tree with the usb.current tree

Hi Greg, On Wed, 20 Dec 2017 10:36:15 +0100 Greg KH wrote: > > Thanks for the fixup, I'll do it when these trees converge in a week or > so. Unfortunately, it looks like when you back merged Linus' tree (to get commit 8272d099d05f) you lost the spelling fix in commit 81d8a8eb0a97. -- Cheers,

RE: [PATCH V3] ARM: imx: use outer_disable/resume for low power

> -Original Message- > From: Peng Fan > Sent: Thursday, December 28, 2017 5:09 PM > To: shawn...@kernel.org > Cc: linux-arm-ker...@lists.infradead.org; linux-kernel@vger.kernel.org; > van.free...@gmail.com; Peng Fan ; Sascha Hauer > ; Fabio

RE: [PATCH V3] ARM: imx: use outer_disable/resume for low power

> -Original Message- > From: Peng Fan > Sent: Thursday, December 28, 2017 5:09 PM > To: shawn...@kernel.org > Cc: linux-arm-ker...@lists.infradead.org; linux-kernel@vger.kernel.org; > van.free...@gmail.com; Peng Fan ; Sascha Hauer > ; Fabio Estevam ; A.s. > Dong ; Russell King >

Re: platform/x86/thinkpad_acpi: Adjustments for four function implementations

On Tue, 2018-01-02 at 16:10 -0800, Darren Hart wrote: > > > Leave those pr_ messages alone, please, [] > Andy and Henrique raised a few reasons why these patches should not be > accepted: > > 1. This is init code (so any space savings is short lived) Not exactly true. The object code itself is

Re: platform/x86/thinkpad_acpi: Adjustments for four function implementations

On Tue, 2018-01-02 at 16:10 -0800, Darren Hart wrote: > > > Leave those pr_ messages alone, please, [] > Andy and Henrique raised a few reasons why these patches should not be > accepted: > > 1. This is init code (so any space savings is short lived) Not exactly true. The object code itself is

[PATCH 4/7] PM / mfd: intel-lpss: Use DPM_FLAG_SMART_SUSPEND

From: Rafael J. Wysocki Make the intel-lpss driver set DPM_FLAG_SMART_SUSPEND for its devices which will allow them to stay in runtime suspend during system suspend unless they need to be reconfigured for some reason. Also make it avoid resuming its child devices if

[PATCH 4/7] PM / mfd: intel-lpss: Use DPM_FLAG_SMART_SUSPEND

From: Rafael J. Wysocki Make the intel-lpss driver set DPM_FLAG_SMART_SUSPEND for its devices which will allow them to stay in runtime suspend during system suspend unless they need to be reconfigured for some reason. Also make it avoid resuming its child devices if they have

Re: [PATCH -V4 -mm] mm, swap: Fix race between swapoff and some swap operations

Mel Gorman writes: > On Tue, Jan 02, 2018 at 12:29:55PM +0100, Jan Kara wrote: >> On Tue 02-01-18 10:21:03, Mel Gorman wrote: >> > On Sat, Dec 23, 2017 at 10:36:53AM +0900, Minchan Kim wrote: >> > > > code path. It appears that similar situation is possible for them

Re: [PATCH -V4 -mm] mm, swap: Fix race between swapoff and some swap operations

Mel Gorman writes: > On Tue, Jan 02, 2018 at 12:29:55PM +0100, Jan Kara wrote: >> On Tue 02-01-18 10:21:03, Mel Gorman wrote: >> > On Sat, Dec 23, 2017 at 10:36:53AM +0900, Minchan Kim wrote: >> > > > code path. It appears that similar situation is possible for them too. >> > > > >> > > > The

[PATCH 3/7] PM / core: Direct DPM_FLAG_LEAVE_SUSPENDED handling

From: Rafael J. Wysocki Make the PM core handle DPM_FLAG_LEAVE_SUSPENDED directly for devices whose "noirq", "late" and "early" driver callbacks are invoked directly by it. Namely, make it skip all of the system-wide resume callbacks for such devices with

[PATCH 3/7] PM / core: Direct DPM_FLAG_LEAVE_SUSPENDED handling

From: Rafael J. Wysocki Make the PM core handle DPM_FLAG_LEAVE_SUSPENDED directly for devices whose "noirq", "late" and "early" driver callbacks are invoked directly by it. Namely, make it skip all of the system-wide resume callbacks for such devices with DPM_FLAG_LEAVE_SUSPENDED set if (1)

[PATCH 7/7] PCI / PM: Use SMART_SUSPEND and LEAVE_SUSPENDED flags for PCIe ports

From: Rafael J. Wysocki Make the PCIe port driver set DPM_FLAG_SMART_SUSPEND and DPM_FLAG_LEAVE_SUSPENDED for the devices handled by it to benefit from the opportunistic optimizations in the PCI layer enabled by these flags. Signed-off-by: Rafael J. Wysocki

[PATCH 7/7] PCI / PM: Use SMART_SUSPEND and LEAVE_SUSPENDED flags for PCIe ports

From: Rafael J. Wysocki Make the PCIe port driver set DPM_FLAG_SMART_SUSPEND and DPM_FLAG_LEAVE_SUSPENDED for the devices handled by it to benefit from the opportunistic optimizations in the PCI layer enabled by these flags. Signed-off-by: Rafael J. Wysocki --- drivers/pci/pcie/portdrv_pci.c

[PATCH 2/7] PM / core: Direct DPM_FLAG_SMART_SUSPEND optimization

From: Rafael J. Wysocki Make the PM core avoid invoking the "late" and "noirq" system-wide suspend (or analogous) callbacks provided by device drivers directly for devices with DPM_FLAG_SMART_SUSPEND set that are in runtime suspend during the "late" and "noirq" phases

[PATCH 2/7] PM / core: Direct DPM_FLAG_SMART_SUSPEND optimization

From: Rafael J. Wysocki Make the PM core avoid invoking the "late" and "noirq" system-wide suspend (or analogous) callbacks provided by device drivers directly for devices with DPM_FLAG_SMART_SUSPEND set that are in runtime suspend during the "late" and "noirq" phases of system-wide suspend (or

[PATCH 1/7] PM / core: Add helpers for subsystem callback selection

From: Rafael J. Wysocki Add helper routines to find and return a suitable subsystem callback during the "noirq" phases of system suspend/resume (or analogous) transitions as well as during the "late" phase of system suspend and the "early" phase of system resume (or

[PATCH 1/7] PM / core: Add helpers for subsystem callback selection

From: Rafael J. Wysocki Add helper routines to find and return a suitable subsystem callback during the "noirq" phases of system suspend/resume (or analogous) transitions as well as during the "late" phase of system suspend and the "early" phase of system resume (or analogous) transitions. The

[PATCH 5/7] PM: i2c-designware-platdrv: Use DPM_FLAG_SMART_PREPARE

From: Rafael J. Wysocki Modify i2c-designware-platdrv to set DPM_FLAG_SMART_PREPARE for its devices and return 0 from the system suspend ->prepare callback if the device has an ACPI companion object in order to tell the PM core and middle layers to avoid skipping

[PATCH 5/7] PM: i2c-designware-platdrv: Use DPM_FLAG_SMART_PREPARE

From: Rafael J. Wysocki Modify i2c-designware-platdrv to set DPM_FLAG_SMART_PREPARE for its devices and return 0 from the system suspend ->prepare callback if the device has an ACPI companion object in order to tell the PM core and middle layers to avoid skipping system suspend/resume callbacks

<    1   2   3   4   5   6   7   8   9   10   >