[PATCH 0/3] net: TCP/IP: A few minor cleanups

The following patch series is an ad hoc "cleanup" that I made while perusing the code (I'm not well versed in this code, so I would not be surprised if there were objections to the changes): [1] net: __sock_cmsg_send(): Remove unused parameter `msg' [2] net: inet_recvmsg(): Remove unnecessary

[PATCH 0/3] net: TCP/IP: A few minor cleanups

The following patch series is an ad hoc "cleanup" that I made while perusing the code (I'm not well versed in this code, so I would not be surprised if there were objections to the changes): [1] net: __sock_cmsg_send(): Remove unused parameter `msg' [2] net: inet_recvmsg(): Remove unnecessary

Re: linux-next: build warning after merge of the vfs tree

Hi, On Fri, Sep 08, 2017 at 09:25:45AM +1000, Stephen Rothwell wrote: > Hi Al, > > After merging the vfs tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > kernel/signal.c: In function 'C_SYSC_rt_sigaction': > kernel/signal.c:3405:19: warning: unused variable

Re: linux-next: build warning after merge of the vfs tree

Hi, On Fri, Sep 08, 2017 at 09:25:45AM +1000, Stephen Rothwell wrote: > Hi Al, > > After merging the vfs tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > kernel/signal.c: In function 'C_SYSC_rt_sigaction': > kernel/signal.c:3405:19: warning: unused variable

Re: [PATCH v2] leds: pca955x: Don't invert requested value in pca955x_gpio_set_value()

On Sat, Sep 2, 2017 at 2:36 AM, Cédric Le Goater wrote: > On 09/01/2017 07:38 AM, Andrew Jeffery wrote: >> Rework leds-pca955x so that we avoid the incorrect inversion and clarify >> the semantics with respect to GPIO. >> >> Signed-off-by: Andrew Jeffery > >

Re: [PATCH v2] leds: pca955x: Don't invert requested value in pca955x_gpio_set_value()

On Sat, Sep 2, 2017 at 2:36 AM, Cédric Le Goater wrote: > On 09/01/2017 07:38 AM, Andrew Jeffery wrote: >> Rework leds-pca955x so that we avoid the incorrect inversion and clarify >> the semantics with respect to GPIO. >> >> Signed-off-by: Andrew Jeffery > > Reviewed-by: Cédric Le Goater I

Re: [PATCH] ASoC: fsl_ssi: Override bit clock rate based on slot number

On Thu, Sep 07, 2017 at 10:23:43PM -0700, Nicolin Chen wrote: > The set_sysclk() now is used to override the output bit clock rate. > But this is not a common way to implement a set_dai_sysclk(). And > this creates a problem when a general machine driver (simple-card > for example) tries to do

Re: [PATCH] ASoC: fsl_ssi: Override bit clock rate based on slot number

On Thu, Sep 07, 2017 at 10:23:43PM -0700, Nicolin Chen wrote: > The set_sysclk() now is used to override the output bit clock rate. > But this is not a common way to implement a set_dai_sysclk(). And > this creates a problem when a general machine driver (simple-card > for example) tries to do

[PATCH v2] netfilter: xt_hashlimit: fix build error caused by 64bit division

64bit division causes build/link errors on 32bit architectures. It prints out error messages like: ERROR: "__aeabi_uldivmod" [net/netfilter/xt_hashlimit.ko] undefined! The value of avg passed through by userspace in BYTE mode cannot exceed U32_MAX. Which means 64bit division in user2rate_bytes

[PATCH v2] netfilter: xt_hashlimit: fix build error caused by 64bit division

64bit division causes build/link errors on 32bit architectures. It prints out error messages like: ERROR: "__aeabi_uldivmod" [net/netfilter/xt_hashlimit.ko] undefined! The value of avg passed through by userspace in BYTE mode cannot exceed U32_MAX. Which means 64bit division in user2rate_bytes

Re: Current mainline git (24e700e291d52bd2) hangs when building e.g. perf

On 2017.09.07 at 08:28 +0200, Markus Trippelsdorf wrote: > On 2017.09.06 at 15:15 +0200, Markus Trippelsdorf wrote: > > On 2017.09.06 at 14:52 +0200, Thomas Gleixner wrote: > > > On Tue, 5 Sep 2017, Markus Trippelsdorf wrote: > > > > On 2017.09.05 at 10:53 +0200, Peter Zijlstra wrote: > > > > > >

Re: Current mainline git (24e700e291d52bd2) hangs when building e.g. perf

On 2017.09.07 at 08:28 +0200, Markus Trippelsdorf wrote: > On 2017.09.06 at 15:15 +0200, Markus Trippelsdorf wrote: > > On 2017.09.06 at 14:52 +0200, Thomas Gleixner wrote: > > > On Tue, 5 Sep 2017, Markus Trippelsdorf wrote: > > > > On 2017.09.05 at 10:53 +0200, Peter Zijlstra wrote: > > > > > >

[PATCH] ASoC: fsl-asoc-card: Don't error out if ENOTSUPP

The snd_soc_component_set_sysclk() and snd_soc_dai_set_tdm_slot() in the soc-core.c will return -ENOTSUPP if there is no function implementation for them in the dai and component drivers. So this patch tries to ignore this errno. Signed-off-by: Nicolin Chen ---

[PATCH] ASoC: fsl-asoc-card: Don't error out if ENOTSUPP

The snd_soc_component_set_sysclk() and snd_soc_dai_set_tdm_slot() in the soc-core.c will return -ENOTSUPP if there is no function implementation for them in the dai and component drivers. So this patch tries to ignore this errno. Signed-off-by: Nicolin Chen --- sound/soc/fsl/fsl-asoc-card.c |

[PATCH] ASoC: fsl_ssi: Override bit clock rate based on slot number

The set_sysclk() now is used to override the output bit clock rate. But this is not a common way to implement a set_dai_sysclk(). And this creates a problem when a general machine driver (simple-card for example) tries to do set_dai_sysclk() by passing an input clock rate for the baud clock

[PATCH] ASoC: fsl_ssi: Override bit clock rate based on slot number

The set_sysclk() now is used to override the output bit clock rate. But this is not a common way to implement a set_dai_sysclk(). And this creates a problem when a general machine driver (simple-card for example) tries to do set_dai_sysclk() by passing an input clock rate for the baud clock

Re: [PATCH] ttyport: trivial fix for some typo in comments

On Thu, Sep 07, 2017 at 10:51:08PM +0200, Antonio Borneo wrote: > Signed-off-by: Antonio Borneo > --- > To: Greg Kroah-Hartman > To: Jiri Slaby > Cc: Jiri Kosina > Cc: linux-kernel@vger.kernel.org > ---

Re: [PATCH] ttyport: trivial fix for some typo in comments

On Thu, Sep 07, 2017 at 10:51:08PM +0200, Antonio Borneo wrote: > Signed-off-by: Antonio Borneo > --- > To: Greg Kroah-Hartman > To: Jiri Slaby > Cc: Jiri Kosina > Cc: linux-kernel@vger.kernel.org > --- > drivers/tty/tty_port.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) I

Re: [PATCH] hwmon: pmbus: Make reg check and clear faults functions return errors

On Thu, 2017-09-07 at 22:14 -0700, Guenter Roeck wrote: > On 09/07/2017 08:40 PM, Andrew Jeffery wrote: > > On Fri, 2017-09-08 at 12:51 +1000, Andrew Jeffery wrote: > > > > I can't test with devicetree. x86 system. > > > >    > > > > 2,100+ iterations with your driver, no failures. > > > > > >

Re: [PATCH net-next v2 01/10] net: dsa: add debugfs interface

I agree you shouldn't be using debugfs for this, but in the future, if you do write debugfs code, please take the following review into account: On Mon, Aug 28, 2017 at 03:17:39PM -0400, Vivien Didelot wrote: > +static int dsa_debugfs_create_port(struct dsa_switch *ds, int port) > +{ > +

Re: [PATCH] hwmon: pmbus: Make reg check and clear faults functions return errors

On Thu, 2017-09-07 at 22:14 -0700, Guenter Roeck wrote: > On 09/07/2017 08:40 PM, Andrew Jeffery wrote: > > On Fri, 2017-09-08 at 12:51 +1000, Andrew Jeffery wrote: > > > > I can't test with devicetree. x86 system. > > > >    > > > > 2,100+ iterations with your driver, no failures. > > > > > >

Re: [PATCH net-next v2 01/10] net: dsa: add debugfs interface

I agree you shouldn't be using debugfs for this, but in the future, if you do write debugfs code, please take the following review into account: On Mon, Aug 28, 2017 at 03:17:39PM -0400, Vivien Didelot wrote: > +static int dsa_debugfs_create_port(struct dsa_switch *ds, int port) > +{ > +

[PATCH v3] pci: dwc: dra7xx: Add shutdown handler to cleanly turn off clocks

Add shutdown handler to cleanly turn off clocks. This will help in cases of kexec where in a new kernel can boot abruptly. Signed-off-by: Keerthy Acked-by: Kishon Vijay Abraham I --- Changes in v3: * Pushed the function outside #ifdef CONFIG_PM_SLEEP. *

[PATCH v3] pci: dwc: dra7xx: Add shutdown handler to cleanly turn off clocks

Add shutdown handler to cleanly turn off clocks. This will help in cases of kexec where in a new kernel can boot abruptly. Signed-off-by: Keerthy Acked-by: Kishon Vijay Abraham I --- Changes in v3: * Pushed the function outside #ifdef CONFIG_PM_SLEEP. * Added more details to commit log.

Re: [PATCH] hwmon: pmbus: Make reg check and clear faults functions return errors

On 09/07/2017 08:40 PM, Andrew Jeffery wrote: On Fri, 2017-09-08 at 12:51 +1000, Andrew Jeffery wrote: I can't test with devicetree. x86 system. 2,100+ iterations with your driver, no failures. Great. I really appreciate your testing here, so thanks for your efforts. I owe you a few drinks

Re: [PATCH] hwmon: pmbus: Make reg check and clear faults functions return errors

On 09/07/2017 08:40 PM, Andrew Jeffery wrote: On Fri, 2017-09-08 at 12:51 +1000, Andrew Jeffery wrote: I can't test with devicetree. x86 system. 2,100+ iterations with your driver, no failures. Great. I really appreciate your testing here, so thanks for your efforts. I owe you a few drinks

[PATCH v2] ARM: dts: Add initial Pistachio i.mx6q board support.

From: YuanCheng Cheng Working items: - 800/433 MHz (CPU/DDR3) - 2GB of RAM (DDR3) - 4GB of NAND FLASH - 1T1R WiFi 2.4 GHz - Power management support - 1x 10/100/1000 Mbps Ethernet WAN port - 2x USB 2.0 Host - PCIe - HDMI/VGA/LVDS display - 1x UART for RS232/422/485 - 2x UART

[PATCH v2] ARM: dts: Add initial Pistachio i.mx6q board support.

From: YuanCheng Cheng Working items: - 800/433 MHz (CPU/DDR3) - 2GB of RAM (DDR3) - 4GB of NAND FLASH - 1T1R WiFi 2.4 GHz - Power management support - 1x 10/100/1000 Mbps Ethernet WAN port - 2x USB 2.0 Host - PCIe - HDMI/VGA/LVDS display - 1x UART for RS232/422/485 - 2x UART for RS232 - 1x UART

Re: [PATCH 1/2] x86/mm: Get rid of VM_BUG_ON in switch_tlb_irqs_off()

On Thu, Sep 7, 2017 at 10:06 PM, Andy Lutomirski wrote: > If we hit the VM_BUG_ON(), we're detecting a genuinely bad situation, > but we're very unlikely to get a useful call trace. Sigh, typo below. Ingo, if you apply this version, can you fix it? > +* a

Re: [PATCH 1/2] x86/mm: Get rid of VM_BUG_ON in switch_tlb_irqs_off()

On Thu, Sep 7, 2017 at 10:06 PM, Andy Lutomirski wrote: > If we hit the VM_BUG_ON(), we're detecting a genuinely bad situation, > but we're very unlikely to get a useful call trace. Sigh, typo below. Ingo, if you apply this version, can you fix it? > +* a global flush to

Re: [PATCH] hwmon: pmbus: Make reg check and clear faults functions return errors

On Thu, 2017-09-07 at 21:43 -0700, Guenter Roeck wrote: > On 09/07/2017 08:40 PM, Andrew Jeffery wrote: > > On Fri, 2017-09-08 at 12:51 +1000, Andrew Jeffery wrote: > > > > I can't test with devicetree. x86 system. > > > >    > > > > 2,100+ iterations with your driver, no failures. > > > > > >

Re: [PATCH] hwmon: pmbus: Make reg check and clear faults functions return errors

On Thu, 2017-09-07 at 21:43 -0700, Guenter Roeck wrote: > On 09/07/2017 08:40 PM, Andrew Jeffery wrote: > > On Fri, 2017-09-08 at 12:51 +1000, Andrew Jeffery wrote: > > > > I can't test with devicetree. x86 system. > > > >    > > > > 2,100+ iterations with your driver, no failures. > > > > > >

[PATCH 1/2] x86/mm: Get rid of VM_BUG_ON in switch_tlb_irqs_off()

If we hit the VM_BUG_ON(), we're detecting a genuinely bad situation, but we're very unlikely to get a useful call trace. Make it a warning instead. Signed-off-by: Andy Lutomirski --- arch/x86/mm/tlb.c | 22 +- 1 file changed, 21 insertions(+), 1

[PATCH 2/2] x86/hibernate/64: Mask off CR3's PCID bits in the saved CR3

Jiri reported a resume-from-hibernation failure triggered by PCID. The root cause appears to be rather odd. The hibernation asm restores a CR3 value that comes from the image header. If the image kernel has PCID on, it's entirely reasonable for this CR3 value to have one of the low 12 bits set.

[PATCH 0/2] More PCID fixes

This gets rid of the problematic VM_BUG_ON and fixes hibernation. Andy Lutomirski (2): x86/mm: Get rid of VM_BUG_ON in switch_tlb_irqs_off() x86/hibernate/64: Mask off CR3's PCID bits in the saved CR3 arch/x86/mm/tlb.c | 22 +- arch/x86/power/hibernate_64.c |

[PATCH 1/2] x86/mm: Get rid of VM_BUG_ON in switch_tlb_irqs_off()

If we hit the VM_BUG_ON(), we're detecting a genuinely bad situation, but we're very unlikely to get a useful call trace. Make it a warning instead. Signed-off-by: Andy Lutomirski --- arch/x86/mm/tlb.c | 22 +- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git

[PATCH 2/2] x86/hibernate/64: Mask off CR3's PCID bits in the saved CR3

Jiri reported a resume-from-hibernation failure triggered by PCID. The root cause appears to be rather odd. The hibernation asm restores a CR3 value that comes from the image header. If the image kernel has PCID on, it's entirely reasonable for this CR3 value to have one of the low 12 bits set.

[PATCH 0/2] More PCID fixes

This gets rid of the problematic VM_BUG_ON and fixes hibernation. Andy Lutomirski (2): x86/mm: Get rid of VM_BUG_ON in switch_tlb_irqs_off() x86/hibernate/64: Mask off CR3's PCID bits in the saved CR3 arch/x86/mm/tlb.c | 22 +- arch/x86/power/hibernate_64.c |

Re: [PATCH v2] pci: dwc: dra7xx: Add shutdown handler to cleanly turn off clocks

On Wednesday 06 September 2017 07:26 PM, Keerthy wrote: > Add shutdown handler to cleanly turn off clocks. > > Signed-off-by: Keerthy > Acked-by: Kishon Vijay Abraham I > --- > > Changes in v2: > > * used a local dev pointer instead of dereferencing dev at

Re: [PATCH v2] pci: dwc: dra7xx: Add shutdown handler to cleanly turn off clocks

On Wednesday 06 September 2017 07:26 PM, Keerthy wrote: > Add shutdown handler to cleanly turn off clocks. > > Signed-off-by: Keerthy > Acked-by: Kishon Vijay Abraham I > --- > > Changes in v2: > > * used a local dev pointer instead of dereferencing dev at multiple places. > *

Re: [PATCH v8 3/3] drm/rockchip: Add support for Rockchip Soc LVDS

Am Freitag, 8. September 2017, 09:23:09 CEST schrieb Mark yao: > On 2017年09月07日 20:09, Heiko Stübner wrote: > > Hi Mark, > > > > Am Donnerstag, 7. September 2017, 18:16:29 CEST schrieb Mark yao: > >> Looks good for me, so: > >> Reviewed-by: Mark Yao > >> > >> I'd like to

Re: [PATCH v8 3/3] drm/rockchip: Add support for Rockchip Soc LVDS

Am Freitag, 8. September 2017, 09:23:09 CEST schrieb Mark yao: > On 2017年09月07日 20:09, Heiko Stübner wrote: > > Hi Mark, > > > > Am Donnerstag, 7. September 2017, 18:16:29 CEST schrieb Mark yao: > >> Looks good for me, so: > >> Reviewed-by: Mark Yao > >> > >> I'd like to apply these lvds patches

Re: [GIT PULL] Security subsystem updates for 4.14

On Thu, 7 Sep 2017, Linus Torvalds wrote: > On Mon, Sep 4, 2017 at 3:29 AM, James Morris wrote: > > > > IMA: > > - A new integrity_read file operation method, avoids races when > > calculating file hashes > > Honestly, this seems really odd. > > It documents that it

Re: [GIT PULL] Security subsystem updates for 4.14

On Thu, 7 Sep 2017, Linus Torvalds wrote: > On Mon, Sep 4, 2017 at 3:29 AM, James Morris wrote: > > > > IMA: > > - A new integrity_read file operation method, avoids races when > > calculating file hashes > > Honestly, this seems really odd. > > It documents that it needs to be called

[PATCH] Staging: iio: adc: Added Space around binary op.

Added space around(one on each side of) binary operator(-) as preferred according to kernel coding style. Signed-off-by: Himanshi Jain --- drivers/staging/iio/adc/ad7192.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] Staging: iio: adc: Added Space around binary op.

