Re: [RFC v2 00/13] usb/mmc/power: Fix USB/LAN when TFTP booting

On Thu, May 05, 2016 at 05:42:40PM -0500, Rob Herring wrote: > On Thu, May 05, 2016 at 02:34:13PM +0200, Krzysztof Kozlowski wrote: > > Hi, > > > > This is a different, second try to fix usb3503+lan on Odroid U3 board > > if it was initialized by bootloader (e.g. for TFTP boot). > > > > First

Re: [RFC v2 00/13] usb/mmc/power: Fix USB/LAN when TFTP booting

On Thu, May 05, 2016 at 05:42:40PM -0500, Rob Herring wrote: > On Thu, May 05, 2016 at 02:34:13PM +0200, Krzysztof Kozlowski wrote: > > Hi, > > > > This is a different, second try to fix usb3503+lan on Odroid U3 board > > if it was initialized by bootloader (e.g. for TFTP boot). > > > > First

Re: [PATCH 1/2] usb: configfs: allow UDC binding rule configured as binding to *any* UDC

On 05/06/2016 04:46 AM, Du, Changbin wrote: (...) >> Well, I'm not sure if any configfs interface has been proposed as easy >> to use from cmd line. I think they all has been proposed as *usable* >> from cmd line but not necessarily *easy to use*. >> >> That's why most of configfs clients has

Re: [PATCH 1/2] usb: configfs: allow UDC binding rule configured as binding to *any* UDC

On 05/06/2016 04:46 AM, Du, Changbin wrote: (...) >> Well, I'm not sure if any configfs interface has been proposed as easy >> to use from cmd line. I think they all has been proposed as *usable* >> from cmd line but not necessarily *easy to use*. >> >> That's why most of configfs clients has

Re: linux-next: build failure after merge of the akpm-current tree

On Fri, 6 May 2016 14:58:10 +1000 Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (and a > few earlier ones) (powerpc allnoconfig (and many others)) failed like > this: > > lib/vsprintf.c:160:2: error: initializer

Re: linux-next: build failure after merge of the akpm-current tree

On Fri, 6 May 2016 14:58:10 +1000 Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (and a > few earlier ones) (powerpc allnoconfig (and many others)) failed like > this: > > lib/vsprintf.c:160:2: error: initializer element is not constant

linux-next: Tree for May 6

