Re: [PATCH v2 4/8] scripts: add glimpse.sh for indexing the kernel

On Sat, 18 Jun 2016, Luis R. Rodriguez wrote: > On Fri, Jun 17, 2016 at 05:35:26PM +0200, Julia Lawall wrote: > > On Fri, 17 Jun 2016, Luis R. Rodriguez wrote: > > > > > On Fri, Jun 17, 2016 at 11:44:26AM +0200, Julia Lawall wrote: > > > > I'm not sure that this is worth it. It adds a

Re: [PATCH v2 4/8] scripts: add glimpse.sh for indexing the kernel

On Sat, 18 Jun 2016, Luis R. Rodriguez wrote: > On Fri, Jun 17, 2016 at 05:35:26PM +0200, Julia Lawall wrote: > > On Fri, 17 Jun 2016, Luis R. Rodriguez wrote: > > > > > On Fri, Jun 17, 2016 at 11:44:26AM +0200, Julia Lawall wrote: > > > > I'm not sure that this is worth it. It adds a

[PATCH RESEND] trace: function graph: Fix filters for function_graph threshold

Function graph tracer currently ignores filters if tracing_thresh is set. For example, even if set_ftrace_pid is set, then its ignored if tracing_thresh set, resulting in all processes being traced. To fix this, we reuse the same entry function as when tracing_thresh is not set and do everything

[PATCH RESEND] trace: function graph: Fix filters for function_graph threshold

Function graph tracer currently ignores filters if tracing_thresh is set. For example, even if set_ftrace_pid is set, then its ignored if tracing_thresh set, resulting in all processes being traced. To fix this, we reuse the same entry function as when tracing_thresh is not set and do everything

Re: [PATCH 2/2] net: ethernet: et131x: use phy_ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Fri, 17 Jun 2016 23:32:15 +0200 > There are two generics functions phy_ethtool_{get|set}_link_ksettings, > so we can use them instead of defining the same code in the driver. > > Signed-off-by: Philippe Reynes Applied.

Re: [PATCH 2/2] net: ethernet: et131x: use phy_ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Fri, 17 Jun 2016 23:32:15 +0200 > There are two generics functions phy_ethtool_{get|set}_link_ksettings, > so we can use them instead of defining the same code in the driver. > > Signed-off-by: Philippe Reynes Applied.

Re: [PATCH 1/2] net: ethernet: et131x: use phydev from struct net_device

From: Philippe Reynes Date: Fri, 17 Jun 2016 23:32:14 +0200 > The private structure contain a pointer to phydev, but the structure > net_device already contain such pointer. So we can remove the pointer > phydev in the private structure, and update the driver to use the > one

Re: [PATCH 1/2] net: ethernet: et131x: use phydev from struct net_device

From: Philippe Reynes Date: Fri, 17 Jun 2016 23:32:14 +0200 > The private structure contain a pointer to phydev, but the structure > net_device already contain such pointer. So we can remove the pointer > phydev in the private structure, and update the driver to use the > one contained in struct

Re: Stable -rc git trees and email headers

Hi Greg, On Fri, Jun 17, 2016 at 08:16:20PM -0700, Greg KH wrote: > Hi, > > I've finally gotten off my butt and made my quilt trees of patches into > a "semi-proper" git tree to make it easier for people to test them. > > I'm now pushing the patches I accept into the stable queues into the git

Re: Stable -rc git trees and email headers

Hi Greg, On Fri, Jun 17, 2016 at 08:16:20PM -0700, Greg KH wrote: > Hi, > > I've finally gotten off my butt and made my quilt trees of patches into > a "semi-proper" git tree to make it easier for people to test them. > > I'm now pushing the patches I accept into the stable queues into the git

Re: [PATCH] net: tilegx: use correct timespec64 type

From: Arnd Bergmann Date: Fri, 17 Jun 2016 18:15:30 +0200 > The conversion to the 64-bit time based ptp methods left two instances > of 'struct timespec' in place. This is harmless because 64-bit > architectures define timespec64 as timespec, and this driver is > not used on

Re: [PATCH] net: tilegx: use correct timespec64 type

From: Arnd Bergmann Date: Fri, 17 Jun 2016 18:15:30 +0200 > The conversion to the 64-bit time based ptp methods left two instances > of 'struct timespec' in place. This is harmless because 64-bit > architectures define timespec64 as timespec, and this driver is > not used on 32-bit machines. >

Re: [very-RFC 0/8] TSN driver for the kernel

Hi, Sorry to be late. In this weekday, I have little time for this thread because working for alsa-lib[1]. Besides, I'm not full-time developer for this kind of work. In short, I use my limited private time for this discussion. On Jun 15 2016 17:06, Richard Cochran wrote: > On Wed, Jun 15, 2016

Re: [very-RFC 0/8] TSN driver for the kernel