Added space around(one on each side of) binary operator(-) as preferred according to kernel coding style. Signed-off-by: Himanshi Jain --- drivers/staging/iio/adc/ad7192.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/iio/adc/ad7192.c

Re: [PATCH] hwmon: pmbus: Make reg check and clear faults functions return errors

On 09/07/2017 08:40 PM, Andrew Jeffery wrote: On Fri, 2017-09-08 at 12:51 +1000, Andrew Jeffery wrote: I can't test with devicetree. x86 system. 2,100+ iterations with your driver, no failures. Great. I really appreciate your testing here, so thanks for your efforts. I owe you a few drinks

Re: [PATCH] hwmon: pmbus: Make reg check and clear faults functions return errors

On 09/07/2017 08:40 PM, Andrew Jeffery wrote: On Fri, 2017-09-08 at 12:51 +1000, Andrew Jeffery wrote: I can't test with devicetree. x86 system. 2,100+ iterations with your driver, no failures. Great. I really appreciate your testing here, so thanks for your efforts. I owe you a few drinks

[PATCH v3 3/3] pmbus: Add driver for Maxim MAX31785 Intelligent Fan Controller

The Maxim MAX31785 is a PMBus device providing closed-loop, multi-channel fan management with temperature and remote voltage sensing. Various fan control features are provided, including PWM frequency control, temperature hysteresis, dual tachometer measurements, and fan health monitoring. The