Hi all, Changes since 20160505: Dropped tree: hsi (at the maintainer's request) The sound-asoc tree gained a build failure for which I applied a fix patch. I fetched and remerged the arm-current and arm trees at Russell's request. The akpm-current tree gained a build failure for which I

linux-next: Tree for May 6

Hi all, Changes since 20160505: Dropped tree: hsi (at the maintainer's request) The sound-asoc tree gained a build failure for which I applied a fix patch. I fetched and remerged the arm-current and arm trees at Russell's request. The akpm-current tree gained a build failure for which I

[PATCH v5 2/2] Input: SiS 9200 documentation parts.

From: Mika Penttilä Signed-off-by: Mika Penttilä Acked-by: Tammy Tseng Acked-by: Yuger Yu --- .../bindings/input/touchscreen/sis_i2c.txt | 22 ++

[PATCH v5 2/2] Input: SiS 9200 documentation parts.

From: Mika Penttilä Signed-off-by: Mika Penttilä Acked-by: Tammy Tseng Acked-by: Yuger Yu --- .../bindings/input/touchscreen/sis_i2c.txt | 22 ++ .../devicetree/bindings/vendor-prefixes.txt| 1 + 2 files changed, 23 insertions(+) create mode 100644

[PATCH v5 1/2] Input: Driver for SiS 9200 family I2C touchscreen controller.

From: Mika Penttilä Multitouch protocol B support. v5: - rebased to 4.6.0-rc6 v4: - cleanups and fixes according to review feedback - irq and reset gpios are now optional, if not spesified it is expected the firmware / hw takes care of reset states and

[PATCH v5 1/2] Input: Driver for SiS 9200 family I2C touchscreen controller.

From: Mika Penttilä Multitouch protocol B support. v5: - rebased to 4.6.0-rc6 v4: - cleanups and fixes according to review feedback - irq and reset gpios are now optional, if not spesified it is expected the firmware / hw takes care of reset states and irq flow - irq and reset

[PATCH v5 0/2] Input: SiS 9200 family I2C touchscreen controller driver

Hi, Here are the v5 patches for SiS 9200 I2C multitouch controller. All the issues raised so far are addressed in this version. Rebased on 4.6.0-rc6. Thanks, Mika [PATCH v5 1/2] Input: Driver for SiS 9200 family I2C touchscreen controller. [PATCH v5 2/2] Input: SiS 9200 documentation parts.

[PATCH v5 0/2] Input: SiS 9200 family I2C touchscreen controller driver

Hi, Here are the v5 patches for SiS 9200 I2C multitouch controller. All the issues raised so far are addressed in this version. Rebased on 4.6.0-rc6. Thanks, Mika [PATCH v5 1/2] Input: Driver for SiS 9200 family I2C touchscreen controller. [PATCH v5 2/2] Input: SiS 9200 documentation parts.

linux-next: build failure after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (and a few earlier ones) (powerpc allnoconfig (and many others)) failed like this: lib/vsprintf.c:160:2: error: initializer element is not constant lib/vsprintf.c:160:2: error: (near initialization for 'decpair[0]')

linux-next: build failure after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (and a few earlier ones) (powerpc allnoconfig (and many others)) failed like this: lib/vsprintf.c:160:2: error: initializer element is not constant lib/vsprintf.c:160:2: error: (near initialization for 'decpair[0]')

Re: [PATCH v7 6/9] i2c: rk3x: Move spec timing data to "static const" structs

Hi Doug, 在 2016/5/6 6:58, Doug Anderson 写道: David, On Wed, May 4, 2016 at 7:34 AM, David Wu wrote: Signed-off-by: David Wu As you can probably guess, again a description would be nice. Like maybe: The i2c timing specs are really just

Re: [PATCH v7 6/9] i2c: rk3x: Move spec timing data to "static const" structs

Hi Doug, 在 2016/5/6 6:58, Doug Anderson 写道: David, On Wed, May 4, 2016 at 7:34 AM, David Wu wrote: Signed-off-by: David Wu As you can probably guess, again a description would be nice. Like maybe: The i2c timing specs are really just constant data. There's no reason to write code to

Re: [PATCH] Coccinelle: noderef: Add a rule and correct the old rule

On Friday 06 May 2016 01:40 AM, Julia Lawall wrote: > > > On Wed, 27 Apr 2016, Vaishali Thakkar wrote: > >> Add a new rule to detect the cases where sizeof is used as a >> subexpression rather than a top level argument. >> >> Also, for the patch mode third rule should behave same as >> second

Re: [PATCH] Coccinelle: noderef: Add a rule and correct the old rule

On Friday 06 May 2016 01:40 AM, Julia Lawall wrote: > > > On Wed, 27 Apr 2016, Vaishali Thakkar wrote: > >> Add a new rule to detect the cases where sizeof is used as a >> subexpression rather than a top level argument. >> >> Also, for the patch mode third rule should behave same as >> second

Re: [PATCH 3/3] regulator: lp873x: Add support for lp873x PMIC regulators

Hi Mark, On Thursday 05 May 2016 09:08 PM, Mark Brown wrote: On Thu, May 05, 2016 at 10:40:40AM +0530, Keerthy wrote: +static const struct of_device_id of_lp873x_match_tbl[] = { + { .compatible = "ti,lp8733-regulators",}, + { .compatible = "ti,lp8732-regulators",}, + {

Re: [PATCH 3/3] regulator: lp873x: Add support for lp873x PMIC regulators

Hi Mark, On Thursday 05 May 2016 09:08 PM, Mark Brown wrote: On Thu, May 05, 2016 at 10:40:40AM +0530, Keerthy wrote: +static const struct of_device_id of_lp873x_match_tbl[] = { + { .compatible = "ti,lp8733-regulators",}, + { .compatible = "ti,lp8732-regulators",}, + {

Re: [PATCH] mm/zsmalloc: avoid unnecessary iteration in get_pages_per_zspage()

Hi Ganesh, On Fri, May 06, 2016 at 12:25:18PM +0800, Ganesh Mahendran wrote: > Hi, Minchan: > > 2016-05-06 11:09 GMT+08:00 Minchan Kim : > > On Thu, May 05, 2016 at 07:03:29PM +0900, Sergey Senozhatsky wrote: > >> On (05/05/16 13:17), Ganesh Mahendran wrote: > >> > if we find

Re: [PATCH] mm/zsmalloc: avoid unnecessary iteration in get_pages_per_zspage()

Hi Ganesh, On Fri, May 06, 2016 at 12:25:18PM +0800, Ganesh Mahendran wrote: > Hi, Minchan: > > 2016-05-06 11:09 GMT+08:00 Minchan Kim : > > On Thu, May 05, 2016 at 07:03:29PM +0900, Sergey Senozhatsky wrote: > >> On (05/05/16 13:17), Ganesh Mahendran wrote: > >> > if we find a zspage with usage

[git pull] drm fixes

Hi Linus, Fixes for i915, amdgpu/radeon and imx. The IMX fix is for an autoloading regression found in Fedora. The radeon fixes, are the same fix to amdgpu/radeon to avoid a hardware lockup in some circumstances with a bad mode, and a double free bug I took a few hours chasing down the other

[git pull] drm fixes

Hi Linus, Fixes for i915, amdgpu/radeon and imx. The IMX fix is for an autoloading regression found in Fedora. The radeon fixes, are the same fix to amdgpu/radeon to avoid a hardware lockup in some circumstances with a bad mode, and a double free bug I took a few hours chasing down the other

Re: [PATCH] mm/zsmalloc: avoid unnecessary iteration in get_pages_per_zspage()

Hi, Minchan: 2016-05-06 11:09 GMT+08:00 Minchan Kim : > On Thu, May 05, 2016 at 07:03:29PM +0900, Sergey Senozhatsky wrote: >> On (05/05/16 13:17), Ganesh Mahendran wrote: >> > if we find a zspage with usage == 100%, there is no need to >> > try other zspages. >> >> Hello, >>

Re: [PATCH] mm/zsmalloc: avoid unnecessary iteration in get_pages_per_zspage()

Hi, Minchan: 2016-05-06 11:09 GMT+08:00 Minchan Kim : > On Thu, May 05, 2016 at 07:03:29PM +0900, Sergey Senozhatsky wrote: >> On (05/05/16 13:17), Ganesh Mahendran wrote: >> > if we find a zspage with usage == 100%, there is no need to >> > try other zspages. >> >> Hello, >> >> well... we

Re: [PATCH v11 04/60] sparc/PCI: Use correct offset for bus address to resource

On Thu, May 5, 2016 at 5:56 PM, Yinghai Lu wrote: > On Thu, May 5, 2016 at 3:02 PM, Benjamin Herrenschmidt > wrote: >> On Thu, 2016-05-05 at 08:53 -0700, Yinghai Lu wrote: >>> For powerpc io port, we still need extra offset from resource address >>>

Re: [PATCH v11 04/60] sparc/PCI: Use correct offset for bus address to resource

On Thu, May 5, 2016 at 5:56 PM, Yinghai Lu wrote: > On Thu, May 5, 2016 at 3:02 PM, Benjamin Herrenschmidt > wrote: >> On Thu, 2016-05-05 at 08:53 -0700, Yinghai Lu wrote: >>> For powerpc io port, we still need extra offset from resource address >>> to final address. >>> >>> resource_size_t

RE: [PATCH 2/2] drivers: i2c: qup: Fix error handling

Hi Andy, > -Original Message- > From: Andy Gross [mailto:andy.gr...@linaro.org] > Sent: Thursday, May 05, 2016 10:52 PM > To: Sricharan R > Cc: devicet...@vger.kernel.org; arch...@codeaurora.org; linux-arm- > m...@vger.kernel.org; ntel...@codeaurora.org;

RE: [PATCH 2/2] drivers: i2c: qup: Fix error handling

Hi Andy, > -Original Message- > From: Andy Gross [mailto:andy.gr...@linaro.org] > Sent: Thursday, May 05, 2016 10:52 PM > To: Sricharan R > Cc: devicet...@vger.kernel.org; arch...@codeaurora.org; linux-arm- > m...@vger.kernel.org; ntel...@codeaurora.org; ga...@codeaurora.org; >

Re: [PATCH] mfd: lp873x: Add lp873x PMIC support

On Thursday 05 May 2016 02:05 PM, Manish Badarkhe wrote: Hi Keerthy, + * struct tps65086 - state holder for the tps65086 driver need to change name over here in comment. Thanks for catching this Manish! I will fix it in the next version. + * Device data may be used to access the

Re: [PATCH] mfd: lp873x: Add lp873x PMIC support

On Thursday 05 May 2016 02:05 PM, Manish Badarkhe wrote: Hi Keerthy, + * struct tps65086 - state holder for the tps65086 driver need to change name over here in comment. Thanks for catching this Manish! I will fix it in the next version. + * Device data may be used to access the

[PATCH v2] ksm: fix conflict between mmput and scan_get_next_rmap_item

A concurrency issue about KSM in the function scan_get_next_rmap_item. task A (ksmd): |task B (the mm's task): | mm = slot->mm; | down_read(>mmap_sem); |

[PATCH v2] ksm: fix conflict between mmput and scan_get_next_rmap_item

A concurrency issue about KSM in the function scan_get_next_rmap_item. task A (ksmd): |task B (the mm's task): | mm = slot->mm; | down_read(>mmap_sem); |

[PATCH] x86, tsc: Fix tsc ratio calibration to avoid broken mdelay

From: Chen Yu Currently we fetch the tsc radio by: ratio = (lo >> 8) & 0x1f; thus get bit8~bit12 of the MSR_PLATFORM_INFO, however according to Intel 64 and IA-32 Architectures Software Developer Manual 35.5, the ratio bit should be bit8~bit15, otherwise we might get

[PATCH] x86, tsc: Fix tsc ratio calibration to avoid broken mdelay

From: Chen Yu Currently we fetch the tsc radio by: ratio = (lo >> 8) & 0x1f; thus get bit8~bit12 of the MSR_PLATFORM_INFO, however according to Intel 64 and IA-32 Architectures Software Developer Manual 35.5, the ratio bit should be bit8~bit15, otherwise we might get incorrect tsc ratio and

Re: [PATCH 0/2] scop GFP_NOFS api

On Wed, May 04 2016, Dave Chinner wrote: > FWIW, I don't think making evict() non-blocking is going to be worth > the effort here. Making memory reclaim wait on a priority ordered > queue while asynchronous reclaim threads run reclaim as efficiently > as possible and wakes waiters as it frees the

Re: [PATCH 0/2] scop GFP_NOFS api

On Wed, May 04 2016, Dave Chinner wrote: > FWIW, I don't think making evict() non-blocking is going to be worth > the effort here. Making memory reclaim wait on a priority ordered > queue while asynchronous reclaim threads run reclaim as efficiently > as possible and wakes waiters as it frees the

Re: [PATCH v7 4/9] i2c: rk3x: Move setting STATE_START and add STATE_SETUP

Hi Doug, 在 2016/5/6 6:56, Doug Anderson 写道: David, On Wed, May 4, 2016 at 7:13 AM, David Wu wrote: Signed-off-by: David Wu --- Change in v7: - none drivers/i2c/busses/i2c-rk3x.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-)

Re: [PATCH v7 4/9] i2c: rk3x: Move setting STATE_START and add STATE_SETUP

Hi Doug, 在 2016/5/6 6:56, Doug Anderson 写道: David, On Wed, May 4, 2016 at 7:13 AM, David Wu wrote: Signed-off-by: David Wu --- Change in v7: - none drivers/i2c/busses/i2c-rk3x.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) Probably this change could be dropped now.

Re: [PATCH] mm/zsmalloc: avoid unnecessary iteration in get_pages_per_zspage()

On Thu, May 05, 2016 at 07:03:29PM +0900, Sergey Senozhatsky wrote: > On (05/05/16 13:17), Ganesh Mahendran wrote: > > if we find a zspage with usage == 100%, there is no need to > > try other zspages. > > Hello, > > well... we iterate there from 0 to 1<<2, which is not awfully > a lot to break

Re: [PATCH] mm/zsmalloc: avoid unnecessary iteration in get_pages_per_zspage()

On Thu, May 05, 2016 at 07:03:29PM +0900, Sergey Senozhatsky wrote: > On (05/05/16 13:17), Ganesh Mahendran wrote: > > if we find a zspage with usage == 100%, there is no need to > > try other zspages. > > Hello, > > well... we iterate there from 0 to 1<<2, which is not awfully > a lot to break

Re: [PATCH] ksm: fix conflict between mmput and scan_get_next_rmap_item

On 2016/5/6 5:57, Andrea Arcangeli wrote: Hello Zhou, Great catch. On Thu, May 05, 2016 at 08:42:56PM +0800, Zhou Chengming wrote: remove_trailing_rmap_items(slot, ksm_scan.rmap_list); + up_read(>mmap_sem); spin_lock(_mmlist_lock); ksm_scan.mm_slot =

Re: [PATCH] ksm: fix conflict between mmput and scan_get_next_rmap_item

On 2016/5/6 5:57, Andrea Arcangeli wrote: Hello Zhou, Great catch. On Thu, May 05, 2016 at 08:42:56PM +0800, Zhou Chengming wrote: remove_trailing_rmap_items(slot, ksm_scan.rmap_list); + up_read(>mmap_sem); spin_lock(_mmlist_lock); ksm_scan.mm_slot =

Re: [PATCH] ksm: fix conflict between mmput and scan_get_next_rmap_item

Good Catch. The original code looks too old, use the ksm_mmlist_lock to protect the mm_list looks will affect the performance, Should we use the RCU to protect the list and not free the mm until out of the rcu critical period? On 2016/5/6 5:57, Andrea Arcangeli wrote: > Hello Zhou, > >

Re: [PATCH] ksm: fix conflict between mmput and scan_get_next_rmap_item

Good Catch. The original code looks too old, use the ksm_mmlist_lock to protect the mm_list looks will affect the performance, Should we use the RCU to protect the list and not free the mm until out of the rcu critical period? On 2016/5/6 5:57, Andrea Arcangeli wrote: > Hello Zhou, > >

Re: [PATCH] ksm: fix conflict between mmput and scan_get_next_rmap_item

On 2016/5/6 5:07, Andrew Morton wrote: On Thu, 5 May 2016 20:42:56 +0800 Zhou Chengming wrote: A concurrency issue about KSM in the function scan_get_next_rmap_item. task A (ksmd): |task B (the mm's task):

Re: [PATCH] ksm: fix conflict between mmput and scan_get_next_rmap_item

On 2016/5/6 5:07, Andrew Morton wrote: On Thu, 5 May 2016 20:42:56 +0800 Zhou Chengming wrote: A concurrency issue about KSM in the function scan_get_next_rmap_item. task A (ksmd): |task B (the mm's task): | mm = slot->mm;

Re: [RFC v2 PATCH 0/8] VFS:userns: support portable root filesystems

On Thu, May 05, 2016 at 11:24:35PM +0100, Djalal Harouni wrote: > On Thu, May 05, 2016 at 10:23:14AM +1000, Dave Chinner wrote: > > On Wed, May 04, 2016 at 04:26:46PM +0200, Djalal Harouni wrote: > > > This is version 2 of the VFS:userns support portable root filesystems > > > RFC. Changes since

Re: [RFC v2 PATCH 0/8] VFS:userns: support portable root filesystems

On Thu, May 05, 2016 at 11:24:35PM +0100, Djalal Harouni wrote: > On Thu, May 05, 2016 at 10:23:14AM +1000, Dave Chinner wrote: > > On Wed, May 04, 2016 at 04:26:46PM +0200, Djalal Harouni wrote: > > > This is version 2 of the VFS:userns support portable root filesystems > > > RFC. Changes since

Re: [PATCH] ION: Sys_heap: Makes ion buffer always alloc from page pool

On 2016/5/6 1:09, Laura Abbott wrote: > On 05/04/2016 08:27 PM, Chen Feng wrote: >> Makes the ion buffer always alloced from page pool, no matter >> it's cached or not. In this way, it can improve the efficiency >> of it. >> >> Currently, there is no difference from cached or non-cached buffer

Re: [PATCH] ION: Sys_heap: Makes ion buffer always alloc from page pool

On 2016/5/6 1:09, Laura Abbott wrote: > On 05/04/2016 08:27 PM, Chen Feng wrote: >> Makes the ion buffer always alloced from page pool, no matter >> it's cached or not. In this way, it can improve the efficiency >> of it. >> >> Currently, there is no difference from cached or non-cached buffer

RE: [PATCH 1/2] usb: configfs: allow UDC binding rule configured as binding to *any* UDC

> >>> On most platforms, there is only one device controller available. > >>> In this case, we desn't care the UDC's name. So let's ignore the > >>> name by setting 'UDC' to 'any'. > >> > >> Hmm libubsgx allows to do this for a very long time. You simply pass > >> NULL instead of pointer to

RE: [PATCH 1/2] usb: configfs: allow UDC binding rule configured as binding to *any* UDC

> >>> On most platforms, there is only one device controller available. > >>> In this case, we desn't care the UDC's name. So let's ignore the > >>> name by setting 'UDC' to 'any'. > >> > >> Hmm libubsgx allows to do this for a very long time. You simply pass > >> NULL instead of pointer to

Re: [RESEND Patch] jbd2: remove excess descriptions for handle_s

On Mon, Apr 11, 2016 at 12:44:16PM +0100, Luis de Bethencourt wrote: > Commit bf6993276f74 ("jbd2: Use tracepoints for history file") > removed the members j_history, j_history_max and j_history_cur from struct > handle_s but the descriptions stayed lingering. Removing them. > > Signed-off-by:

Re: [RESEND Patch] jbd2: remove excess descriptions for handle_s

On Mon, Apr 11, 2016 at 12:44:16PM +0100, Luis de Bethencourt wrote: > Commit bf6993276f74 ("jbd2: Use tracepoints for history file") > removed the members j_history, j_history_max and j_history_cur from struct > handle_s but the descriptions stayed lingering. Removing them. > > Signed-off-by:

Re: [PATCH] usb: gadget: f_fs: Fix kernel panic for SuperSpeed

On 2016年05月04日 18:37, Felipe Balbi wrote: * PGP Signed by an unknown key Hi, Jim Lin writes: In f_fs.c " static int __ffs_data_do_os_desc(enum ffs_os_desc_type type, struct usb_os_desc_header *h, void *data, unsigned len, void

Re: [PATCH] usb: gadget: f_fs: Fix kernel panic for SuperSpeed

On 2016年05月04日 18:37, Felipe Balbi wrote: * PGP Signed by an unknown key Hi, Jim Lin writes: In f_fs.c " static int __ffs_data_do_os_desc(enum ffs_os_desc_type type, struct usb_os_desc_header *h, void *data, unsigned len, void *priv) {

Re: UB in general ... and linux/bitops.h in particular

>-- Perhaps the compiler guys could be persuaded to support > the needed features explicitly, perhaps via a command-line > option: -std=vanilla > This should be a no-cost option as things stand today, but > it helps to prevent nasty surprises in the future. It looks LLVM has

Re: UB in general ... and linux/bitops.h in particular

>-- Perhaps the compiler guys could be persuaded to support > the needed features explicitly, perhaps via a command-line > option: -std=vanilla > This should be a no-cost option as things stand today, but > it helps to prevent nasty surprises in the future. It looks LLVM has

Re: [PATCH v7 2/9] i2c: rk3x: use struct "rk3x_i2c_calced_timings"

Hi Doug, 在 2016/5/6 6:55, Doug Anderson 写道: David, On Wed, May 4, 2016 at 7:13 AM, David Wu wrote: Signed-off-by: David Wu Usually folks like a description and not just a subject line. I'd add a description like: The "div_high" and

Re: [PATCH v7 2/9] i2c: rk3x: use struct "rk3x_i2c_calced_timings"

Hi Doug, 在 2016/5/6 6:55, Doug Anderson 写道: David, On Wed, May 4, 2016 at 7:13 AM, David Wu wrote: Signed-off-by: David Wu Usually folks like a description and not just a subject line. I'd add a description like: The "div_high" and "div_low" values are always used together. Group them

Re: [PATCH] kbuild: fix if_change and friends to consider argument order

Hi David, 2016-05-05 17:08 GMT+09:00 Woodhouse, David : > On Thu, 2016-05-05 at 16:45 +0900, Masahiro Yamada wrote: >> >> This commit fixes arg-check to compare two strings as a whole. >> $(strip ...) is important because we want to ignore the difference >> that comes

Re: [PATCH] kbuild: fix if_change and friends to consider argument order

Hi David, 2016-05-05 17:08 GMT+09:00 Woodhouse, David : > On Thu, 2016-05-05 at 16:45 +0900, Masahiro Yamada wrote: >> >> This commit fixes arg-check to compare two strings as a whole. >> $(strip ...) is important because we want to ignore the difference >> that comes from white-spaces. > > Do

Re: [PATCH v7 9/9] i2c: rk3x: support fast-mode plus for rk3399

Hi Doug, 在 2016/5/6 7:02, Doug Anderson 写道: David, On Wed, May 4, 2016 at 7:37 AM, David Wu wrote: Signed-off-by: David Wu --- drivers/i2c/busses/i2c-rk3x.c | 21 + 1 file changed, 17 insertions(+), 4 deletions(-)

Re: [PATCH v7 9/9] i2c: rk3x: support fast-mode plus for rk3399

Hi Doug, 在 2016/5/6 7:02, Doug Anderson 写道: David, On Wed, May 4, 2016 at 7:37 AM, David Wu wrote: Signed-off-by: David Wu --- drivers/i2c/busses/i2c-rk3x.c | 21 + 1 file changed, 17 insertions(+), 4 deletions(-) diff --git a/drivers/i2c/busses/i2c-rk3x.c

Re: [PATCH v3 03/12] sched/fair: Change the variable to hold the number of periods to 32bit

Hi Morten, On Thu, May 05, 2016 at 12:13:10PM +0100, Morten Rasmussen wrote: > On Wed, May 04, 2016 at 04:02:44AM +0800, Yuyang Du wrote: > > In sched average update, a period is about 1ms, so a 32-bit unsigned > > integer can approximately hold a maximum of 49 (=2^32/1000/3600/24) > > days. > >

Re: [PATCH v3 03/12] sched/fair: Change the variable to hold the number of periods to 32bit

Hi Morten, On Thu, May 05, 2016 at 12:13:10PM +0100, Morten Rasmussen wrote: > On Wed, May 04, 2016 at 04:02:44AM +0800, Yuyang Du wrote: > > In sched average update, a period is about 1ms, so a 32-bit unsigned > > integer can approximately hold a maximum of 49 (=2^32/1000/3600/24) > > days. > >

Re: [RFC][PATCH 0/6] Enhanced file stat system call

On Thu, May 5, 2016 at 5:54 PM, Steve French wrote: > On Wed, May 4, 2016 at 8:46 AM, Arnd Bergmann wrote: >> On Friday 29 April 2016 13:57:36 David Howells wrote: >>> struct statx *buffer); >>> >>> This is an enhanced file stat function that provides a number

Re: [RFC][PATCH 0/6] Enhanced file stat system call

On Thu, May 5, 2016 at 5:54 PM, Steve French wrote: > On Wed, May 4, 2016 at 8:46 AM, Arnd Bergmann wrote: >> On Friday 29 April 2016 13:57:36 David Howells wrote: >>> struct statx *buffer); >>> >>> This is an enhanced file stat function that provides a number of useful >>> features, in summary:

Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available

On Thu, May 05, 2016 at 09:04:09PM +0100, David Howells wrote: > Jeff Layton wrote: > > > I don't see a real attack vector here either, but OTOH is there a > > potential user of this at the moment? > > I'm not sure. BSD stat has an st_gen, so it's possible something

Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available

On Thu, May 05, 2016 at 09:04:09PM +0100, David Howells wrote: > Jeff Layton wrote: > > > I don't see a real attack vector here either, but OTOH is there a > > potential user of this at the moment? > > I'm not sure. BSD stat has an st_gen, so it's possible something out there > will use it if

Re: [PATCH] efi/capsule: Make efi_capsule_pending() lockless

On Thu, 2016-05-05 at 14:27 +, Kweh, Hock Leong wrote: > > -Original Message- > > From: Matt Fleming [mailto:m...@codeblueprint.co.uk] > > Sent: Wednesday, May 04, 2016 10:36 PM > > To: Kweh, Hock Leong; Bryan O'Donoghue > > Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;

Re: [PATCH] efi/capsule: Make efi_capsule_pending() lockless

On Thu, 2016-05-05 at 14:27 +, Kweh, Hock Leong wrote: > > -Original Message- > > From: Matt Fleming [mailto:m...@codeblueprint.co.uk] > > Sent: Wednesday, May 04, 2016 10:36 PM > > To: Kweh, Hock Leong; Bryan O'Donoghue > > Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;

[lkp] [string_helpers] 726ecfc321: test_string_helpers: Test 'test_string_get_size_one' failed!

FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y commit 726ecfc321994ec6ab044c1e3e5886408de991ac ("string_helpers: fix precision loss for some inputs") on test machine: vm-kbuild-yocto-i386: 2 threads qemu-system-i386

[lkp] [string_helpers] 726ecfc321: test_string_helpers: Test 'test_string_get_size_one' failed!

FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y commit 726ecfc321994ec6ab044c1e3e5886408de991ac ("string_helpers: fix precision loss for some inputs") on test machine: vm-kbuild-yocto-i386: 2 threads qemu-system-i386

Re: [RFC PATCH net-next 20/20] net: dsa: mv88e6xxx: factorize the switch driver

> +config NET_DSA_MV88E6XXX > tristate "Marvell 88E6085/6095/6095F/6131 ethernet switch chip support" > depends on NET_DSA > - select NET_DSA_MV88E6XXX > select NET_DSA_TAG_EDSA > ---help--- > This enables support for the Marvell 88E6085/6095/6095F/6131 >

Re: [PATCH kernel v4 10/11] powerpc/powernv/npu: Rework TCE Kill handling

On Thu, 5 May 2016 14:23:20 Alexey Kardashevskiy wrote: > On 05/03/2016 05:37 PM, Alistair Popple wrote: > > On Fri, 29 Apr 2016 18:55:23 Alexey Kardashevskiy wrote: > >> The pnv_ioda_pe struct keeps an array of peers. At the moment it is only > >> used to link GPU and NPU for 2 purposes: > >> >

Re: [RFC PATCH net-next 20/20] net: dsa: mv88e6xxx: factorize the switch driver

> +config NET_DSA_MV88E6XXX > tristate "Marvell 88E6085/6095/6095F/6131 ethernet switch chip support" > depends on NET_DSA > - select NET_DSA_MV88E6XXX > select NET_DSA_TAG_EDSA > ---help--- > This enables support for the Marvell 88E6085/6095/6095F/6131 >

Re: [PATCH kernel v4 10/11] powerpc/powernv/npu: Rework TCE Kill handling

On Thu, 5 May 2016 14:23:20 Alexey Kardashevskiy wrote: > On 05/03/2016 05:37 PM, Alistair Popple wrote: > > On Fri, 29 Apr 2016 18:55:23 Alexey Kardashevskiy wrote: > >> The pnv_ioda_pe struct keeps an array of peers. At the moment it is only > >> used to link GPU and NPU for 2 purposes: > >> >

Re: [PATCH v3 0/2] irqchip/mbigen: fix the IO remap problem in mbigen driver.

Hi Marc: 在 2016/5/5 22:49, Marc Zyngier 写道: > On 22/03/16 03:10, majun (F) wrote: >> >> >> 在 2016/3/21 18:29, Thomas Gleixner 写道: >>> On Thu, 17 Mar 2016, MaJun wrote: This patch set is used to fix the problem of remap a set of registers repeatedly in current mbigen driver.

Re: [PATCH v3 0/2] irqchip/mbigen: fix the IO remap problem in mbigen driver.

Hi Marc: 在 2016/5/5 22:49, Marc Zyngier 写道: > On 22/03/16 03:10, majun (F) wrote: >> >> >> 在 2016/3/21 18:29, Thomas Gleixner 写道: >>> On Thu, 17 Mar 2016, MaJun wrote: This patch set is used to fix the problem of remap a set of registers repeatedly in current mbigen driver.

Re: [RFC PATCH net-next 19/20] net: dsa: mv88e6xxx: factorize tag protocol

On Thu, May 05, 2016 at 06:41:03PM -0400, Vivien Didelot wrote: > 6131 is the only driver to set the tag protocol to DSA_TAG_PROTO_DSA. > Since it works fine with DSA_TAG_PROTO_EDSA, change its value, like all > other mv88e6xxx drivers. Hi Vivien You might as well remove net/dsa/tag_dsa.c as

Re: [RFC PATCH net-next 19/20] net: dsa: mv88e6xxx: factorize tag protocol

On Thu, May 05, 2016 at 06:41:03PM -0400, Vivien Didelot wrote: > 6131 is the only driver to set the tag protocol to DSA_TAG_PROTO_DSA. > Since it works fine with DSA_TAG_PROTO_EDSA, change its value, like all > other mv88e6xxx drivers. Hi Vivien You might as well remove net/dsa/tag_dsa.c as

Re: [PATCH kernel v4 11/11] powerpc/powernv/npu: Enable NVLink pass through

On Thu, 5 May 2016 15:49:18 Alexey Kardashevskiy wrote: > On 05/04/2016 12:08 AM, Alistair Popple wrote: > > Hi Alexey, > > > > On Fri, 29 Apr 2016 18:55:24 Alexey Kardashevskiy wrote: > >> IBM POWER8 NVlink systems come with Tesla K40-ish GPUs each of which > >> also has a couple of fast speed

Re: [PATCH kernel v4 11/11] powerpc/powernv/npu: Enable NVLink pass through

On Thu, 5 May 2016 15:49:18 Alexey Kardashevskiy wrote: > On 05/04/2016 12:08 AM, Alistair Popple wrote: > > Hi Alexey, > > > > On Fri, 29 Apr 2016 18:55:24 Alexey Kardashevskiy wrote: > >> IBM POWER8 NVlink systems come with Tesla K40-ish GPUs each of which > >> also has a couple of fast speed

[PATCH] ARM: dts: rk3288: add SPI flash node for veyron

This is a standard binding for describing SPI flash that can be identified by reading their JEDEC ID. Let's use it. Tested on Veyron Jaq. Signed-off-by: Brian Norris --- arch/arm/boot/dts/rk3288-veyron.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH] ARM: dts: rk3288: add SPI flash node for veyron

This is a standard binding for describing SPI flash that can be identified by reading their JEDEC ID. Let's use it. Tested on Veyron Jaq. Signed-off-by: Brian Norris --- arch/arm/boot/dts/rk3288-veyron.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git

Re: [PATCH] Input: synaptics-rmi4: Support regulator supplies

On Thu 05 May 13:55 PDT 2016, Andrew Duggan wrote: > Hi Bjorn, > > On 04/21/2016 03:37 PM, Bjorn Andersson wrote: [..] > >I see no (sane) way of waiting for the rmi_driver to finish probeing; > >there could be cases where it's powered by a regulator (or reset gpio) > >that is not yet probed.

Re: [PATCH] Input: synaptics-rmi4: Support regulator supplies

On Thu 05 May 13:55 PDT 2016, Andrew Duggan wrote: > Hi Bjorn, > > On 04/21/2016 03:37 PM, Bjorn Andersson wrote: [..] > >I see no (sane) way of waiting for the rmi_driver to finish probeing; > >there could be cases where it's powered by a regulator (or reset gpio) > >that is not yet probed.

Re: [RFC PATCH net-next 14/20] net: dsa: mv88e6xxx: factorize VLAN Ethertype

On Thu, May 05, 2016 at 06:40:58PM -0400, Vivien Didelot wrote: > Only the 6131 driver was setting the VLAN Ethertype to 0x8100. Set it to > all models. > > Signed-off-by: Vivien Didelot > --- > drivers/net/dsa/mv88e6131.c | 9 - >

Re: [RFC PATCH net-next 14/20] net: dsa: mv88e6xxx: factorize VLAN Ethertype

On Thu, May 05, 2016 at 06:40:58PM -0400, Vivien Didelot wrote: > Only the 6131 driver was setting the VLAN Ethertype to 0x8100. Set it to > all models. > > Signed-off-by: Vivien Didelot > --- > drivers/net/dsa/mv88e6131.c | 9 - > drivers/net/dsa/mv88e6xxx.c | 8 >

linux-next: build failure after merge of the sound-asoc tree

Hi all, After merging the sound-asoc tree, today's linux-next build (x86_64 allmodconfig) failed like this: sound/soc/codecs/da7219.c:1964:23: error: implicit declaration of function 'ACPI_PTR' [-Werror=implicit-function-declaration] .acpi_match_table = ACPI_PTR(da7219_acpi_match),

linux-next: build failure after merge of the sound-asoc tree

Hi all, After merging the sound-asoc tree, today's linux-next build (x86_64 allmodconfig) failed like this: sound/soc/codecs/da7219.c:1964:23: error: implicit declaration of function 'ACPI_PTR' [-Werror=implicit-function-declaration] .acpi_match_table = ACPI_PTR(da7219_acpi_match),

Re: [PATCH v11 04/60] sparc/PCI: Use correct offset for bus address to resource

On Thu, May 5, 2016 at 3:02 PM, Benjamin Herrenschmidt wrote: > On Thu, 2016-05-05 at 08:53 -0700, Yinghai Lu wrote: >> For powerpc io port, we still need extra offset from resource address >> to final address. >> >> resource_size_t offset = >>

Re: [PATCH RESEND] mtd: spi-nor: Add support for S3AN spi-nor devices

On Wed, Apr 27, 2016 at 03:14:22PM +0200, Ricardo Ribalda Delgado wrote: > Xilinx Spartan-3AN contain an embedded spi device where they keep their > configuration data and optionally some user data. > > The protocol of this flash follows most of the spi-nor standard. With > the following

Re: [PATCH v11 04/60] sparc/PCI: Use correct offset for bus address to resource

On Thu, May 5, 2016 at 3:02 PM, Benjamin Herrenschmidt wrote: > On Thu, 2016-05-05 at 08:53 -0700, Yinghai Lu wrote: >> For powerpc io port, we still need extra offset from resource address >> to final address. >> >> resource_size_t offset = >> ((resource_size_t)vma->vm_pgoff) <<

Re: [PATCH RESEND] mtd: spi-nor: Add support for S3AN spi-nor devices

On Wed, Apr 27, 2016 at 03:14:22PM +0200, Ricardo Ribalda Delgado wrote: > Xilinx Spartan-3AN contain an embedded spi device where they keep their > configuration data and optionally some user data. > > The protocol of this flash follows most of the spi-nor standard. With > the following

  1   2   3   4   5   6   7   8   9   10   >