Re: [GIT PULL] STi defconfig updates for v4.10 round 3

On Monday, November 28, 2016 1:37:00 PM CET Patrice Chotard wrote: > > STi defconfig fix: > > Enable HVA (Hardware Video Accelerator) video encoder > driver for STMicroelectronics SoC. > > Pulled into next/defconfig, thanks! Arnd [I had to take ker...@stlinux.com from the Cc list,

Re: [PATCH v3 0/2] Support for Axentia TSE-850

On Wednesday, November 30, 2016 1:48:20 PM CET Peter Rosin wrote: > Hi! > > changes v2 -> v3 > - document the new compatible strings prefixed with "axentia,". > > changes v1 -> v2 > - squash the fixup into the correct patch, sorry for the noise. > > After finally having all essintial drivers

Re: [PATCH 1/7] vfs - merge path_is_mountpoint() and path_is_mountpoint_rcu()

So a far as I can tell, this patch series is intended to address Al's review comments against the http://lkml.kernel.org/r/20161011053352.27645.83962.st...@pluto.themaw.net series?

Re: [PATCH 1/7] vfs - merge path_is_mountpoint() and path_is_mountpoint_rcu()

So a far as I can tell, this patch series is intended to address Al's review comments against the http://lkml.kernel.org/r/20161011053352.27645.83962.st...@pluto.themaw.net series?

Re: [PATCH 2/3 v2] ALSA: usb-audio: avoid setting of sample rate multiple times on bus

On Nov 30 2016 19:45, Takashi Sakamoto wrote: Hi Jiada, I don't oppose this patch. Nevertheless, your description is not necessarily correct. On Nov 30 2016 16:59, Jiada Wang wrote: From: Daniel Girnus ALSA usually calls the prepare function twice before starting the

Re: [PATCH 2/3 v2] ALSA: usb-audio: avoid setting of sample rate multiple times on bus

On Nov 30 2016 19:45, Takashi Sakamoto wrote: Hi Jiada, I don't oppose this patch. Nevertheless, your description is not necessarily correct. On Nov 30 2016 16:59, Jiada Wang wrote: From: Daniel Girnus ALSA usually calls the prepare function twice before starting the playback: 1. On

Re: [PATCH 4/6] net: ethernet: ti: cpts: add ptp pps support

On Wed, Nov 30, 2016 at 02:43:57PM -0600, Grygorii Strashko wrote: > > In order to produce the PPS edge correctly, you would have to adjust > > the comparison value whenever cc.mult changes, > > yes. And that is done in cpts_ptp_adjfreq() > if (cpts->ts_comp_enabled) >

Re: [PATCH 4/6] net: ethernet: ti: cpts: add ptp pps support

On Wed, Nov 30, 2016 at 02:43:57PM -0600, Grygorii Strashko wrote: > > In order to produce the PPS edge correctly, you would have to adjust > > the comparison value whenever cc.mult changes, > > yes. And that is done in cpts_ptp_adjfreq() > if (cpts->ts_comp_enabled) >

RE: [RESEND PATCH 06/11] cpufreq: intel_pstate: Add Knights Mill CPUID

Thanks! Piotr > -Original Message- > From: rjwyso...@gmail.com [mailto:rjwyso...@gmail.com] On Behalf Of > Rafael J. Wysocki > Sent: Wednesday, November 30, 2016 11:02 PM > To: Luc, Piotr > Cc: raf...@kernel.org; srinivas.pandruv...@linux.intel.com; >

RE: [RESEND PATCH 06/11] cpufreq: intel_pstate: Add Knights Mill CPUID

Thanks! Piotr > -Original Message- > From: rjwyso...@gmail.com [mailto:rjwyso...@gmail.com] On Behalf Of > Rafael J. Wysocki > Sent: Wednesday, November 30, 2016 11:02 PM > To: Luc, Piotr > Cc: raf...@kernel.org; srinivas.pandruv...@linux.intel.com; > l...@kernel.org;

Re: [PATCH] x86/intel_rdt.c: Disable preempt for intel_rdt_sched_in() in move_myself()

On Wed, 30 Nov 2016, Fenghua Yu wrote: > From: Fenghua Yu Subject: x86/intel_rdt.c: Disable preempt for intel_rdt_sched_in() in move_myself() - The prefix is crap. git log arch/x86/kernel/cpu/intel_rdt.c should tell you what's the proper prefix is. It's preemption not

Re: [PATCH] x86/intel_rdt.c: Disable preempt for intel_rdt_sched_in() in move_myself()

On Wed, 30 Nov 2016, Fenghua Yu wrote: > From: Fenghua Yu Subject: x86/intel_rdt.c: Disable preempt for intel_rdt_sched_in() in move_myself() - The prefix is crap. git log arch/x86/kernel/cpu/intel_rdt.c should tell you what's the proper prefix is. It's preemption not preempt and this wants

Re: [PATCH] intelrdt: resctrl: recommend locking for resctrlfs

On Wed, Nov 30, 2016 at 01:48:10PM -0200, Marcelo Tosatti wrote: > > There is a locking problem between different applications > reading/writing to resctrlfs directory at the same time (read the patch > below for details). > > Suggest a standard locking scheme for applications to use. > >

Re: [PATCH] intelrdt: resctrl: recommend locking for resctrlfs

On Wed, Nov 30, 2016 at 01:48:10PM -0200, Marcelo Tosatti wrote: > > There is a locking problem between different applications > reading/writing to resctrlfs directory at the same time (read the patch > below for details). > > Suggest a standard locking scheme for applications to use. > >

Re: [OpenRISC] Add openrisc for-next branch to linux-next

On 11/30/16 12:11, Olof Kindgren wrote: > > Hi, > > I see that you have updated MAINTAINERS. Good. > > Does openRISC support VGA console? > I tried to send a patch to Jason a few days ago. > Please look at http://marc.info/?l=linux-kernel=147968525011508=2 >

Re: [OpenRISC] Add openrisc for-next branch to linux-next

On 11/30/16 12:11, Olof Kindgren wrote: > > Hi, > > I see that you have updated MAINTAINERS. Good. > > Does openRISC support VGA console? > I tried to send a patch to Jason a few days ago. > Please look at http://marc.info/?l=linux-kernel=147968525011508=2 >

Re: [PATCH 01/10] doc: DT: camss: Binding document for Qualcomm Camera subsystem driver

On Fri, Nov 25, 2016 at 04:56:53PM +0200, Todor Tomov wrote: > Add DT binding document for Qualcomm Camera subsystem driver. > > Signed-off-by: Todor Tomov > --- > .../devicetree/bindings/media/qcom,camss.txt | 196 > + > 1 file changed, 196

Re: [PATCH 01/10] doc: DT: camss: Binding document for Qualcomm Camera subsystem driver

On Fri, Nov 25, 2016 at 04:56:53PM +0200, Todor Tomov wrote: > Add DT binding document for Qualcomm Camera subsystem driver. > > Signed-off-by: Todor Tomov > --- > .../devicetree/bindings/media/qcom,camss.txt | 196 > + > 1 file changed, 196 insertions(+) > create

Re: [PATCH v3 3/5] KVM: nVMX: fix checks on CR{0,4} during virtual VMX operation

2016-11-29 18:14-0800, David Matlack: > KVM emulates MSR_IA32_VMX_CR{0,4}_FIXED1 with the value -1ULL, meaning > all CR0 and CR4 bits are allowed to be 1 during VMX operation. > > This does not match real hardware, which disallows the high 32 bits of > CR0 to be 1, and disallows reserved bits of

[PATCH] net: atarilance: use %8ph for printing hex string

This is already using the %pM printf extension; might as well also use %ph to make the code smaller. Signed-off-by: Rasmus Villemoes --- drivers/net/ethernet/amd/atarilance.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git

[PATCH] net: atarilance: use %8ph for printing hex string

This is already using the %pM printf extension; might as well also use %ph to make the code smaller. Signed-off-by: Rasmus Villemoes --- drivers/net/ethernet/amd/atarilance.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/drivers/net/ethernet/amd/atarilance.c

Re: [PATCH v3 3/5] KVM: nVMX: fix checks on CR{0,4} during virtual VMX operation

2016-11-29 18:14-0800, David Matlack: > KVM emulates MSR_IA32_VMX_CR{0,4}_FIXED1 with the value -1ULL, meaning > all CR0 and CR4 bits are allowed to be 1 during VMX operation. > > This does not match real hardware, which disallows the high 32 bits of > CR0 to be 1, and disallows reserved bits of

[PATCH v6 1/3] media: Media Device Allocator API

Media Device Allocator API to allows multiple drivers share a media device. Using this API, drivers can allocate a media device with the shared struct device as the key. Once the media device is allocated by a driver, other drivers can get a reference to it. The media device is released when all

[PATCH v6 1/3] media: Media Device Allocator API

Media Device Allocator API to allows multiple drivers share a media device. Using this API, drivers can allocate a media device with the shared struct device as the key. Once the media device is allocated by a driver, other drivers can get a reference to it. The media device is released when all

Re: [RESEND PATCH 06/11] cpufreq: intel_pstate: Add Knights Mill CPUID

On Wed, Nov 30, 2016 at 5:19 PM, Luc, Piotr wrote: > Hi Rafael, > >> > > >> > > The mentioned path 03/11 is already merged in 4.9.rc2. >> > >> > If it's already there, I can pick up the intel_pstate one. >> > >> > Thanks, >> > > >> > > Rafael >> >> Here is the commit

Re: Add openrisc for-next branch to linux-next

On Wed, 30 Nov 2016, Randy Dunlap wrote: On 11/30/16 05:22, Stafford Horne wrote: Hi Stephen, I have been working on getting the OpenRISC backlog of fixes sorted out for upstream. Can this branch be added to linux-next? git://github.com/openrisc/linux.git for-next These have been

Re: Add openrisc for-next branch to linux-next

On Wed, 30 Nov 2016, Randy Dunlap wrote: On 11/30/16 05:22, Stafford Horne wrote: Hi Stephen, I have been working on getting the OpenRISC backlog of fixes sorted out for upstream. Can this branch be added to linux-next? git://github.com/openrisc/linux.git for-next These have been

Re: [RESEND PATCH 06/11] cpufreq: intel_pstate: Add Knights Mill CPUID

On Wed, Nov 30, 2016 at 5:19 PM, Luc, Piotr wrote: > Hi Rafael, > >> > > >> > > The mentioned path 03/11 is already merged in 4.9.rc2. >> > >> > If it's already there, I can pick up the intel_pstate one. >> > >> > Thanks, >> > > >> > > Rafael >> >> Here is the commit

[PATCH v6 2/3] media: change au0828 to use Media Device Allocator API

Change au0828 to use Media Device Allocator API to allocate media device with the parent usb struct device as the key, so it can be shared with the snd_usb_audio driver. Signed-off-by: Shuah Khan --- Changes to patch 0002: - No changes since patch v2, applies cleanly on

[PATCH v6 3/3] sound/usb: Use Media Controller API to share media resources

Change ALSA driver to use Media Controller API to share media resources with DVB, and V4L2 drivers on a AU0828 media device. Media Controller specific initialization is done after sound card is registered. ALSA creates Media interface and entity function graph nodes for Control, Mixer, PCM

[PATCH v6 0/3] Media Device Allocator API

Media Device Allocator API to allows multiple drivers share a media device. Using this API, drivers can allocate a media device with the shared struct device as the key. Once the media device is allocated by a driver, other drivers can get a reference to it. The media device is released when all

Re: [PATCH V5] PM / OPP: Pass opp_table to dev_pm_opp_put_regulator()

On 11/30, Viresh Kumar wrote: > From: Stephen Boyd > > Joonyoung Shim reported an interesting problem on his ARM octa-core > Odoroid-XU3 platform. During system suspend, dev_pm_opp_put_regulator() > was failing for a struct device for which dev_pm_opp_set_regulator() is >

[PATCH v6 2/3] media: change au0828 to use Media Device Allocator API

Change au0828 to use Media Device Allocator API to allocate media device with the parent usb struct device as the key, so it can be shared with the snd_usb_audio driver. Signed-off-by: Shuah Khan --- Changes to patch 0002: - No changes since patch v2, applies cleanly on top of the following:

[PATCH v6 3/3] sound/usb: Use Media Controller API to share media resources

Change ALSA driver to use Media Controller API to share media resources with DVB, and V4L2 drivers on a AU0828 media device. Media Controller specific initialization is done after sound card is registered. ALSA creates Media interface and entity function graph nodes for Control, Mixer, PCM

[PATCH v6 0/3] Media Device Allocator API

Media Device Allocator API to allows multiple drivers share a media device. Using this API, drivers can allocate a media device with the shared struct device as the key. Once the media device is allocated by a driver, other drivers can get a reference to it. The media device is released when all

Re: [PATCH V5] PM / OPP: Pass opp_table to dev_pm_opp_put_regulator()

On 11/30, Viresh Kumar wrote: > From: Stephen Boyd > > Joonyoung Shim reported an interesting problem on his ARM octa-core > Odoroid-XU3 platform. During system suspend, dev_pm_opp_put_regulator() > was failing for a struct device for which dev_pm_opp_set_regulator() is > called earlier. > >

Re: [PATCH net] cdc_ether: Fix handling connection notification

On Wed, Nov 30, 2016 at 10:51 PM, Bjørn Mork wrote: > Kristian Evensen writes: > >> +void usbnet_cdc_zte_status(struct usbnet *dev, struct urb *urb) >> +{ >> + struct usb_cdc_notification *event; >> + >> + if (urb->actual_length <

Re: [PATCH net] cdc_ether: Fix handling connection notification

On Wed, Nov 30, 2016 at 10:51 PM, Bjørn Mork wrote: > Kristian Evensen writes: > >> +void usbnet_cdc_zte_status(struct usbnet *dev, struct urb *urb) >> +{ >> + struct usb_cdc_notification *event; >> + >> + if (urb->actual_length < sizeof(*event)) >> + return; >> + >> +

[GIT PULL] clk fixes for v4.9-rc7

The following changes since commit ac95330b96376550ae7a533d1396272d675adfa2: clk: sunxi: Fix M factor computation for APB1 (2016-11-04 08:49:46 +0100) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-fixes-for-linus for you to

[GIT PULL] clk fixes for v4.9-rc7

The following changes since commit ac95330b96376550ae7a533d1396272d675adfa2: clk: sunxi: Fix M factor computation for APB1 (2016-11-04 08:49:46 +0100) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-fixes-for-linus for you to

Re: Odd build breakage in 4.9-rc7

On Wed, 2016-11-30 at 22:42 +0100, Paul Bolle wrote: > My current theory is that setting MODVERSIONS, somehow, hides the ERROR spew. > Because that could explain your bisect. Linus' commit turns of MODVERSIONS the > hard way. And, naturally, this theory fails if your .configs never had >

Re: Odd build breakage in 4.9-rc7

On Wed, 2016-11-30 at 22:42 +0100, Paul Bolle wrote: > My current theory is that setting MODVERSIONS, somehow, hides the ERROR spew. > Because that could explain your bisect. Linus' commit turns of MODVERSIONS the > hard way. And, naturally, this theory fails if your .configs never had >

Re: [PATCH 1/2] dt-bindings: usb: add DT binding for s3c2410 USB OHCI controller

On Fri, Nov 25, 2016 at 12:47:28PM -0200, Sergio Prado wrote: > Adds the device tree bindings description for Samsung S3C2410 and > compatible USB OHCI controller. > > Signed-off-by: Sergio Prado > --- > .../devicetree/bindings/usb/s3c2410-usb.txt| 22 >

Re: [PATCH 1/2] dt-bindings: usb: add DT binding for s3c2410 USB OHCI controller

On Fri, Nov 25, 2016 at 12:47:28PM -0200, Sergio Prado wrote: > Adds the device tree bindings description for Samsung S3C2410 and > compatible USB OHCI controller. > > Signed-off-by: Sergio Prado > --- > .../devicetree/bindings/usb/s3c2410-usb.txt| 22 > ++ > 1 file

Re: [PATCH net] cdc_ether: Fix handling connection notification

Kristian Evensen writes: > +void usbnet_cdc_zte_status(struct usbnet *dev, struct urb *urb) > +{ > + struct usb_cdc_notification *event; > + > + if (urb->actual_length < sizeof(*event)) > + return; > + > + event = urb->transfer_buffer; > + > +

Re: [PATCH net] cdc_ether: Fix handling connection notification

Kristian Evensen writes: > +void usbnet_cdc_zte_status(struct usbnet *dev, struct urb *urb) > +{ > + struct usb_cdc_notification *event; > + > + if (urb->actual_length < sizeof(*event)) > + return; > + > + event = urb->transfer_buffer; > + > + if

Re: [GIT PULL 3/3] arm64: dts: exynos: DT for v4.10, second round

On Thursday, November 24, 2016 8:08:29 AM CET Krzysztof Kozlowski wrote: > Samsung DeviceTree arm64 second update for v4.10: > 1. Add Performance Monitor Unit to Exynos7. > 2. Add MFC, JPEG and Gscaler to Exynos5433 based TM2 board. > 3. Cleanups and fixes for recently added TM2 and TM2E boards. >

Re: [GIT PULL 3/3] arm64: dts: exynos: DT for v4.10, second round

On Thursday, November 24, 2016 8:08:29 AM CET Krzysztof Kozlowski wrote: > Samsung DeviceTree arm64 second update for v4.10: > 1. Add Performance Monitor Unit to Exynos7. > 2. Add MFC, JPEG and Gscaler to Exynos5433 based TM2 board. > 3. Cleanups and fixes for recently added TM2 and TM2E boards. >

[PATCH v5 net-next 3/7] net: mvneta: Use cacheable memory to store the rx buffer virtual address

Until now the virtual address of the received buffer were stored in the cookie field of the rx descriptor. However, this field is 32-bits only which prevents to use the driver on a 64-bits architecture. With this patch the virtual address is stored in an array not shared with the hardware (no

[PATCH v5 net-next 2/7] net: mvneta: Do not allocate buffer in rxq init with HWBM

For HWBM all buffers are allocated in mvneta_bm_construct() and in runtime they are put into descriptors by hardware. There is no need to fill them at this point. Suggested-by: Marcin Wojtas Signed-off-by: Gregory CLEMENT ---

[PATCH v5 net-next 4/7] net: mvneta: Convert to be 64 bits compatible

From: Marcin Wojtas Prepare the mvneta driver in order to be usable on the 64 bits platform such as the Armada 3700. [gregory.clem...@free-electrons.com]: this patch was extract from a larger one to ease review and maintenance. Signed-off-by: Marcin Wojtas

[PATCH v5 net-next 3/7] net: mvneta: Use cacheable memory to store the rx buffer virtual address

Until now the virtual address of the received buffer were stored in the cookie field of the rx descriptor. However, this field is 32-bits only which prevents to use the driver on a 64-bits architecture. With this patch the virtual address is stored in an array not shared with the hardware (no

[PATCH v5 net-next 2/7] net: mvneta: Do not allocate buffer in rxq init with HWBM

For HWBM all buffers are allocated in mvneta_bm_construct() and in runtime they are put into descriptors by hardware. There is no need to fill them at this point. Suggested-by: Marcin Wojtas Signed-off-by: Gregory CLEMENT --- drivers/net/ethernet/marvell/mvneta.c | 4 ++-- 1 file changed, 2

[PATCH v5 net-next 4/7] net: mvneta: Convert to be 64 bits compatible

From: Marcin Wojtas Prepare the mvneta driver in order to be usable on the 64 bits platform such as the Armada 3700. [gregory.clem...@free-electrons.com]: this patch was extract from a larger one to ease review and maintenance. Signed-off-by: Marcin Wojtas Signed-off-by: Gregory CLEMENT ---

[PATCH v5 net-next 5/7] net: mvneta: Only disable mvneta_bm for 64-bits

Actually only the mvneta_bm support is not 64-bits compatible. The mvneta code itself can run on 64-bits architecture. Signed-off-by: Gregory CLEMENT --- drivers/net/ethernet/marvell/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH v5 net-next 5/7] net: mvneta: Only disable mvneta_bm for 64-bits

Actually only the mvneta_bm support is not 64-bits compatible. The mvneta code itself can run on 64-bits architecture. Signed-off-by: Gregory CLEMENT --- drivers/net/ethernet/marvell/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH v5 net-next 6/7] net: mvneta: Add network support for Armada 3700 SoC

From: Marcin Wojtas Armada 3700 is a new ARMv8 SoC from Marvell using same network controller as older Armada 370/38x/XP. There are however some differences that needed taking into account when adding support for it: * open default MBUS window to 4GB of DRAM - Armada 3700

[PATCH v5 net-next 0/7] Support Armada 37xx SoC (ARMv8 64-bits) in mvneta driver

Hi, The Armada 37xx is a new ARMv8 SoC from Marvell using same network controller as the older Armada 370/38x/XP SoCs. This series adapts the driver in order to be able to use it on this new SoC. The main changes are: - 64-bits support: the first patches allow using the driver on a 64-bit

[PATCH v5 net-next 6/7] net: mvneta: Add network support for Armada 3700 SoC

From: Marcin Wojtas Armada 3700 is a new ARMv8 SoC from Marvell using same network controller as older Armada 370/38x/XP. There are however some differences that needed taking into account when adding support for it: * open default MBUS window to 4GB of DRAM - Armada 3700 SoC's Mbus

[PATCH v5 net-next 0/7] Support Armada 37xx SoC (ARMv8 64-bits) in mvneta driver

Hi, The Armada 37xx is a new ARMv8 SoC from Marvell using same network controller as the older Armada 370/38x/XP SoCs. This series adapts the driver in order to be able to use it on this new SoC. The main changes are: - 64-bits support: the first patches allow using the driver on a 64-bit

[PATCH v5 net-next 7/7] ARM64: dts: marvell: Add network support for Armada 3700

Add neta nodes for network support both in device tree for the SoC and the board. Signed-off-by: Gregory CLEMENT --- arch/arm64/boot/dts/marvell/armada-3720-db.dts | 23 +++- arch/arm64/boot/dts/marvell/armada-37xx.dtsi | 23

[PATCH v5 net-next 7/7] ARM64: dts: marvell: Add network support for Armada 3700

Add neta nodes for network support both in device tree for the SoC and the board. Signed-off-by: Gregory CLEMENT --- arch/arm64/boot/dts/marvell/armada-3720-db.dts | 23 +++- arch/arm64/boot/dts/marvell/armada-37xx.dtsi | 23 +++- 2 files changed, 46

[PATCH v5 net-next 1/7] net: mvneta: Optimize rx path for small frame

For small frame reuse the phys_addr variable instead of accessing the uncacheable value in the rx descriptor. Signed-off-by: Gregory CLEMENT --- drivers/net/ethernet/marvell/mvneta.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v5 net-next 1/7] net: mvneta: Optimize rx path for small frame

For small frame reuse the phys_addr variable instead of accessing the uncacheable value in the rx descriptor. Signed-off-by: Gregory CLEMENT --- drivers/net/ethernet/marvell/mvneta.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/marvell/mvneta.c

[PATCH] x86/intel_rdt.c: Disable preempt for intel_rdt_sched_in() in move_myself()

From: Fenghua Yu intel_rdt_sched_in() calls this_cpu_ptr() read and write pqr_state and update PQR_ASSOC on current cpu. If execution of the function is preempted and switched to another CPU, the results are wrong. If CONFIG_DEBUG_PREEMPT is turned on, the issue is

[PATCH] x86/intel_rdt.c: Disable preempt for intel_rdt_sched_in() in move_myself()

From: Fenghua Yu intel_rdt_sched_in() calls this_cpu_ptr() read and write pqr_state and update PQR_ASSOC on current cpu. If execution of the function is preempted and switched to another CPU, the results are wrong. If CONFIG_DEBUG_PREEMPT is turned on, the issue is reported as "BUG:

Re: Odd build breakage in 4.9-rc7

On Wed, 2016-11-30 at 16:35 -0500, Jarod Wilson wrote: > Just to confirm, with CONFIG_TRIM_UNUSED_KSYMS unset, the build behaves > normally, no ERROR spew. And if MODVERSIONS is not set? My current theory is that setting MODVERSIONS, somehow, hides the ERROR spew. Because that could explain

Re: Odd build breakage in 4.9-rc7

On Wed, 2016-11-30 at 16:35 -0500, Jarod Wilson wrote: > Just to confirm, with CONFIG_TRIM_UNUSED_KSYMS unset, the build behaves > normally, no ERROR spew. And if MODVERSIONS is not set? My current theory is that setting MODVERSIONS, somehow, hides the ERROR spew. Because that could explain

Re: [GIT PULL 2/3] ARM: dts: exynos: DT for v4.10, second round

On Thursday, November 24, 2016 8:08:28 AM CET Krzysztof Kozlowski wrote: > > Samsung DeviceTree second update for v4.10: > 1. Cleanups in MSHC nodes. > 2. Enable ADC on Odroid boards. > 3. Fix interrupt flags on recently added DMA

Re: [PATCH] dt-bindings: document how to setup rockchip timers as clocksource

> 1 дек. 2016 г., в 0:30, Rob Herring написал(а): > > 1st and 2nd are ambiguous. Plus this is an OS implementation detail that > doesn't belong in the binding. > >> +If you want to bind specific timer as clockevent (i.e. one from alive >> subsystem) >> +and specific timer as

Re: [GIT PULL 2/3] ARM: dts: exynos: DT for v4.10, second round

On Thursday, November 24, 2016 8:08:28 AM CET Krzysztof Kozlowski wrote: > > Samsung DeviceTree second update for v4.10: > 1. Cleanups in MSHC nodes. > 2. Enable ADC on Odroid boards. > 3. Fix interrupt flags on recently added DMA

Re: [PATCH] dt-bindings: document how to setup rockchip timers as clocksource

> 1 дек. 2016 г., в 0:30, Rob Herring написал(а): > > 1st and 2nd are ambiguous. Plus this is an OS implementation detail that > doesn't belong in the binding. > >> +If you want to bind specific timer as clockevent (i.e. one from alive >> subsystem) >> +and specific timer as clocksource, you

[PATCH 3/4] [media] lmedm04: make some string arrays static

It takes more .text to initialize these on the stack than they occupy in .rodata, so just make them static const. Signed-off-by: Rasmus Villemoes --- drivers/media/usb/dvb-usb-v2/lmedm04.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git

[PATCH 2/4] [media] lmedm04: change some static variables to automatic

ibuf and rbuf in lme2510_int_response are always assigned to before they are read, and their addresses do not escape the function, so they have no reason to be static. Signed-off-by: Rasmus Villemoes --- drivers/media/usb/dvb-usb-v2/lmedm04.c | 2 +- 1 file changed, 1

[PATCH 3/4] [media] lmedm04: make some string arrays static

It takes more .text to initialize these on the stack than they occupy in .rodata, so just make them static const. Signed-off-by: Rasmus Villemoes --- drivers/media/usb/dvb-usb-v2/lmedm04.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git

[PATCH 2/4] [media] lmedm04: change some static variables to automatic

ibuf and rbuf in lme2510_int_response are always assigned to before they are read, and their addresses do not escape the function, so they have no reason to be static. Signed-off-by: Rasmus Villemoes --- drivers/media/usb/dvb-usb-v2/lmedm04.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 4/4] [media] lmedm04: make lme2510_powerup a little smaller

gcc isn't smart enough to realize it can share most of the argument buildup and the actual function call between the two branches, so help it a little. Signed-off-by: Rasmus Villemoes --- drivers/media/usb/dvb-usb-v2/lmedm04.c | 5 + 1 file changed, 1 insertion(+),

[PATCH 4/4] [media] lmedm04: make lme2510_powerup a little smaller

gcc isn't smart enough to realize it can share most of the argument buildup and the actual function call between the two branches, so help it a little. Signed-off-by: Rasmus Villemoes --- drivers/media/usb/dvb-usb-v2/lmedm04.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff

Re: [PATCH 2/2] dt-bindings: Add DT bindings info for FlexRM mailbox driver

On Fri, Nov 25, 2016 at 10:05:51AM +0530, Anup Patel wrote: > This patch adds device tree bindings document for the FlexRM > mailbox driver. Bindings document h/w, not drivers. > > Reviewed-by: Ray Jui > Reviewed-by: Scott Branden >

[PATCH 1/4] [media] lmedm04: use %phN for hex dump

Using the %ph printf extension for hex dumps like this makes the generated code quite a bit smaller. Signed-off-by: Rasmus Villemoes --- drivers/media/usb/dvb-usb-v2/lmedm04.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git

Re: [PATCH 2/2] dt-bindings: Add DT bindings info for FlexRM mailbox driver

On Fri, Nov 25, 2016 at 10:05:51AM +0530, Anup Patel wrote: > This patch adds device tree bindings document for the FlexRM > mailbox driver. Bindings document h/w, not drivers. > > Reviewed-by: Ray Jui > Reviewed-by: Scott Branden > Signed-off-by: Anup Patel > --- >

[PATCH 1/4] [media] lmedm04: use %phN for hex dump

Using the %ph printf extension for hex dumps like this makes the generated code quite a bit smaller. Signed-off-by: Rasmus Villemoes --- drivers/media/usb/dvb-usb-v2/lmedm04.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/media/usb/dvb-usb-v2/lmedm04.c

Re: Add openrisc for-next branch to linux-next

Hi Stafford, On Wed, 30 Nov 2016 22:22:41 +0900 (JST) Stafford Horne wrote: > > I have been working on getting the OpenRISC backlog of fixes sorted out > for upstream. Can this branch be added to linux-next? > >git://github.com/openrisc/linux.git for-next > > These

Re: Add openrisc for-next branch to linux-next

Hi Stafford, On Wed, 30 Nov 2016 22:22:41 +0900 (JST) Stafford Horne wrote: > > I have been working on getting the OpenRISC backlog of fixes sorted out > for upstream. Can this branch be added to linux-next? > >git://github.com/openrisc/linux.git for-next > > These have been through a

Re: [PATCH v2 3/7] PWM: add pwm-stm32 DT bindings

On Thu, Nov 24, 2016 at 04:14:19PM +0100, Benjamin Gaignard wrote: > Define bindings for pwm-stm32 > > version 2: > - use parameters instead of compatible of handle the hardware configuration > > Signed-off-by: Benjamin Gaignard > --- >

Re: [PATCH v2 3/7] PWM: add pwm-stm32 DT bindings

On Thu, Nov 24, 2016 at 04:14:19PM +0100, Benjamin Gaignard wrote: > Define bindings for pwm-stm32 > > version 2: > - use parameters instead of compatible of handle the hardware configuration > > Signed-off-by: Benjamin Gaignard > --- > .../devicetree/bindings/pwm/pwm-stm32.txt | 37

Re: Odd build breakage in 4.9-rc7

On 2016-11-30 4:07 PM, Jarod Wilson wrote: On 2016-11-30 3:52 PM, Paul Bolle wrote: On Wed, 2016-11-30 at 12:24 -0500, Jarod Wilson wrote: Up second, once we're past the above, building modules goes splat: 8< $ make -s ARCH=x86_64 V=1 -j8 modules ... ERROR: "module_put"

Re: Odd build breakage in 4.9-rc7

On 2016-11-30 4:07 PM, Jarod Wilson wrote: On 2016-11-30 3:52 PM, Paul Bolle wrote: On Wed, 2016-11-30 at 12:24 -0500, Jarod Wilson wrote: Up second, once we're past the above, building modules goes splat: 8< $ make -s ARCH=x86_64 V=1 -j8 modules ... ERROR: "module_put"

Re: INFO: rcu_sched detected stalls on CPUs/tasks with `kswapd` and `mem_cgroup_shrink_node`

On Wed, Nov 30, 2016 at 06:50:16PM +0100, Peter Zijlstra wrote: > On Wed, Nov 30, 2016 at 06:05:57PM +0100, Michal Hocko wrote: > > On Wed 30-11-16 17:38:20, Peter Zijlstra wrote: > > > On Wed, Nov 30, 2016 at 06:29:55AM -0800, Paul E. McKenney wrote: > > > > We can, and you are correct that

Re: INFO: rcu_sched detected stalls on CPUs/tasks with `kswapd` and `mem_cgroup_shrink_node`

On Wed, Nov 30, 2016 at 06:50:16PM +0100, Peter Zijlstra wrote: > On Wed, Nov 30, 2016 at 06:05:57PM +0100, Michal Hocko wrote: > > On Wed 30-11-16 17:38:20, Peter Zijlstra wrote: > > > On Wed, Nov 30, 2016 at 06:29:55AM -0800, Paul E. McKenney wrote: > > > > We can, and you are correct that

Re: [PATCH] x86/kbuild: enable modversions for symbols exported from asm

On Wed, 2016-11-30 at 10:40 -0800, Linus Torvalds wrote: > > On Wed, Nov 30, 2016 at 10:18 AM, Nicholas Piggin wrote: > > > > Here's an initial rough hack at removing modversions. It gives an idea > > of the complexity we're carrying for this feature (keeping in mind most > >

Re: [PATCH] x86/kbuild: enable modversions for symbols exported from asm

On Wed, 2016-11-30 at 10:40 -0800, Linus Torvalds wrote: > > On Wed, Nov 30, 2016 at 10:18 AM, Nicholas Piggin wrote: > > > > Here's an initial rough hack at removing modversions. It gives an idea > > of the complexity we're carrying for this feature (keeping in mind most > > of the lines

Re: [PATCH] kernel/sysctl: return -EINVAL if write invalid val to ulong type sysctl

On Wed, 30 Nov 2016 18:30:52 +0800 Yisheng Xie wrote: > I tried to echo an invalid value to an unsigned long type sysctl on > 4.9.0-rc6: >linux:~# cat /proc/sys/vm/user_reserve_kbytes >131072 >linux:~# echo -1 > /proc/sys/vm/user_reserve_kbytes >linux:~#

Re: [PATCH] kernel/sysctl: return -EINVAL if write invalid val to ulong type sysctl

On Wed, 30 Nov 2016 18:30:52 +0800 Yisheng Xie wrote: > I tried to echo an invalid value to an unsigned long type sysctl on > 4.9.0-rc6: >linux:~# cat /proc/sys/vm/user_reserve_kbytes >131072 >linux:~# echo -1 > /proc/sys/vm/user_reserve_kbytes >linux:~# cat

Re: [PATCH] dt-bindings: document how to setup rockchip timers as clocksource

On Fri, Nov 25, 2016 at 01:12:16AM +0300, Alexander Kochetkov wrote: > The patch describes how to setup rockchip timers in device tree > so they can be used as clocksource. > > I'm going to implement this feature. > > Signed-off-by: Alexander Kochetkov > --- >

Re: [PATCH] dt-bindings: document how to setup rockchip timers as clocksource

On Fri, Nov 25, 2016 at 01:12:16AM +0300, Alexander Kochetkov wrote: > The patch describes how to setup rockchip timers in device tree > so they can be used as clocksource. > > I'm going to implement this feature. > > Signed-off-by: Alexander Kochetkov > --- >

Re: [PATCH] scsi/ipr: Fix runaway IRQs when falling back from MSI to LSI

Looks good. Thanks! Here is an updated version that should apply cleanly on top of scsi-next. 8< From: Benjamin Herrenschmidt LSIs must be ack'ed with an MMIO otherwise they remain asserted forever. This is controlled by the "clear_isr" flag. While we set that flag

Re: [PATCH] scsi/ipr: Fix runaway IRQs when falling back from MSI to LSI

Looks good. Thanks! Here is an updated version that should apply cleanly on top of scsi-next. 8< From: Benjamin Herrenschmidt LSIs must be ack'ed with an MMIO otherwise they remain asserted forever. This is controlled by the "clear_isr" flag. While we set that flag properly when deciding

Re: [PATCH v4 net-next 3/7] net: mvneta: Use cacheable memory to store the rx buffer virtual address

Hi David, On mer., nov. 30 2016, David Miller wrote: > From: Gregory CLEMENT > Date: Tue, 29 Nov 2016 15:55:21 +0100 > >> +/* Virtual address of the RX buffer */ >> +void **buf_virt_addr; >> + >> /* Virtual address of the

Re: [PATCH v4 net-next 3/7] net: mvneta: Use cacheable memory to store the rx buffer virtual address

Hi David, On mer., nov. 30 2016, David Miller wrote: > From: Gregory CLEMENT > Date: Tue, 29 Nov 2016 15:55:21 +0100 > >> +/* Virtual address of the RX buffer */ >> +void **buf_virt_addr; >> + >> /* Virtual address of the RX DMA descriptors array */ >> struct

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