[PATCH v3 3/3] pmbus: Add driver for Maxim MAX31785 Intelligent Fan Controller

The Maxim MAX31785 is a PMBus device providing closed-loop, multi-channel fan management with temperature and remote voltage sensing. Various fan control features are provided, including PWM frequency control, temperature hysteresis, dual tachometer measurements, and fan health monitoring. The

[PATCH v3 2/3] hwmon: pmbus: Add fan control support

Expose fanX_target, pwmX and pwmX_enable hwmon sysfs attributes. Fans in a PMBus device are driven by the configuration of two registers: FAN_CONFIG_x_y and FAN_COMMAND_x: FAN_CONFIG_x_y dictates how the fan and the tacho operate (if installed), while FAN_COMMAND_x sets the desired fan rate. The

[PATCH v3 2/3] hwmon: pmbus: Add fan control support

Expose fanX_target, pwmX and pwmX_enable hwmon sysfs attributes. Fans in a PMBus device are driven by the configuration of two registers: FAN_CONFIG_x_y and FAN_COMMAND_x: FAN_CONFIG_x_y dictates how the fan and the tacho operate (if installed), while FAN_COMMAND_x sets the desired fan rate. The

[PATCH v3 1/3] dt-bindings: hwmon: pmbus: Add Maxim MAX31785 documentation