Hi, Sorry to be late. In this weekday, I have little time for this thread because working for alsa-lib[1]. Besides, I'm not full-time developer for this kind of work. In short, I use my limited private time for this discussion. On Jun 15 2016 17:06, Richard Cochran wrote: > On Wed, Jun 15, 2016

Re: Stable -rc git trees and email headers

Hi Greg, On Fri, Jun 17, 2016 at 08:16:20PM -0700, Greg KH wrote: > Hi, > > I've finally gotten off my butt and made my quilt trees of patches into > a "semi-proper" git tree to make it easier for people to test them. > > I'm now pushing the patches I accept into the stable queues into the git

Re: Stable -rc git trees and email headers

Hi Greg, On Fri, Jun 17, 2016 at 08:16:20PM -0700, Greg KH wrote: > Hi, > > I've finally gotten off my butt and made my quilt trees of patches into > a "semi-proper" git tree to make it easier for people to test them. > > I'm now pushing the patches I accept into the stable queues into the git

Re: [PATCH] mm: fix account pmd page to the process

On 2016/6/17 23:39, Mike Kravetz wrote: > On 06/17/2016 05:25 AM, Kirill A. Shutemov wrote: >> From fd22922e7b4664e83653a84331f0a95b985bff0c Mon Sep 17 00:00:00 2001 >> From: "Kirill A. Shutemov" >> Date: Fri, 17 Jun 2016 15:07:03 +0300 >> Subject: [PATCH]

Re: [PATCH] mm: fix account pmd page to the process

On 2016/6/17 23:39, Mike Kravetz wrote: > On 06/17/2016 05:25 AM, Kirill A. Shutemov wrote: >> From fd22922e7b4664e83653a84331f0a95b985bff0c Mon Sep 17 00:00:00 2001 >> From: "Kirill A. Shutemov" >> Date: Fri, 17 Jun 2016 15:07:03 +0300 >> Subject: [PATCH] hugetlb: fix nr_pmds accounting with

Re: [PATCH 1/2] usb: phy: Add initial support for Qualcomm HSIC PHY

Hi, [auto build test WARNING on balbi-usb/next] [also build test WARNING on v4.7-rc3 next-20160617] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Neil-Armstrong/usb-phy-Add-support

Re: [PATCH 1/2] usb: phy: Add initial support for Qualcomm HSIC PHY

Hi, [auto build test WARNING on balbi-usb/next] [also build test WARNING on v4.7-rc3 next-20160617] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Neil-Armstrong/usb-phy-Add-support

Re: [PATCH 0/6] eBPF JIT for PPC64

On 2016-06-13 15:40, Naveen N. Rao wrote: On 2016/06/10 10:47PM, David Miller wrote: From: "Naveen N. Rao" Date: Tue, 7 Jun 2016 19:02:17 +0530 > Please note that patch [2] is a pre-requisite for this patchset, and is > not yet upstream. ... > [1]

Re: [PATCH 0/6] eBPF JIT for PPC64

On 2016-06-13 15:40, Naveen N. Rao wrote: On 2016/06/10 10:47PM, David Miller wrote: From: "Naveen N. Rao" Date: Tue, 7 Jun 2016 19:02:17 +0530 > Please note that patch [2] is a pre-requisite for this patchset, and is > not yet upstream. ... > [1]

Re: [PATCH] x86: fux duplicated X86_BUG(9) macro

On Fri, Jun 17, 2016 at 5:15 PM, Dave Hansen wrote: > > Now sending with actual stable@ address... > > -- > > From: Dave Hansen > > cpufeatures.h currently defines X86_BUG(9) twice on 32-bit: Acked-by: Andy Lutomirski # who is

Re: [PATCH] x86: fux duplicated X86_BUG(9) macro

On Fri, Jun 17, 2016 at 5:15 PM, Dave Hansen wrote: > > Now sending with actual stable@ address... > > -- > > From: Dave Hansen > > cpufeatures.h currently defines X86_BUG(9) twice on 32-bit: Acked-by: Andy Lutomirski # who is suitably embarrassed That being said, you or Ingo should consider

Re: [PATCH v3 0/2] net: ethernet: ti: cpsw: delete rx_descs property

From: Ivan Khoronzhuk Date: Fri, 17 Jun 2016 13:25:38 +0300 > There is no reason in rx_descs property because davinici_cpdma > driver splits pool of descriptors equally between tx and rx channels. > So, this patch series makes driver to use available number of >

Re: [PATCH v3 0/2] net: ethernet: ti: cpsw: delete rx_descs property

From: Ivan Khoronzhuk Date: Fri, 17 Jun 2016 13:25:38 +0300 > There is no reason in rx_descs property because davinici_cpdma > driver splits pool of descriptors equally between tx and rx channels. > So, this patch series makes driver to use available number of > descriptors for rx channels. > >