Signed-off-by: Andrew Jeffery --- .../devicetree/bindings/hwmon/pmbus/max31785.txt | 158 + 1 file changed, 158 insertions(+) create mode 100644 Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt diff --git

[PATCH v3 1/3] dt-bindings: hwmon: pmbus: Add Maxim MAX31785 documentation

Signed-off-by: Andrew Jeffery --- .../devicetree/bindings/hwmon/pmbus/max31785.txt | 158 + 1 file changed, 158 insertions(+) create mode 100644 Documentation/devicetree/bindings/hwmon/pmbus/max31785.txt diff --git

[PATCH v3 0/3] pmbus: Expand fan support and add MAX31785 driver

Hello, These three patches lay the ground work for fan control in the pmbus core and introduce a driver for the MAX31785 Intelligent Fan Controller that makes use of the new control features. Since v2[1] I've addressed Rob's comments on the bindings, integrating the thermal support and cleaning

[PATCH v3 0/3] pmbus: Expand fan support and add MAX31785 driver

Hello, These three patches lay the ground work for fan control in the pmbus core and introduce a driver for the MAX31785 Intelligent Fan Controller that makes use of the new control features. Since v2[1] I've addressed Rob's comments on the bindings, integrating the thermal support and cleaning

Re: [PATCH] initramfs: Fix disabling of initramfs (and its compression)

On 09/07/2017 06:19 AM, Nicholas Piggin wrote: > On Thu, 7 Sep 2017 05:50:30 -0700 > Florian Fainelli wrote: > >> On 08/28/2017 08:09 PM, Nicholas Piggin wrote: >>> On Mon, 28 Aug 2017 13:03:31 -0700 >>> Florian Fainelli wrote: >>> On

Re: [PATCH] initramfs: Fix disabling of initramfs (and its compression)

On 09/07/2017 06:19 AM, Nicholas Piggin wrote: > On Thu, 7 Sep 2017 05:50:30 -0700 > Florian Fainelli wrote: > >> On 08/28/2017 08:09 PM, Nicholas Piggin wrote: >>> On Mon, 28 Aug 2017 13:03:31 -0700 >>> Florian Fainelli wrote: >>> On 05/21/2017 07:46 PM, Nicholas Piggin wrote:

Re: [RFC 08/17] x86/asm/64: De-Xen-ify our NMI code

On 07/09/17 20:38, Andy Lutomirski wrote: > On Thu, Sep 7, 2017 at 2:34 AM, Juergen Gross wrote: >> On 06/09/17 23:36, Andy Lutomirski wrote: >>> Xen PV is fundamentally incompatible with our fancy NMI code: it >>> doesn't use IST at all, and Xen entries clobber two stack slots

Re: [RFC 08/17] x86/asm/64: De-Xen-ify our NMI code

On 07/09/17 20:38, Andy Lutomirski wrote: > On Thu, Sep 7, 2017 at 2:34 AM, Juergen Gross wrote: >> On 06/09/17 23:36, Andy Lutomirski wrote: >>> Xen PV is fundamentally incompatible with our fancy NMI code: it >>> doesn't use IST at all, and Xen entries clobber two stack slots >>> below the

Re: [PATCH v2 15/16] dmaengine: bcm-sba-raid: Add debugfs support

On Thu, Sep 07, 2017 at 09:37:32PM +0200, Greg KH wrote: > On Fri, Aug 18, 2017 at 10:56:13AM +0530, Vinod Koul wrote: > > On Fri, Aug 18, 2017 at 10:33:54AM +0530, Anup Patel wrote: > > > On Thu, Aug 17, 2017 at 1:31 PM, Vinod Koul wrote: > > > > On Tue, Aug 01, 2017 at

Re: [PATCH v2 15/16] dmaengine: bcm-sba-raid: Add debugfs support