Re: Stable -rc git trees and email headers

Hi Greg, On 06/17/2016 08:16 PM, Greg KH wrote: Hi, I've finally gotten off my butt and made my quilt trees of patches into a "semi-proper" git tree to make it easier for people to test them. I'm now pushing the patches I accept into the stable queues into the git tree here:

Re: Stable -rc git trees and email headers

Hi Greg, On 06/17/2016 08:16 PM, Greg KH wrote: Hi, I've finally gotten off my butt and made my quilt trees of patches into a "semi-proper" git tree to make it easier for people to test them. I'm now pushing the patches I accept into the stable queues into the git tree here:

Re: [v3,1/4] mfd: cros_ec: Add cros_ec_cmd_xfer_status helper

On 06/17/2016 06:08 PM, Brian Norris wrote: On Fri, Jun 17, 2016 at 02:41:51PM -0700, Guenter Roeck wrote: On Fri, Jun 17, 2016 at 12:58:12PM -0700, Brian Norris wrote: +int cros_ec_cmd_xfer_status(struct cros_ec_device *ec_dev, + struct cros_ec_command *msg) +{ +

Re: [v3,1/4] mfd: cros_ec: Add cros_ec_cmd_xfer_status helper

On 06/17/2016 06:08 PM, Brian Norris wrote: On Fri, Jun 17, 2016 at 02:41:51PM -0700, Guenter Roeck wrote: On Fri, Jun 17, 2016 at 12:58:12PM -0700, Brian Norris wrote: +int cros_ec_cmd_xfer_status(struct cros_ec_device *ec_dev, + struct cros_ec_command *msg) +{ +

Re: [PATCH] Staging: comedi: comedi_fops.c: Replaced ACCESS_ONCE with READ/WRITE_ONCE

On Sun, Jun 05, 2016 at 08:10:50PM -0700, Andy Eleftherion wrote: > Replaced ACCESS_ONCE calls with READ/WRITE_ONCE calls. Why?

Re: [PATCH] Staging: comedi: comedi_fops.c: Replaced ACCESS_ONCE with READ/WRITE_ONCE

On Sun, Jun 05, 2016 at 08:10:50PM -0700, Andy Eleftherion wrote: > Replaced ACCESS_ONCE calls with READ/WRITE_ONCE calls. Why?

Re: [PATCH 2649/2649] Staging: comedi : fixed a camel case style issue

On Wed, Jun 01, 2016 at 10:35:57AM +0100, Ian Abbott wrote: > On 01/06/16 10:19, Ashwin Ravichandran wrote: > > Fixed a coding style issue. > > > > Signed-off-by: Ashwin Ravichandran > > --- > > drivers/staging/comedi/drivers/addi-data/hwdrv_apci3501.c | 2 +- >

Re: [PATCH 2649/2649] Staging: comedi : fixed a camel case style issue

On Wed, Jun 01, 2016 at 02:19:35AM -0700, Ashwin Ravichandran wrote: > Fixed a coding style issue. Which one? And where are the 2648 previous patches in this series? thanks, greg k-h

Re: [PATCH 2649/2649] Staging: comedi : fixed a camel case style issue

On Wed, Jun 01, 2016 at 10:35:57AM +0100, Ian Abbott wrote: > On 01/06/16 10:19, Ashwin Ravichandran wrote: > > Fixed a coding style issue. > > > > Signed-off-by: Ashwin Ravichandran > > --- > > drivers/staging/comedi/drivers/addi-data/hwdrv_apci3501.c | 2 +- > >

Re: [PATCH 2649/2649] Staging: comedi : fixed a camel case style issue

On Wed, Jun 01, 2016 at 02:19:35AM -0700, Ashwin Ravichandran wrote: > Fixed a coding style issue. Which one? And where are the 2648 previous patches in this series? thanks, greg k-h

Re: [PATCH] Staging: comedi: das16.c: Added a blank line fixed a comment, coding style issue

On Tue, May 31, 2016 at 09:00:59PM -0300, Pedro Nieto wrote: > From: PedroNieto No space? > > Fixed a coding style issue. Which one? Please be specific.

Re: [PATCH] Staging: comedi: das16.c: Added a blank line fixed a comment, coding style issue

On Tue, May 31, 2016 at 09:00:59PM -0300, Pedro Nieto wrote: > From: PedroNieto No space? > > Fixed a coding style issue. Which one? Please be specific.

Re: [PATCH] Staging: comedi: ni_atmio: fixed spacing and comment style issues

On Thu, May 26, 2016 at 06:35:48PM -0500, Steven Laabs wrote: > Fixed coding style issues. That's very vague, please be specific and exact. thanks, greg k-h

Re: [PATCH] Staging: comedi: ni_atmio: fixed spacing and comment style issues

On Thu, May 26, 2016 at 06:35:48PM -0500, Steven Laabs wrote: > Fixed coding style issues. That's very vague, please be specific and exact. thanks, greg k-h

Re: [PATCH] Staging: comedi: quatech_daqp_cs.c: Fix a unsigned warning issue

On Tue, May 17, 2016 at 10:23:44PM +0530, Amit Ghadge wrote: > This is a patch to the quatech_daqp_cs.c file that fixes by using > unsigned int instead of unsigned, following warning found by checkpatch. > * WARNING: Prefer 'unsigned int' to bare use of 'unsigned' > > Signed-off-by: Amit Ghadge

Re: [PATCH] Staging: comedi: quatech_daqp_cs.c: Fix a unsigned warning issue

On Tue, May 17, 2016 at 10:23:44PM +0530, Amit Ghadge wrote: > This is a patch to the quatech_daqp_cs.c file that fixes by using > unsigned int instead of unsigned, following warning found by checkpatch. > * WARNING: Prefer 'unsigned int' to bare use of 'unsigned' > > Signed-off-by: Amit Ghadge

Re: [PATCH] Staging: comedi: quatech_daqp_cs.c: fixed a warning issue

On Mon, May 16, 2016 at 11:04:31PM +0530, Amit Ghadge wrote: > Fixed a warning issue to use 'unsigned int'. > > Signed-off-by: Amit Ghadge > --- > drivers/staging/comedi/drivers/quatech_daqp_cs.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Doesn't apply to my

Re: [PATCH] Staging: comedi: quatech_daqp_cs.c: fixed a warning issue

On Mon, May 16, 2016 at 11:04:31PM +0530, Amit Ghadge wrote: > Fixed a warning issue to use 'unsigned int'. > > Signed-off-by: Amit Ghadge > --- > drivers/staging/comedi/drivers/quatech_daqp_cs.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Doesn't apply to my tree :(

Re: [PATCH] net: lantiq_etop: remove unused variable

From: Sudip Mukherjee Date: Thu, 16 Jun 2016 22:19:31 +0100 > The variable i was declared but was never used and we were getting a > build warning for that. > > Signed-off-by: Sudip Mukherjee Applied, thanks.

Re: [PATCH] net: lantiq_etop: remove unused variable

From: Sudip Mukherjee Date: Thu, 16 Jun 2016 22:19:31 +0100 > The variable i was declared but was never used and we were getting a > build warning for that. > > Signed-off-by: Sudip Mukherjee Applied, thanks.

Re: [PATCH v2 1/4] staging : comedi : fix type issues in s626.c

On Sat, May 28, 2016 at 10:56:48AM +0530, Ravishankar Karkala Mallikarjunayya wrote: > This is a patch to the s626.c file that fixes up a type issues like > i.e Prefer kernel type 'u8' over 'uint8_t' > Prefer kernel type 'u16' over 'uint16_t' > Prefer kernel type 'u32' over 'uint32_t' >

Re: [PATCH v2 1/4] staging : comedi : fix type issues in s626.c

On Sat, May 28, 2016 at 10:56:48AM +0530, Ravishankar Karkala Mallikarjunayya wrote: > This is a patch to the s626.c file that fixes up a type issues like > i.e Prefer kernel type 'u8' over 'uint8_t' > Prefer kernel type 'u16' over 'uint16_t' > Prefer kernel type 'u32' over 'uint32_t' >

Re: [PATCH v2 4/4] Staging: comedi: fix line over 80 characters issue in s626.c

On Mon, May 30, 2016 at 03:21:27PM +0100, Luis de Bethencourt wrote: > On 28/05/16 06:26, Ravishankar Karkala Mallikarjunayya wrote: > > This is a patch to the s626.c file that fixes up a line over 80 > > characters issues found by the checkpatch.pl tool. > > > > Signed-off-by: Ravishankar

Re: [PATCH v2 4/4] Staging: comedi: fix line over 80 characters issue in s626.c

On Mon, May 30, 2016 at 03:21:27PM +0100, Luis de Bethencourt wrote: > On 28/05/16 06:26, Ravishankar Karkala Mallikarjunayya wrote: > > This is a patch to the s626.c file that fixes up a line over 80 > > characters issues found by the checkpatch.pl tool. > > > > Signed-off-by: Ravishankar

Re: [PATCH v5 2/4] gpio: Allow PC/104 devices on X86_64

On Fri, Jun 17, 2016 at 11:39:04PM -0400, William Breathitt Gray wrote: > On Fri, Jun 17, 2016 at 08:18:10PM -0700, Greg KH wrote: > >On Fri, Jun 17, 2016 at 10:49:59PM -0400, William Breathitt Gray wrote: > >> The PC/104 drivers were changed to utilize the ISA bus driver as part of > >> the

Re: [PATCH v5 2/4] gpio: Allow PC/104 devices on X86_64

On Fri, Jun 17, 2016 at 11:39:04PM -0400, William Breathitt Gray wrote: > On Fri, Jun 17, 2016 at 08:18:10PM -0700, Greg KH wrote: > >On Fri, Jun 17, 2016 at 10:49:59PM -0400, William Breathitt Gray wrote: > >> The PC/104 drivers were changed to utilize the ISA bus driver as part of > >> the

Re: [PATCH v5 2/4] gpio: Allow PC/104 devices on X86_64

On Fri, Jun 17, 2016 at 08:18:10PM -0700, Greg KH wrote: >On Fri, Jun 17, 2016 at 10:49:59PM -0400, William Breathitt Gray wrote: >> The PC/104 drivers were changed to utilize the ISA bus driver as part of >> the original patchset which attempted to decouple the X86_32 dependency >> from the ISA

Re: [PATCH v5 2/4] gpio: Allow PC/104 devices on X86_64

On Fri, Jun 17, 2016 at 08:18:10PM -0700, Greg KH wrote: >On Fri, Jun 17, 2016 at 10:49:59PM -0400, William Breathitt Gray wrote: >> The PC/104 drivers were changed to utilize the ISA bus driver as part of >> the original patchset which attempted to decouple the X86_32 dependency >> from the ISA

[PATCH 2/4] ASoC: tap6130a2: Use regmap

Use regmap instead of open-coding IO access and caching Signed-off-by: Lars-Peter Clausen [koike: port for upstream] Signed-off-by: Helen Koike --- sound/soc/codecs/tpa6130a2.c | 166 ---

[PATCH 1/4] ASoC: tpa6130a2: Register component

Add tpa6130a2 controls by the component API and update rx51 accordingly Signed-off-by: Lars-Peter Clausen [koike: port for upstream] Signed-off-by: Helen Koike --- sound/soc/codecs/tpa6130a2.c | 26 +-

[PATCH 2/4] ASoC: tap6130a2: Use regmap

Use regmap instead of open-coding IO access and caching Signed-off-by: Lars-Peter Clausen [koike: port for upstream] Signed-off-by: Helen Koike --- sound/soc/codecs/tpa6130a2.c | 166 --- sound/soc/codecs/tpa6130a2.h | 2 - 2 files changed, 46

[PATCH 1/4] ASoC: tpa6130a2: Register component

Add tpa6130a2 controls by the component API and update rx51 accordingly Signed-off-by: Lars-Peter Clausen [koike: port for upstream] Signed-off-by: Helen Koike --- sound/soc/codecs/tpa6130a2.c | 26 +- sound/soc/codecs/tpa6130a2.h | 1 - sound/soc/omap/rx51.c|

[PATCH 4/4] ASoC: tpa6130a2: Add DAPM support

Add DAPM support and updated rx51 accordingly. As a consequence: - the exported function tpa6130a2_stereo_enable is not needed anymore - the mutex is dealt in the DAPM - the power state is tracked by the DAPM Signed-off-by: Lars-Peter Clausen [koike: port for upstream]

[PATCH 4/4] ASoC: tpa6130a2: Add DAPM support

Add DAPM support and updated rx51 accordingly. As a consequence: - the exported function tpa6130a2_stereo_enable is not needed anymore - the mutex is dealt in the DAPM - the power state is tracked by the DAPM Signed-off-by: Lars-Peter Clausen [koike: port for upstream] Signed-off-by: Helen Koike

[PATCH 0/4] ASoC: tpa6130a2: Add support for multiple instances

The current tpa6130a2 driver supports only a single instance. This patch series add support for multiple instances by removing the global variable that holds the instance. This is performed by using the component API, regmap, the snd_soc_{info,put,get}_volsw API and DAPM. This patch series also

[PATCH 3/4] ASoC: tpa6130a2: Use snd soc volsw functions

Use snd_soc_{info,get,put}_volsw instead of custom volume functions Signed-off-by: Lars-Peter Clausen [koike: port for upstream] Signed-off-by: Helen Koike --- sound/soc/codecs/tpa6130a2.c | 64 ++-- 1 file

[PATCH 0/4] ASoC: tpa6130a2: Add support for multiple instances

The current tpa6130a2 driver supports only a single instance. This patch series add support for multiple instances by removing the global variable that holds the instance. This is performed by using the component API, regmap, the snd_soc_{info,put,get}_volsw API and DAPM. This patch series also

[PATCH 3/4] ASoC: tpa6130a2: Use snd soc volsw functions

Use snd_soc_{info,get,put}_volsw instead of custom volume functions Signed-off-by: Lars-Peter Clausen [koike: port for upstream] Signed-off-by: Helen Koike --- sound/soc/codecs/tpa6130a2.c | 64 ++-- 1 file changed, 2 insertions(+), 62 deletions(-) diff

Re: [PATCH 2/3] staging: lustre: lnet: Allocate MEs and small MDs in own kmem_caches

On Wed, Jun 15, 2016 at 04:02:40AM +0100, James Simmons wrote: > > > > This may also possibly help to save cycles due to high usage and > > > contention when using a generic kmem_cache (when they stay separate > > > from others, thanks for the precision!). > > > > Have you measured this? > > >

Re: [PATCH 2/3] staging: lustre: lnet: Allocate MEs and small MDs in own kmem_caches

On Wed, Jun 15, 2016 at 04:02:40AM +0100, James Simmons wrote: > > > > This may also possibly help to save cycles due to high usage and > > > contention when using a generic kmem_cache (when they stay separate > > > from others, thanks for the precision!). > > > > Have you measured this? > > >

Re: [PATCH v2] ION: Sys_heap: Add cached pool to spead up cached buffer alloc

Greg, I checkout your staging tree[1]. Not find this patch. Can you take it thanks! [1]git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git On 2016/6/5 23:02, Greg KH wrote: > On Sun, Jun 05, 2016 at 04:51:23PM +0800, Chen Feng wrote: >> Hi Greg, >> >> Can you take this patch? >

Re: [PATCH v2] ION: Sys_heap: Add cached pool to spead up cached buffer alloc

Greg, I checkout your staging tree[1]. Not find this patch. Can you take it thanks! [1]git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git On 2016/6/5 23:02, Greg KH wrote: > On Sun, Jun 05, 2016 at 04:51:23PM +0800, Chen Feng wrote: >> Hi Greg, >> >> Can you take this patch? >

Re: [PATCH v5 2/4] gpio: Allow PC/104 devices on X86_64

On Fri, Jun 17, 2016 at 10:49:59PM -0400, William Breathitt Gray wrote: > On Fri, Jun 17, 2016 at 07:36:07PM -0700, Greg KH wrote: > >On Fri, Jun 17, 2016 at 12:47:14PM +0200, Thorsten Leemhuis wrote: > >> On 31.05.2016 17:25, Greg KH wrote: > >> > On Tue, May 31, 2016 at 07:23:06AM -0400, William

Re: [PATCH v5 2/4] gpio: Allow PC/104 devices on X86_64

On Fri, Jun 17, 2016 at 10:49:59PM -0400, William Breathitt Gray wrote: > On Fri, Jun 17, 2016 at 07:36:07PM -0700, Greg KH wrote: > >On Fri, Jun 17, 2016 at 12:47:14PM +0200, Thorsten Leemhuis wrote: > >> On 31.05.2016 17:25, Greg KH wrote: > >> > On Tue, May 31, 2016 at 07:23:06AM -0400, William

[GIT PULL] liblockdep fixes for 4.7

Hey Ingo, Please pull a bunch of fixes for liblockdep from Ben and Vishal. Mostly build failures as a result of kernel changes. Thanks, Sasha === The following changes since commit 1a695a905c18548062509178b98bc91e67510864: Linux 4.7-rc1 (2016-05-29 09:29:24 -0700) are available in the

[GIT PULL] liblockdep fixes for 4.7

Hey Ingo, Please pull a bunch of fixes for liblockdep from Ben and Vishal. Mostly build failures as a result of kernel changes. Thanks, Sasha === The following changes since commit 1a695a905c18548062509178b98bc91e67510864: Linux 4.7-rc1 (2016-05-29 09:29:24 -0700) are available in the

Stable -rc git trees and email headers

Hi, I've finally gotten off my butt and made my quilt trees of patches into a "semi-proper" git tree to make it easier for people to test them. I'm now pushing the patches I accept into the stable queues into the git tree here:

Stable -rc git trees and email headers

Hi, I've finally gotten off my butt and made my quilt trees of patches into a "semi-proper" git tree to make it easier for people to test them. I'm now pushing the patches I accept into the stable queues into the git tree here:

Re: [PATCH v8 2/4] power: reset: add reboot mode driver

Hi Sebastian: On 2016年06月16日 22:36, Sebastian Reichel wrote: Hi, On Mon, Apr 25, 2016 at 02:55:36PM +0800, Andy Yan wrote: This driver parses the reboot commands like "reboot bootloader" and "reboot recovery" to get a boot mode described in the device tree , then call the write interfae to

Re: [PATCH v8 2/4] power: reset: add reboot mode driver

Hi Sebastian: On 2016年06月16日 22:36, Sebastian Reichel wrote: Hi, On Mon, Apr 25, 2016 at 02:55:36PM +0800, Andy Yan wrote: This driver parses the reboot commands like "reboot bootloader" and "reboot recovery" to get a boot mode described in the device tree , then call the write interfae to

Re: [PATCH v5 2/4] gpio: Allow PC/104 devices on X86_64

On Fri, Jun 17, 2016 at 07:36:07PM -0700, Greg KH wrote: >On Fri, Jun 17, 2016 at 12:47:14PM +0200, Thorsten Leemhuis wrote: >> On 31.05.2016 17:25, Greg KH wrote: >> > On Tue, May 31, 2016 at 07:23:06AM -0400, William Breathitt Gray wrote: >> >> On Tue, May 31, 2016 at 10:41:49AM +0200, Linus

Re: [PATCH v5 2/4] gpio: Allow PC/104 devices on X86_64

On Fri, Jun 17, 2016 at 07:36:07PM -0700, Greg KH wrote: >On Fri, Jun 17, 2016 at 12:47:14PM +0200, Thorsten Leemhuis wrote: >> On 31.05.2016 17:25, Greg KH wrote: >> > On Tue, May 31, 2016 at 07:23:06AM -0400, William Breathitt Gray wrote: >> >> On Tue, May 31, 2016 at 10:41:49AM +0200, Linus

Re: [PATCH v5 2/4] gpio: Allow PC/104 devices on X86_64

On Fri, Jun 17, 2016 at 12:47:14PM +0200, Thorsten Leemhuis wrote: > On 31.05.2016 17:25, Greg KH wrote: > > On Tue, May 31, 2016 at 07:23:06AM -0400, William Breathitt Gray wrote: > >> On Tue, May 31, 2016 at 10:41:49AM +0200, Linus Walleij wrote: > >>> On Sat, May 28, 2016 at 12:08 AM, William

Re: [PATCH v5 2/4] gpio: Allow PC/104 devices on X86_64

On Fri, Jun 17, 2016 at 12:47:14PM +0200, Thorsten Leemhuis wrote: > On 31.05.2016 17:25, Greg KH wrote: > > On Tue, May 31, 2016 at 07:23:06AM -0400, William Breathitt Gray wrote: > >> On Tue, May 31, 2016 at 10:41:49AM +0200, Linus Walleij wrote: > >>> On Sat, May 28, 2016 at 12:08 AM, William

[PATCH v13 06/16] sparc/PCI: Reserve legacy mmio after PCI mmio

On one system found bunch of claim resource fail from pci device. pci_sun4v f02b894c: PCI host bridge to bus :00 pci_bus :00: root bus resource [io 0x2007e-0x2007e0fff] (bus address [0x-0xfff]) pci_bus :00: root bus resource [mem 0x2-0x27eff]

[PATCH v13 06/16] sparc/PCI: Reserve legacy mmio after PCI mmio

On one system found bunch of claim resource fail from pci device. pci_sun4v f02b894c: PCI host bridge to bus :00 pci_bus :00: root bus resource [io 0x2007e-0x2007e0fff] (bus address [0x-0xfff]) pci_bus :00: root bus resource [mem 0x2-0x27eff]

[PATCH v13 15/16] PCI: Only treat non-pref mmio64 as pref if host bridge has mmio64

If host bridge does not have mmio64 above 4G, We don't need to treat device non-pref mmio64 as as pref mmio64. Signed-off-by: Yinghai Lu Tested-by: Khalid Aziz --- drivers/pci/setup-bus.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH v13 13/16] PCI: Only treat non-pref mmio64 as pref if all bridges have MEM_64

If any bridge up to root only have 32bit pref mmio, We don't need to treat device non-pref mmio64 as as pref mmio64. We need to move pci_bridge_check_ranges calling early. For parent bridges pref mmio BAR may not allocated by BIOS, res flags is still 0, we need to have it correct set before we

[PATCH v13 15/16] PCI: Only treat non-pref mmio64 as pref if host bridge has mmio64

If host bridge does not have mmio64 above 4G, We don't need to treat device non-pref mmio64 as as pref mmio64. Signed-off-by: Yinghai Lu Tested-by: Khalid Aziz --- drivers/pci/setup-bus.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pci/setup-bus.c

[PATCH v13 13/16] PCI: Only treat non-pref mmio64 as pref if all bridges have MEM_64

If any bridge up to root only have 32bit pref mmio, We don't need to treat device non-pref mmio64 as as pref mmio64. We need to move pci_bridge_check_ranges calling early. For parent bridges pref mmio BAR may not allocated by BIOS, res flags is still 0, we need to have it correct set before we

[PATCH v13 09/16] powerpc/PCI: Keep resource idx order with bridge register number

Same as sparc version. Make resource with consistent sequence like other arch or directly from pci_read_bridge_bases(), even when non-pref mmio is missing, or out of ordering in firmware reporting. Just hold i = 1 for non pref mmio, and i = 2 for pref mmio. Signed-off-by: Yinghai Lu

[PATCH v13 16/16] PCI: Restore pref MMIO allocation logic for host bridge without mmio64

>From 5b2854155 (PCI: Restrict 64-bit prefetchable bridge windows to 64-bit resources), we change the logic for pref mmio allocation: When bridge pref support mmio64, we will only put children pref that support mmio64 into it, and will put children pref mmio32 into bridge's non-pref mmio32. That

[PATCH v13 14/16] PCI: Add has_mem64 for struct host_bridge

Add has_mem64 for struct host_bridge, on root bus that does not support mmio64 above 4g, will not set that. We will use that info next two following patches: 1. Don't treat non-pref mmio64 as pref mmio, so will not put it under bridge's pref range when rescan the devices 2. will keep pref

[PATCH v13 05/16] PCI: Add pci_find_bus_resource()

Add pci_find_bus_resource() to return bus resource for input resource. In some case, we may only have bus instead of dev. It is same as pci_find_parent_resource, but take bus as input. Signed-off-by: Yinghai Lu --- drivers/pci/pci.c | 27 ---

[PATCH v13 09/16] powerpc/PCI: Keep resource idx order with bridge register number

Same as sparc version. Make resource with consistent sequence like other arch or directly from pci_read_bridge_bases(), even when non-pref mmio is missing, or out of ordering in firmware reporting. Just hold i = 1 for non pref mmio, and i = 2 for pref mmio. Signed-off-by: Yinghai Lu Cc:

[PATCH v13 16/16] PCI: Restore pref MMIO allocation logic for host bridge without mmio64

>From 5b2854155 (PCI: Restrict 64-bit prefetchable bridge windows to 64-bit resources), we change the logic for pref mmio allocation: When bridge pref support mmio64, we will only put children pref that support mmio64 into it, and will put children pref mmio32 into bridge's non-pref mmio32. That

[PATCH v13 14/16] PCI: Add has_mem64 for struct host_bridge

Add has_mem64 for struct host_bridge, on root bus that does not support mmio64 above 4g, will not set that. We will use that info next two following patches: 1. Don't treat non-pref mmio64 as pref mmio, so will not put it under bridge's pref range when rescan the devices 2. will keep pref

[PATCH v13 05/16] PCI: Add pci_find_bus_resource()

Add pci_find_bus_resource() to return bus resource for input resource. In some case, we may only have bus instead of dev. It is same as pci_find_parent_resource, but take bus as input. Signed-off-by: Yinghai Lu --- drivers/pci/pci.c | 27 --- include/linux/pci.h | 2

[PATCH v13 00/16] PCI: Fixup for 64bit resource with sparc

Hi Bjorn, After 5b28541552ef (PCI: Restrict 64-bit prefetchable bridge windows to 64-bit resources), we have several reports on resource allocation failure, and we try to fix the problem with resource clip, and find more problems. One is from sparc that have problem with clip as we don't parse

[PATCH v13 12/16] PCI: Check pref compatible bit for mem64 resource of PCIe device

We still get "no compatible bridge window" warning on sparc T5-8 after we add support for 64bit resource parsing for root bus. PCI: scan_bus[/pci@300/pci@1/pci@0/pci@6] bus no 8 PCI: Claiming :00:01.0: Resource 15: 8001..8004afff [220c] PCI: Claiming :01:00.0:

[PATCH v13 04/16] sparc/PCI: Use correct offset for bus address to resource

After we added 64bit mmio parsing, we got some "no compatible bridge window" warning on anther new model that support 64bit resource. It turns out that we can not use mem_space.start as 64bit mem space offset, aka there is mem_space.start != offset. Use child_phys_addr to calculate exact offset

[PATCH v13 01/16] PCI: Let pci_mmap_page_range() take resource address

In 8c05cd08a7 ("PCI: fix offset check for sysfs mmapped files"), try to check exposed value with resource start/end in proc mmap path. |start = vma->vm_pgoff; |size = ((pci_resource_len(pdev, resno) - 1) >> PAGE_SHIFT) + 1; |pci_start = (mmap_api == PCI_MMAP_PROCFS) ? |

Re: [PATCH v12.update2 02/15] PCI: Let pci_mmap_page_range() take resource address

On Fri, Jun 17, 2016 at 12:52 PM, Bjorn Helgaas wrote: >> >> and respin the whole patchset today. > > I added your acks and pushed the result to pci/resource. I'll also > post these formally on the list so they're easier to find. Please review patchset v13 that is against

[PATCH v13 00/16] PCI: Fixup for 64bit resource with sparc

Hi Bjorn, After 5b28541552ef (PCI: Restrict 64-bit prefetchable bridge windows to 64-bit resources), we have several reports on resource allocation failure, and we try to fix the problem with resource clip, and find more problems. One is from sparc that have problem with clip as we don't parse

  1   2   3   4   5   6   7   8   9   10   >