On Thu, Sep 07, 2017 at 09:37:32PM +0200, Greg KH wrote: > On Fri, Aug 18, 2017 at 10:56:13AM +0530, Vinod Koul wrote: > > On Fri, Aug 18, 2017 at 10:33:54AM +0530, Anup Patel wrote: > > > On Thu, Aug 17, 2017 at 1:31 PM, Vinod Koul wrote: > > > > On Tue, Aug 01, 2017 at 04:07:59PM +0530, Anup

Re: [PATCH v2 1/4] dt-bindings: hwmon: pmbus: Add Maxim MAX31785 documentation

On Mon, 2017-08-14 at 11:25 +0930, Andrew Jeffery wrote: > On Thu, 2017-08-10 at 11:13 -0500, Rob Herring wrote: > > On Wed, Aug 02, 2017 at 04:45:38PM +0930, Andrew Jeffery wrote: > > > > > Signed-off-by: Andrew Jeffery > > >  > > > --- > > >  

Re: [PATCH v2 1/4] dt-bindings: hwmon: pmbus: Add Maxim MAX31785 documentation

On Mon, 2017-08-14 at 11:25 +0930, Andrew Jeffery wrote: > On Thu, 2017-08-10 at 11:13 -0500, Rob Herring wrote: > > On Wed, Aug 02, 2017 at 04:45:38PM +0930, Andrew Jeffery wrote: > > > > > Signed-off-by: Andrew Jeffery > > >  > > > --- > > >  .../devicetree/bindings/hwmon/pmbus/max31785.txt   |

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

Hi all, On Fri, 8 Sep 2017 12:49:59 +1000 Stephen Rothwell wrote: > > OK, so today I have applied this instead (which is the same as dropping > mm-thp-enable-thp-migration-in-generic-path-fix-fix-fix): > > From: Stephen Rothwell > Date: Fri, 8 Sep

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

Hi all, On Fri, 8 Sep 2017 12:49:59 +1000 Stephen Rothwell wrote: > > OK, so today I have applied this instead (which is the same as dropping > mm-thp-enable-thp-migration-in-generic-path-fix-fix-fix): > > From: Stephen Rothwell > Date: Fri, 8 Sep 2017 12:40:39 +1000 > Subject: [PATCH]

Re: [PATCH] hwmon: pmbus: Make reg check and clear faults functions return errors

On Fri, 2017-09-08 at 12:51 +1000, Andrew Jeffery wrote: > > I can't test with devicetree. x86 system. > >  > > 2,100+ iterations with your driver, no failures. > > Great. I really appreciate your testing here, so thanks for your > efforts. I owe you a few drinks if we ever happen to meet.

Re: [patch v7 3/4] Documentation: jtag: Add bindings for Aspeed SoC 24xx and 25xx families JTAG master driver

On Sat, Sep 2, 2017 at 1:36 AM, Oleksandr Shamray wrote: > diff --git a/Documentation/devicetree/bindings/jtag/aspeed-jtag.txt > b/Documentation/devicetree/bindings/jtag/aspeed-jtag.txt > new file mode 100644 > index 000..f4ded49 > --- /dev/null > +++

Re: [PATCH] hwmon: pmbus: Make reg check and clear faults functions return errors

On Fri, 2017-09-08 at 12:51 +1000, Andrew Jeffery wrote: > > I can't test with devicetree. x86 system. > >  > > 2,100+ iterations with your driver, no failures. > > Great. I really appreciate your testing here, so thanks for your > efforts. I owe you a few drinks if we ever happen to meet.

Re: [patch v7 3/4] Documentation: jtag: Add bindings for Aspeed SoC 24xx and 25xx families JTAG master driver

On Sat, Sep 2, 2017 at 1:36 AM, Oleksandr Shamray wrote: > diff --git a/Documentation/devicetree/bindings/jtag/aspeed-jtag.txt > b/Documentation/devicetree/bindings/jtag/aspeed-jtag.txt > new file mode 100644 > index 000..f4ded49 > --- /dev/null > +++

Re: [patch v7 2/4] drivers: jtag: Add Aspeed SoC 24xx and 25xx families JTAG master driver

Hello Oleksandr, On Sat, Sep 2, 2017 at 1:36 AM, Oleksandr Shamray wrote: > Driver adds support of Aspeed 2500/2400 series SOC JTAG master controller. Looks good. I have some small comments. The most important is the compatible string. > --- a/drivers/jtag/Kconfig >

Re: [patch v7 2/4] drivers: jtag: Add Aspeed SoC 24xx and 25xx families JTAG master driver

Hello Oleksandr, On Sat, Sep 2, 2017 at 1:36 AM, Oleksandr Shamray wrote: > Driver adds support of Aspeed 2500/2400 series SOC JTAG master controller. Looks good. I have some small comments. The most important is the compatible string. > --- a/drivers/jtag/Kconfig > +++ b/drivers/jtag/Kconfig

Re: [PATCH v15 3/5] virtio-balloon: VIRTIO_BALLOON_F_SG

On Tue, Aug 29, 2017 at 11:09:18AM +0800, Wei Wang wrote: > On 08/29/2017 02:03 AM, Michael S. Tsirkin wrote: > > On Mon, Aug 28, 2017 at 06:08:31PM +0800, Wei Wang wrote: > > > Add a new feature, VIRTIO_BALLOON_F_SG, which enables the transfer > > > of balloon (i.e. inflated/deflated) pages using

Re: [PATCH v15 3/5] virtio-balloon: VIRTIO_BALLOON_F_SG

On Tue, Aug 29, 2017 at 11:09:18AM +0800, Wei Wang wrote: > On 08/29/2017 02:03 AM, Michael S. Tsirkin wrote: > > On Mon, Aug 28, 2017 at 06:08:31PM +0800, Wei Wang wrote: > > > Add a new feature, VIRTIO_BALLOON_F_SG, which enables the transfer > > > of balloon (i.e. inflated/deflated) pages using

linux-next: Tree for Sep 8

Hi all, Please do not add any v4.15 related material to your linux-next included branches until after v4.14-rc1 has been released. Changes since 20170907: Removed tree: wberr at maintainer's request (finished with) The akpm-current tree still had its build failure for which I applied a fix

linux-next: Tree for Sep 8

Hi all, Please do not add any v4.15 related material to your linux-next included branches until after v4.14-rc1 has been released. Changes since 20170907: Removed tree: wberr at maintainer's request (finished with) The akpm-current tree still had its build failure for which I applied a fix

Re: [PATCH] selftests/seccomp: Support glibc 2.26 siginfo_t.h

On Thu, Sep 7, 2017 at 8:19 PM, Seth Forshee wrote: > On Thu, Sep 07, 2017 at 04:32:46PM -0700, Kees Cook wrote: >> The 2.26 release of glibc changed how siginfo_t is defined, and the earlier >> work-around to using the kernel definition are no longer needed. The old

Re: [PATCH] selftests/seccomp: Support glibc 2.26 siginfo_t.h

On Thu, Sep 7, 2017 at 8:19 PM, Seth Forshee wrote: > On Thu, Sep 07, 2017 at 04:32:46PM -0700, Kees Cook wrote: >> The 2.26 release of glibc changed how siginfo_t is defined, and the earlier >> work-around to using the kernel definition are no longer needed. The old >> way needs to stay around

Re: [PATCH V2 13/13] thermal/drivers/hisi: Remove mutex_lock in the code

On Mon, Sep 04, 2017 at 09:56:12PM +0200, Daniel Lezcano wrote: > The mutex is used to protect against writes in the configuration register. > > That happens at probe time, with no possible race yet. > > Then when the module is unloaded and at suspend/resume. > > When the module is unloaded, it

Re: [PATCH V2 13/13] thermal/drivers/hisi: Remove mutex_lock in the code

On Mon, Sep 04, 2017 at 09:56:12PM +0200, Daniel Lezcano wrote: > The mutex is used to protect against writes in the configuration register. > > That happens at probe time, with no possible race yet. > > Then when the module is unloaded and at suspend/resume. > > When the module is unloaded, it

Re: [PATCH V2 09/13] thermal/drivers/hisi: Remove costly sensor inspection

On Mon, Sep 04, 2017 at 09:56:08PM +0200, Daniel Lezcano wrote: > The sensor is all setup, bind, resetted, acked, etc... every single second. > > That was the way to workaround a problem with the interrupt bouncing again and > again. > > With the following changes, we fix all in one: > > - Do

Re: [PATCH V2 09/13] thermal/drivers/hisi: Remove costly sensor inspection

On Mon, Sep 04, 2017 at 09:56:08PM +0200, Daniel Lezcano wrote: > The sensor is all setup, bind, resetted, acked, etc... every single second. > > That was the way to workaround a problem with the interrupt bouncing again and > again. > > With the following changes, we fix all in one: > > - Do

Re: [PATCH] selftests/seccomp: Support glibc 2.26 siginfo_t.h

On Thu, Sep 07, 2017 at 04:32:46PM -0700, Kees Cook wrote: > The 2.26 release of glibc changed how siginfo_t is defined, and the earlier > work-around to using the kernel definition are no longer needed. The old > way needs to stay around for a while, though. > > Reported-by: Seth Forshee

Re: [PATCH] selftests/seccomp: Support glibc 2.26 siginfo_t.h

On Thu, Sep 07, 2017 at 04:32:46PM -0700, Kees Cook wrote: > The 2.26 release of glibc changed how siginfo_t is defined, and the earlier > work-around to using the kernel definition are no longer needed. The old > way needs to stay around for a while, though. > > Reported-by: Seth Forshee > Cc:

Re: [PATCH V2 06/13] thermal/drivers/hisi: Remove pointless lock

On Mon, Sep 04, 2017 at 09:56:05PM +0200, Daniel Lezcano wrote: > The threaded interrupt inspect the sensors structure to look in the temp > threshold field, but this field is read-only in all the code, except in the > probe function before the threaded interrupt is set. In other words there > is

[PATCH 5/9] arm64: kexec_file: create purgatory

This is a basic purgatory, or a kind of glue code between the two kernels, for arm64. Since purgatory is assumed to be relocatable (not executable) object by kexec generic code, arch_kexec_apply_relocations_add() is required in general. Arm64's purgatory, however, is a simple asm and all the

Re: [PATCH V2 06/13] thermal/drivers/hisi: Remove pointless lock

On Mon, Sep 04, 2017 at 09:56:05PM +0200, Daniel Lezcano wrote: > The threaded interrupt inspect the sensors structure to look in the temp > threshold field, but this field is read-only in all the code, except in the > probe function before the threaded interrupt is set. In other words there > is

[PATCH 5/9] arm64: kexec_file: create purgatory

This is a basic purgatory, or a kind of glue code between the two kernels, for arm64. Since purgatory is assumed to be relocatable (not executable) object by kexec generic code, arch_kexec_apply_relocations_add() is required in general. Arm64's purgatory, however, is a simple asm and all the

[PATCH 9/9] arm64: kexec_file: add Image format support

The "Image" binary will be loaded at the offset of TEXT_OFFSET from the start of system memory. TEXT_OFFSET is determined from the header of the image. Regarding kernel signature verification, it will be done through verify_pefile_signature() as arm64's "Image" binary can be seen as in PE format.

[PATCH 8/9] arm64: enable KEXEC_FILE config

Modify arm64/Kconfig and Makefile to enable kexec_file_load support. Signed-off-by: AKASHI Takahiro Cc: Catalin Marinas Cc: Will Deacon --- arch/arm64/Kconfig | 22 ++

[PATCH 9/9] arm64: kexec_file: add Image format support

The "Image" binary will be loaded at the offset of TEXT_OFFSET from the start of system memory. TEXT_OFFSET is determined from the header of the image. Regarding kernel signature verification, it will be done through verify_pefile_signature() as arm64's "Image" binary can be seen as in PE format.

[PATCH 8/9] arm64: enable KEXEC_FILE config

Modify arm64/Kconfig and Makefile to enable kexec_file_load support. Signed-off-by: AKASHI Takahiro Cc: Catalin Marinas Cc: Will Deacon --- arch/arm64/Kconfig | 22 ++ arch/arm64/kernel/Makefile | 2 +- 2 files changed, 23 insertions(+), 1 deletion(-) diff --git

[PATCH 7/9] arm64: kexec_file: set up for crash dump adding elf core header

load_crashdump_segments() creates and loads a memory segment of elf core header for crash dump. "linux,usable-memory-range" and "linux,elfcorehdr" will add to the 2nd kernel's device-tree blob. The logic of this cod is also from kexec-tools. Signed-off-by: AKASHI Takahiro

[PATCH 7/9] arm64: kexec_file: set up for crash dump adding elf core header

load_crashdump_segments() creates and loads a memory segment of elf core header for crash dump. "linux,usable-memory-range" and "linux,elfcorehdr" will add to the 2nd kernel's device-tree blob. The logic of this cod is also from kexec-tools. Signed-off-by: AKASHI Takahiro Cc: Catalin Marinas

[PATCH 3/9] kexec_file: factor out crashdump elf header function from x86

prepare_elf_headers() can also be useful for other architectures, including arm64. So let it factored out. Signed-off-by: AKASHI Takahiro Cc: Dave Young Cc: Vivek Goyal Cc: Baoquan He ---

[PATCH 4/9] asm-generic: add kexec_file_load system call to unistd.h

The initial user of this system call number is arm64. Signed-off-by: AKASHI Takahiro Acked-by: Arnd Bergmann --- include/uapi/asm-generic/unistd.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/include/uapi/asm-generic/unistd.h

[PATCH 3/9] kexec_file: factor out crashdump elf header function from x86

prepare_elf_headers() can also be useful for other architectures, including arm64. So let it factored out. Signed-off-by: AKASHI Takahiro Cc: Dave Young Cc: Vivek Goyal Cc: Baoquan He --- arch/x86/kernel/crash.c | 324 --- include/linux/kexec.h |

[PATCH 4/9] asm-generic: add kexec_file_load system call to unistd.h

The initial user of this system call number is arm64. Signed-off-by: AKASHI Takahiro Acked-by: Arnd Bergmann --- include/uapi/asm-generic/unistd.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/include/uapi/asm-generic/unistd.h b/include/uapi/asm-generic/unistd.h index

[PATCH 6/9] arm64: kexec_file: load initrd, device-tree and purgatory segments

load_other_segments() sets up and adds all the memory segments necessary other than kernel, including initrd, device-tree blob and purgatory. Most of the code was borrowed from kexec-tools' counterpart. In addition, arch_kexec_image_probe(), arch_kexec_image_load() and

[PATCH 6/9] arm64: kexec_file: load initrd, device-tree and purgatory segments

load_other_segments() sets up and adds all the memory segments necessary other than kernel, including initrd, device-tree blob and purgatory. Most of the code was borrowed from kexec-tools' counterpart. In addition, arch_kexec_image_probe(), arch_kexec_image_load() and

  1   2   3   4   5   6   7   8   9   10   >