Re: [Intel-gfx] [PATCH 3/4] lib/scatterlist: Introduce and export __sg_alloc_table_from_pages

On Wed, 2 Aug 2017 14:06:39 +0100 Tvrtko Ursulin wrote: > > Hi Andrew, > > We have a couple of small lib/scatterlist.c tidies here, plus exporting > the new API which allows drivers to control the maximum coalesced entry > as created by

Re: [Intel-gfx] [PATCH 3/4] lib/scatterlist: Introduce and export __sg_alloc_table_from_pages

On Wed, 2 Aug 2017 14:06:39 +0100 Tvrtko Ursulin wrote: > > Hi Andrew, > > We have a couple of small lib/scatterlist.c tidies here, plus exporting > the new API which allows drivers to control the maximum coalesced entry > as created by __sg_alloc_table_from_pages. > > I am looking for an

Re: [PATCH v3] KVM: nVMX: Fix attempting to emulate "Acknowledge interrupt on exit" when there is no interrupt which L1 requires to inject to L2

2017-08-03 4:26 GMT+08:00 Radim Krčmář : > 2017-08-02 03:48-0700, Wanpeng Li: >> From: Wanpeng Li >> >> [ cut here ] >> WARNING: CPU: 5 PID: 2288 at arch/x86/kvm/vmx.c:11124 >> nested_vmx_vmexit+0xd64/0xd70 [kvm_intel] >> CPU:

Re: [PATCH v3] KVM: nVMX: Fix attempting to emulate "Acknowledge interrupt on exit" when there is no interrupt which L1 requires to inject to L2

2017-08-03 4:26 GMT+08:00 Radim Krčmář : > 2017-08-02 03:48-0700, Wanpeng Li: >> From: Wanpeng Li >> >> [ cut here ] >> WARNING: CPU: 5 PID: 2288 at arch/x86/kvm/vmx.c:11124 >> nested_vmx_vmexit+0xd64/0xd70 [kvm_intel] >> CPU: 5 PID: 2288 Comm: qemu-system-x86 Not

[PATCH] loop: constify attribute_group structure

Functions working with attribute_groups provided by work with const attribute_group. These attribute_group structures do not change at runtime so mark them as const. File size before: text data bss dec hex filename 27981 5489 480 33950849e drivers/block/loop.o

[PATCH] loop: constify attribute_group structure

Functions working with attribute_groups provided by work with const attribute_group. These attribute_group structures do not change at runtime so mark them as const. File size before: text data bss dec hex filename 27981 5489 480 33950849e drivers/block/loop.o

Re: [PATCH 1/5] test_kmod: make selftest executable

On Wed, Aug 2, 2017 at 3:43 PM, Andrew Morton wrote: > On Wed, 2 Aug 2017 14:14:46 -0700 "Luis R. Rodriguez" > wrote: > >> We had just forgotten to do this. >> >> Fixes: 39258f448d71 ("kmod: add test driver to stress test the module >> loader") >>

Re: [PATCH 1/5] test_kmod: make selftest executable

On Wed, Aug 2, 2017 at 3:43 PM, Andrew Morton wrote: > On Wed, 2 Aug 2017 14:14:46 -0700 "Luis R. Rodriguez" > wrote: > >> We had just forgotten to do this. >> >> Fixes: 39258f448d71 ("kmod: add test driver to stress test the module >> loader") >> Signed-off-by: Luis R. Rodriguez >> --- >>

Re: [PATCH] zram: Fix buffer size passed to strlcpy()

Hi, On Fri, Jul 28, 2017 at 10:12 AM, Matthias Kaehlcke wrote: > comp_algorithm_store() passes the size of the source buffer to strlcpy() > instead of the destination buffer size, fix this. This was introduced in commit 415403be37e2 ("zram: use crypto api to check alg

Re: [PATCH] zram: Fix buffer size passed to strlcpy()

Hi, On Fri, Jul 28, 2017 at 10:12 AM, Matthias Kaehlcke wrote: > comp_algorithm_store() passes the size of the source buffer to strlcpy() > instead of the destination buffer size, fix this. This was introduced in commit 415403be37e2 ("zram: use crypto api to check alg availability"), but

[PATCH 2/2] arm64: Define PAGE_OFFSET using GENMASK_ULL

As is the definition causes an integer overflow, which is expected, however clang raises the following warning: arch/arm64/kernel/head.S:47:8: warning: integer overflow in preprocessor expression #elif (PAGE_OFFSET & 0x1f) != 0 ^~~

[PATCH 2/2] arm64: Define PAGE_OFFSET using GENMASK_ULL

As is the definition causes an integer overflow, which is expected, however clang raises the following warning: arch/arm64/kernel/head.S:47:8: warning: integer overflow in preprocessor expression #elif (PAGE_OFFSET & 0x1f) != 0 ^~~

[PATCH 1/2] bitops: Avoid integer overflow warning in GENMASK_ULL

GENMASK_ULL performs a left-shift of (~0ULL), which technically results in an integer overflow. clang raises a warning about this if the overflow occurs in a preprocessor expression. To avoid the overflow first perform a right-shift to clear the bits that are shifted out. Signed-off-by: Matthias

Re: [PATCH v3 7/7] ima: Support module-style appended signatures for appraisal

On Wed, 2017-08-02 at 14:42 -0300, Thiago Jung Bauermann wrote: > Mimi Zohar writes: > > > On Thu, 2017-07-06 at 19:17 -0300, Thiago Jung Bauermann wrote: > >> --- a/security/integrity/ima/ima_appraise.c > >> +++ b/security/integrity/ima/ima_appraise.c > >> @@ -200,18

[PATCH 1/2] bitops: Avoid integer overflow warning in GENMASK_ULL

GENMASK_ULL performs a left-shift of (~0ULL), which technically results in an integer overflow. clang raises a warning about this if the overflow occurs in a preprocessor expression. To avoid the overflow first perform a right-shift to clear the bits that are shifted out. Signed-off-by: Matthias

Re: [PATCH v3 7/7] ima: Support module-style appended signatures for appraisal

On Wed, 2017-08-02 at 14:42 -0300, Thiago Jung Bauermann wrote: > Mimi Zohar writes: > > > On Thu, 2017-07-06 at 19:17 -0300, Thiago Jung Bauermann wrote: > >> --- a/security/integrity/ima/ima_appraise.c > >> +++ b/security/integrity/ima/ima_appraise.c > >> @@ -200,18 +200,40 @@ int

Re: [PATCH 2/2] i2c: mux: pinctrl: drop the idle_state member

On 08/02/2017 03:25 PM, Peter Rosin wrote: On 2017-08-02 21:06, Stephen Warren wrote: On 08/02/2017 01:27 AM, Peter Rosin wrote: The information is available elsewhere. diff --git a/drivers/i2c/muxes/i2c-mux-pinctrl.c b/drivers/i2c/muxes/i2c-mux-pinctrl.c static int

Re: [PATCH 2/2] i2c: mux: pinctrl: drop the idle_state member

On 08/02/2017 03:25 PM, Peter Rosin wrote: On 2017-08-02 21:06, Stephen Warren wrote: On 08/02/2017 01:27 AM, Peter Rosin wrote: The information is available elsewhere. diff --git a/drivers/i2c/muxes/i2c-mux-pinctrl.c b/drivers/i2c/muxes/i2c-mux-pinctrl.c static int

Re: [linux-sunxi] [PATCH 01/13] dt-bindings: update the binding for Allwinner H3 DE2 support

于 2017年8月3日 GMT+08:00 上午3:06:26, "Jernej Škrabec" 写到: >Hi, > >Dne sreda, 02. avgust 2017 ob 07:02:39 CEST je icen...@aosc.io >napisal(a): >> 在 2017-08-02 12:53，Jernej Škrabec 写道： >> >> > Hi Icenowy, >> > >> > Dne torek, 01. avgust 2017 ob 15:12:52 CEST je Icenowy

Re: [linux-sunxi] [PATCH 01/13] dt-bindings: update the binding for Allwinner H3 DE2 support

于 2017年8月3日 GMT+08:00 上午3:06:26, "Jernej Škrabec" 写到: >Hi, > >Dne sreda, 02. avgust 2017 ob 07:02:39 CEST je icen...@aosc.io >napisal(a): >> 在 2017-08-02 12:53，Jernej Škrabec 写道： >> >> > Hi Icenowy, >> > >> > Dne torek, 01. avgust 2017 ob 15:12:52 CEST je Icenowy Zheng >> > >> > napisal(a):

Re: [PATCH 1/5] test_kmod: make selftest executable

On Wed, 2 Aug 2017 14:14:46 -0700 "Luis R. Rodriguez" wrote: > We had just forgotten to do this. > > Fixes: 39258f448d71 ("kmod: add test driver to stress test the module loader") > Signed-off-by: Luis R. Rodriguez > --- >

Re: [PATCH 1/5] test_kmod: make selftest executable

On Wed, 2 Aug 2017 14:14:46 -0700 "Luis R. Rodriguez" wrote: > We had just forgotten to do this. > > Fixes: 39258f448d71 ("kmod: add test driver to stress test the module loader") > Signed-off-by: Luis R. Rodriguez > --- > tools/testing/selftests/kmod/kmod.sh | 0 > 1 file changed, 0

Re: [PATCH 3/3] EDAC, ghes: Make it a proper module

On Wed, 2017-08-02 at 05:18 +0200, Borislav Petkov wrote: > On Wed, Aug 02, 2017 at 12:19:29AM +, Kani, Toshimitsu wrote: > > 1. Device-probing-logic should belong to a driver, and should > > remain private to a driver.  When we add the white-list, it should > > be added to ghes_edac. > >

Re: [PATCH 3/3] EDAC, ghes: Make it a proper module

On Wed, 2017-08-02 at 05:18 +0200, Borislav Petkov wrote: > On Wed, Aug 02, 2017 at 12:19:29AM +, Kani, Toshimitsu wrote: > > 1. Device-probing-logic should belong to a driver, and should > > remain private to a driver.  When we add the white-list, it should > > be added to ghes_edac. > >

Re: [PATCH] PCI: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:43:21PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc:

Re: [PATCH] PCI: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:43:21PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc: Thomas Petazzoni

Re: [PATCH] xen-platform: constify pci_device_id.

On 08/02/2017 01:46 PM, Arvind Yadav wrote: > pci_device_id are not supposed to change at runtime. All functions > working with pci_device_id provided by work with > const pci_device_id. So mark the non-const structs as const. > > Signed-off-by: Arvind Yadav

Re: [PATCH] xen-platform: constify pci_device_id.

On 08/02/2017 01:46 PM, Arvind Yadav wrote: > pci_device_id are not supposed to change at runtime. All functions > working with pci_device_id provided by work with > const pci_device_id. So mark the non-const structs as const. > > Signed-off-by: Arvind Yadav Reviewed-by: Boris Ostrovsky

[PATCH] selftests: futex: fix run_tests target

make -C tools/testing/selftests/futex/ run_tests doesn't run the tests. Running run_tests target only when $(OUTPUT) is the $(PWD) is incorrect. When $(OUTPUT) is empty, run_tests will not run. Fix it. Fixes: a8ba798bc8ec ("selftests: enable O and KBUILD_OUTPUT") Signed-off-by: Shuah Khan

[PATCH] selftests: futex: fix run_tests target

make -C tools/testing/selftests/futex/ run_tests doesn't run the tests. Running run_tests target only when $(OUTPUT) is the $(PWD) is incorrect. When $(OUTPUT) is empty, run_tests will not run. Fix it. Fixes: a8ba798bc8ec ("selftests: enable O and KBUILD_OUTPUT") Signed-off-by: Shuah Khan ---

[PATCH V3 2/2] It makes the code clearer and less error prone.

clearer: - less code - the code is now using the same format to create strings dynamically less error prone: - no magic number +2 +9 +5 to compute the size - no copy of the strings to compute the size and to concatenate The function `asprintf` is not POSIX standard but the program was already

[PATCH 2/4] i2c: davinci: Add PM Runtime Support

This patch adds PM runtime support to the I2C Davinci driver. Reviewed-by: Grygorii Strashko Signed-off-by: Franklin S Cooper Jr Signed-off-by: Sekhar Nori --- drivers/i2c/busses/i2c-davinci.c | 61

[PATCH 2/4] i2c: davinci: Add PM Runtime Support

This patch adds PM runtime support to the I2C Davinci driver. Reviewed-by: Grygorii Strashko Signed-off-by: Franklin S Cooper Jr Signed-off-by: Sekhar Nori --- drivers/i2c/busses/i2c-davinci.c | 61 ++-- 1 file changed, 53 insertions(+), 8 deletions(-)

[PATCH V3 2/2] It makes the code clearer and less error prone.

clearer: - less code - the code is now using the same format to create strings dynamically less error prone: - no magic number +2 +9 +5 to compute the size - no copy of the strings to compute the size and to concatenate The function `asprintf` is not POSIX standard but the program was already

[PATCH 3/4] dt-bindings: i2c: i2c-davinci: Update binding for 66AK2Gx pwr dm property

Add pm-domains property which is required for 66AK2Gx. Also document 66AK2G unique clocks property usage. Signed-off-by: Franklin S Cooper Jr --- Documentation/devicetree/bindings/i2c/i2c-davinci.txt | 12 1 file changed, 12 insertions(+) diff --git

[PATCH 3/4] dt-bindings: i2c: i2c-davinci: Update binding for 66AK2Gx pwr dm property

Add pm-domains property which is required for 66AK2Gx. Also document 66AK2G unique clocks property usage. Signed-off-by: Franklin S Cooper Jr --- Documentation/devicetree/bindings/i2c/i2c-davinci.txt | 12 1 file changed, 12 insertions(+) diff --git

[PATCH V3 1/2] use direname instead of custom code

Prefer well known functions like `dirname(3)` instead of custom implementation for the same functionality Signed-off-by: Federico Vaga --- trace-record.c | 45 ++--- 1 file changed, 30 insertions(+), 15 deletions(-) diff --git

[PATCH 4/4] ARM: dts: keystone-k2g: Add I2C nodes

From: Vitaly Andrianov Add nodes for the various I2C instances. Signed-off-by: Vitaly Andrianov [d-gerl...@ti.com: Add power domain and clock properties] Signed-off-by: Dave Gerlach [fcoo...@ti.com: Update subject and commit message]

[PATCH 1/4] i2c: davinci: Preserve return value of devm_clk_get

The i2c driver can run into driver dependency issues if its loaded before a clock driver it depends on. Therefore, EPROBE_DEFER may be returned by devm_clk_get and should be returned in probe to allow the kernel to reprobe the driver at a later time. This patch allows the error value returned by

[PATCH 4/4] ARM: dts: keystone-k2g: Add I2C nodes

From: Vitaly Andrianov Add nodes for the various I2C instances. Signed-off-by: Vitaly Andrianov [d-gerl...@ti.com: Add power domain and clock properties] Signed-off-by: Dave Gerlach [fcoo...@ti.com: Update subject and commit message] Signed-off-by: Franklin S Cooper Jr ---

[PATCH 1/4] i2c: davinci: Preserve return value of devm_clk_get

The i2c driver can run into driver dependency issues if its loaded before a clock driver it depends on. Therefore, EPROBE_DEFER may be returned by devm_clk_get and should be returned in probe to allow the kernel to reprobe the driver at a later time. This patch allows the error value returned by

[PATCH V3 1/2] use direname instead of custom code

Prefer well known functions like `dirname(3)` instead of custom implementation for the same functionality Signed-off-by: Federico Vaga --- trace-record.c | 45 ++--- 1 file changed, 30 insertions(+), 15 deletions(-) diff --git a/trace-record.c

[PATCH 0/4] ARM: dts: keystone-k2g: Add I2C support for 66AK2G

Add I2C support to 66AK2G. Primary requirement is to add PM Runtime support to the driver. This has been tested on following platforms by performing simple i2c test such as i2c detect and reading on board i2c devices: K2G GP evm OMAPL138 K2L GP EVM and boot tested on: K2E GP EVM K2HK GP EVM

[PATCH 0/4] ARM: dts: keystone-k2g: Add I2C support for 66AK2G

Add I2C support to 66AK2G. Primary requirement is to add PM Runtime support to the driver. This has been tested on following platforms by performing simple i2c test such as i2c detect and reading on board i2c devices: K2G GP evm OMAPL138 K2L GP EVM and boot tested on: K2E GP EVM K2HK GP EVM

Re: [PATCH 0/3] remove rw_page() from brd, pmem and btt

On Fri, Jul 28, 2017 at 10:31:43AM -0700, Matthew Wilcox wrote: > On Fri, Jul 28, 2017 at 10:56:01AM -0600, Ross Zwisler wrote: > > Dan Williams and Christoph Hellwig have recently expressed doubt about > > whether the rw_page() interface made sense for synchronous memory drivers > > [1][2]. It's

Re: [PATCH 0/3] remove rw_page() from brd, pmem and btt

On Fri, Jul 28, 2017 at 10:31:43AM -0700, Matthew Wilcox wrote: > On Fri, Jul 28, 2017 at 10:56:01AM -0600, Ross Zwisler wrote: > > Dan Williams and Christoph Hellwig have recently expressed doubt about > > whether the rw_page() interface made sense for synchronous memory drivers > > [1][2]. It's

Re: [RFC v1 3/6] platform/x86: intel_pmc_ipc: Use MFD framework to create dependent devices

On 08/01/2017 10:14 PM, Chakravarty, Souvik K wrote: -Original Message- From: platform-driver-x86-ow...@vger.kernel.org [mailto:platform-driver- x86-ow...@vger.kernel.org] On Behalf Of sathyanarayanan.kuppusw...@linux.intel.com Sent: Tuesday, August 1, 2017 11:44 PM To:

Re: [RFC v1 3/6] platform/x86: intel_pmc_ipc: Use MFD framework to create dependent devices

On 08/01/2017 10:14 PM, Chakravarty, Souvik K wrote: -Original Message- From: platform-driver-x86-ow...@vger.kernel.org [mailto:platform-driver- x86-ow...@vger.kernel.org] On Behalf Of sathyanarayanan.kuppusw...@linux.intel.com Sent: Tuesday, August 1, 2017 11:44 PM To:

Re: [PATCH] power: smb347-charger: Summit SMB358 charger IC

Hi Vinay, [auto build test ERROR on linus/master] [also build test ERROR on v4.13-rc3 next-20170802] [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/Vinay-Simha-BN/power-smb347-charger-Summit

Re: [PATCH] power: smb347-charger: Summit SMB358 charger IC

Hi Vinay, [auto build test ERROR on linus/master] [also build test ERROR on v4.13-rc3 next-20170802] [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/Vinay-Simha-BN/power-smb347-charger-Summit

Re: sysctl, argument parsing, possible bug

On Tue, Aug 01, 2017 at 02:54:51PM -0700, Cong Wang wrote: > On Tue, Aug 1, 2017 at 2:34 PM, Massimo Sala > wrote: > > Do you confirm it is a sysctl parsing bug ? > > > > Bosybox handles these cases, so I think also standalone sysctl have to. > > > > Or at least

Re: sysctl, argument parsing, possible bug

On Tue, Aug 01, 2017 at 02:54:51PM -0700, Cong Wang wrote: > On Tue, Aug 1, 2017 at 2:34 PM, Massimo Sala > wrote: > > Do you confirm it is a sysctl parsing bug ? > > > > Bosybox handles these cases, so I think also standalone sysctl have to. > > > > Or at least someone must update sysctl docs /

Re: [PATCH v2] PCI: dwc: designware: test PCIE_ATU_ENABLE bit to check enabled or not

On Tue, Jul 18, 2017 at 02:48:21PM +0800, Jisheng Zhang wrote: > The ATU CTRL2 register is 32 bit, besides the enable bit, other bits > may also be set. To check whether the ATU is enabled or not, we should > test the enable bit. > > Signed-off-by: Jisheng Zhang > Acked-by:

Re: [PATCH v2] PCI: dwc: designware: test PCIE_ATU_ENABLE bit to check enabled or not

On Tue, Jul 18, 2017 at 02:48:21PM +0800, Jisheng Zhang wrote: > The ATU CTRL2 register is 32 bit, besides the enable bit, other bits > may also be set. To check whether the ATU is enabled or not, we should > test the enable bit. > > Signed-off-by: Jisheng Zhang > Acked-by: Joao Pinto Applied

Re: [PATCH] PCI: dwc: designware: make dw_pcie_prog_*_atu_unroll() static

On Mon, Jul 17, 2017 at 02:13:34PM +0100, Carlos Palminha wrote: > Helper functions dw_pcie_prog_*_atu_unroll don't need to be in global scope, > so make it static. > > Cleans up sparse warnings: > - symbol 'dw_pcie_prog_outbound_atu_unroll' was not declared. Should it be > static? > - symbol

Re: [PATCH] PCI: dwc: designware: make dw_pcie_prog_*_atu_unroll() static

On Mon, Jul 17, 2017 at 02:13:34PM +0100, Carlos Palminha wrote: > Helper functions dw_pcie_prog_*_atu_unroll don't need to be in global scope, > so make it static. > > Cleans up sparse warnings: > - symbol 'dw_pcie_prog_outbound_atu_unroll' was not declared. Should it be > static? > - symbol

Re: [RFC PATCH 3/5] ima: mamespace audit status flags

On Tue, Aug 01, 2017 at 01:25:31PM -0400, Mehmet Kayaalp wrote: > >> +unsigned long iint_flags(struct integrity_iint_cache *iint, > >> + struct ns_status *status) > >> +{ > >> + if (!status) > >> + return iint->flags; > >> + > >> + return iint->flags & (status->flags &

Re: [RFC PATCH 3/5] ima: mamespace audit status flags

On Tue, Aug 01, 2017 at 01:25:31PM -0400, Mehmet Kayaalp wrote: > >> +unsigned long iint_flags(struct integrity_iint_cache *iint, > >> + struct ns_status *status) > >> +{ > >> + if (!status) > >> + return iint->flags; > >> + > >> + return iint->flags & (status->flags &

Re: [PATCH v2 2/2] Implement sysfs based cpuinfo for x86 cpus.

>>> Greg KH 08/02/17 7:47 PM >>> On Wed, Aug 02, 2017 at 07:35:16PM +0200, Felix Schnizlein wrote: >> Enable sysfs cpuinfo for x86 based cpus. Export often used cpu >> information to sysfs. Stepping, cpu flags, cpu bugs, bogomips, >> cpu family, vendor_id, model, and

Re: [PATCH v2 2/2] Implement sysfs based cpuinfo for x86 cpus.

>>> Greg KH 08/02/17 7:47 PM >>> On Wed, Aug 02, 2017 at 07:35:16PM +0200, Felix Schnizlein wrote: >> Enable sysfs cpuinfo for x86 based cpus. Export often used cpu >> information to sysfs. Stepping, cpu flags, cpu bugs, bogomips, >> cpu family, vendor_id, model, and model_name are exported. >>

Re: suspicious __GFP_NOMEMALLOC in selinux

On Wed, Aug 2, 2017 at 6:50 AM, Michal Hocko wrote: > Hi, > while doing something completely unrelated to selinux I've noticed a > really strange __GFP_NOMEMALLOC usage pattern in selinux, especially > GFP_ATOMIC | __GFP_NOMEMALLOC doesn't make much sense to me. GFP_ATOMIC > on

Re: suspicious __GFP_NOMEMALLOC in selinux

On Wed, Aug 2, 2017 at 6:50 AM, Michal Hocko wrote: > Hi, > while doing something completely unrelated to selinux I've noticed a > really strange __GFP_NOMEMALLOC usage pattern in selinux, especially > GFP_ATOMIC | __GFP_NOMEMALLOC doesn't make much sense to me. GFP_ATOMIC > on its own allows to

Re: [PATCH 2/3] PCI: qcom: Don't unroll init if init fails

On Sat, Jul 15, 2017 at 11:41:53PM -0700, Bjorn Andersson wrote: > When the init op fails it will restore the state of the resources, so we > should not disable them one more time when this happens. > > Signed-off-by: Bjorn Andersson Stanimir, any opinion on this and

Re: [PATCH 2/3] PCI: qcom: Don't unroll init if init fails

On Sat, Jul 15, 2017 at 11:41:53PM -0700, Bjorn Andersson wrote: > When the init op fails it will restore the state of the resources, so we > should not disable them one more time when this happens. > > Signed-off-by: Bjorn Andersson Stanimir, any opinion on this and the following patch? > ---

Re: strace-4.18 test suite oopses sparc64 4.12 and 4.13-rc kernels

On Tue, Aug 01, 2017 at 10:58:29PM +0200, Sam Ravnborg wrote: > Hi Mikael. > > I think this translates to the following code > from linux/uaccess.h > > first part is the inlined _copy_from_user() > > > > > (gdb) x/10i do_sys_poll+0x80-16 > >0x516ed0 : brz %o0, 0x5170fc

Re: strace-4.18 test suite oopses sparc64 4.12 and 4.13-rc kernels

On Tue, Aug 01, 2017 at 10:58:29PM +0200, Sam Ravnborg wrote: > Hi Mikael. > > I think this translates to the following code > from linux/uaccess.h > > first part is the inlined _copy_from_user() > > > > > (gdb) x/10i do_sys_poll+0x80-16 > >0x516ed0 : brz %o0, 0x5170fc > if

Re: [PATCH 0/2] PCI: dwc: convert remaining dbi read/writes to dw_pcie_readX_dbi/dw_pcie_writeX_dbi

[+cc Kishon, Pratyush] On Fri, Jul 14, 2017 at 02:07:33PM +0200, Niklas Cassel wrote: > Since the introduction of the dw_pcie_readX_dbi/dw_pcie_writeX_dbi macros, > most dw_pcie_read(pci->dbi_base, ..)/dw_pcie_write(pci->dbi_base, ..) calls > have been converted to

Re: [PATCH 0/2] PCI: dwc: convert remaining dbi read/writes to dw_pcie_readX_dbi/dw_pcie_writeX_dbi

[+cc Kishon, Pratyush] On Fri, Jul 14, 2017 at 02:07:33PM +0200, Niklas Cassel wrote: > Since the introduction of the dw_pcie_readX_dbi/dw_pcie_writeX_dbi macros, > most dw_pcie_read(pci->dbi_base, ..)/dw_pcie_write(pci->dbi_base, ..) calls > have been converted to

Re: [PATCH] selftests: ptp: include default header install path

On 07/28/2017 05:44 PM, Grygorii Strashko wrote: > Add the usr/include subdirectory of the top-level tree to the include > path to fix build when cross compiling for ARM. > testptp.c: In function 'main': > testptp.c:289:15: error: 'struct ptp_clock_caps' has no member named > 'cross_timestamping'

Re: [PATCH] selftests: ptp: include default header install path

On 07/28/2017 05:44 PM, Grygorii Strashko wrote: > Add the usr/include subdirectory of the top-level tree to the include > path to fix build when cross compiling for ARM. > testptp.c: In function 'main': > testptp.c:289:15: error: 'struct ptp_clock_caps' has no member named > 'cross_timestamping'

Re: [PATCH V5 1/2] firmware: add more flexible request_firmware_async function

On Mon, Jul 31, 2017 at 05:09:44PM +0200, Rafał Miłecki wrote: > From: Rafał Miłecki > > So far we got only one function for loading firmware asynchronously: > request_firmware_nowait. It didn't allow much customization of firmware > loading process - there is only one bool

Re: [PATCH V5 1/2] firmware: add more flexible request_firmware_async function

On Mon, Jul 31, 2017 at 05:09:44PM +0200, Rafał Miłecki wrote: > From: Rafał Miłecki > > So far we got only one function for loading firmware asynchronously: > request_firmware_nowait. It didn't allow much customization of firmware > loading process - there is only one bool uevent argument.

Re: coda's use of file->f_mapping and inode->i_mapping

On Wed, Aug 02, 2017 at 11:05:31AM -0400, Jeff Layton wrote: > The weird bit is that in coda_file_mmap, we then do this: > > coda_file->f_mapping = host_file->f_mapping; > if (coda_inode->i_mapping == _inode->i_data) > coda_inode->i_mapping = host_inode->i_mapping;

Re: [PATCH] firmware: add const to bin_attribute structures

On Wed, Aug 02, 2017 at 02:11:35PM +0530, Bhumika Goyal wrote: > Add const to bin_attribute structures as they are only passed to the > functions sysfs_{remove/create}_bin_file. The arguments passed are of > type const, so declare the structures to be const. > > Done using Coccinelle. > > @m

Re: coda's use of file->f_mapping and inode->i_mapping

On Wed, Aug 02, 2017 at 11:05:31AM -0400, Jeff Layton wrote: > The weird bit is that in coda_file_mmap, we then do this: > > coda_file->f_mapping = host_file->f_mapping; > if (coda_inode->i_mapping == _inode->i_data) > coda_inode->i_mapping = host_inode->i_mapping;

Re: [PATCH] firmware: add const to bin_attribute structures

On Wed, Aug 02, 2017 at 02:11:35PM +0530, Bhumika Goyal wrote: > Add const to bin_attribute structures as they are only passed to the > functions sysfs_{remove/create}_bin_file. The arguments passed are of > type const, so declare the structures to be const. > > Done using Coccinelle. > > @m

[PATCH] powerpc/macintosh: constify wf_sensor_ops structures

The wf_sensor_ops structures are only stored in the ops field of a wf_sensor structure, which is declared as const. Thus the wf_sensor_ops structures themselves can be const. Done with the help of Coccinelle. // @r disable optional_qualifier@ identifier i; position p; @@ static struct

[PATCH] powerpc/macintosh: constify wf_sensor_ops structures

The wf_sensor_ops structures are only stored in the ops field of a wf_sensor structure, which is declared as const. Thus the wf_sensor_ops structures themselves can be const. Done with the help of Coccinelle. // @r disable optional_qualifier@ identifier i; position p; @@ static struct

Re: [PATCH 2/2] i2c: mux: pinctrl: drop the idle_state member

On 2017-08-02 21:06, Stephen Warren wrote: > On 08/02/2017 01:27 AM, Peter Rosin wrote: >> The information is available elsewhere. > >> diff --git a/drivers/i2c/muxes/i2c-mux-pinctrl.c >> b/drivers/i2c/muxes/i2c-mux-pinctrl.c > >> static int i2c_mux_pinctrl_deselect(struct i2c_mux_core *muxc,

Re: [PATCH 2/2] i2c: mux: pinctrl: drop the idle_state member

On 2017-08-02 21:06, Stephen Warren wrote: > On 08/02/2017 01:27 AM, Peter Rosin wrote: >> The information is available elsewhere. > >> diff --git a/drivers/i2c/muxes/i2c-mux-pinctrl.c >> b/drivers/i2c/muxes/i2c-mux-pinctrl.c > >> static int i2c_mux_pinctrl_deselect(struct i2c_mux_core *muxc,

Re: [PATCH V7 1/3] PCI: limit FLR wait time to 100ms maximum

On 8/2/2017 4:27 PM, Bjorn Helgaas wrote: > On Wed, Aug 02, 2017 at 03:15:15PM -0400, Sinan Kaya wrote: > My hypothesis was that CRS isn't useful on VFs because of sec 2.2.2 > says "FLR ... does not affect its existence in PCI Configuration > Space". But I think that hypothesis is wrong because

Re: [PATCH V7 1/3] PCI: limit FLR wait time to 100ms maximum

On 8/2/2017 4:27 PM, Bjorn Helgaas wrote: > On Wed, Aug 02, 2017 at 03:15:15PM -0400, Sinan Kaya wrote: > My hypothesis was that CRS isn't useful on VFs because of sec 2.2.2 > says "FLR ... does not affect its existence in PCI Configuration > Space". But I think that hypothesis is wrong because

Re: [PATCH v2 03/22] fpga: bridge: remove OF dependency for fpga-bridge

On Sun, Jun 25, 2017 at 8:51 PM, Wu Hao wrote: > This patch removes OF dependency of fpga-bridge, it allows drivers > to use fpga-bridge class without device tree support. > > Signed-off-by: Wu Hao Acked-by: Alan Tull

Re: [PATCH v2 03/22] fpga: bridge: remove OF dependency for fpga-bridge

On Sun, Jun 25, 2017 at 8:51 PM, Wu Hao wrote: > This patch removes OF dependency of fpga-bridge, it allows drivers > to use fpga-bridge class without device tree support. > > Signed-off-by: Wu Hao Acked-by: Alan Tull

Re: Please pull ARCPGU changes

Hi Alex, On Wed, 2017-08-02 at 14:24 -0400, Alex Deucher wrote: > On Wed, Aug 2, 2017 at 6:16 AM, Alexey Brodkin > wrote: > > > > Hi Daniel, > > > > On Wed, 2017-08-02 at 11:41 +0200, Daniel Vetter wrote: > > > > > > On Mon, Jul 31, 2017 at 11:11:06AM +,

[PULL] Please pull ARCPGU changes

Hi Dave, Could you please pull a couple of minor fixes and improvements for ARCPGU. These changes are based on today's drm-next branch. The following changes since commit dd24df657075fdf1e850612ea50634816f3c3581:   Merge branch 'drm-next-4.14' of git://people.freedesktop.org/~agd5f/linux into

Re: Please pull ARCPGU changes

Hi Alex, On Wed, 2017-08-02 at 14:24 -0400, Alex Deucher wrote: > On Wed, Aug 2, 2017 at 6:16 AM, Alexey Brodkin > wrote: > > > > Hi Daniel, > > > > On Wed, 2017-08-02 at 11:41 +0200, Daniel Vetter wrote: > > > > > > On Mon, Jul 31, 2017 at 11:11:06AM +, Alexey Brodkin wrote: > > > > > >

[PULL] Please pull ARCPGU changes

Hi Dave, Could you please pull a couple of minor fixes and improvements for ARCPGU. These changes are based on today's drm-next branch. The following changes since commit dd24df657075fdf1e850612ea50634816f3c3581:   Merge branch 'drm-next-4.14' of git://people.freedesktop.org/~agd5f/linux into

Re: [PATCH 1/2] i2c: mux: pinctrl: remove platform_data

On 2017-08-02 21:05, Stephen Warren wrote: > On 08/02/2017 01:27 AM, Peter Rosin wrote: >> No platform (at least no upstreamed platform) has ever used this >> platform_data. Just drop it and simplify the code. > >> diff --git a/drivers/i2c/muxes/i2c-mux-pinctrl.c >>

Re: [PATCH 1/2] i2c: mux: pinctrl: remove platform_data

On 2017-08-02 21:05, Stephen Warren wrote: > On 08/02/2017 01:27 AM, Peter Rosin wrote: >> No platform (at least no upstreamed platform) has ever used this >> platform_data. Just drop it and simplify the code. > >> diff --git a/drivers/i2c/muxes/i2c-mux-pinctrl.c >>

[PATCH 0/2] test_kmod: pending patches for v4.14-rc1

Andrew, After the fixes for v4.13-final which I just sent these are the rest of the development patches so far queued up for v4.14 for test_kmod. Its just two minor changes. These changes are available on my linux-next kernel.org tree on the 20170801-kmod-for-v4.14 branch [0]. Please let me know

[PATCH 0/2] test_kmod: pending patches for v4.14-rc1

Andrew, After the fixes for v4.13-final which I just sent these are the rest of the development patches so far queued up for v4.14 for test_kmod. Its just two minor changes. These changes are available on my linux-next kernel.org tree on the 20170801-kmod-for-v4.14 branch [0]. Please let me know

[PATCH 1/2] test_kmod: remove paranoid UINT_MAX check on uint range processing

From: Dan Carpenter The UINT_MAX comparison is not needed because "max" is already an unsigned int, and we expect developer C code max value input to have a sensible 0 - UINT_MAX range. Note that if it so happens to be UINT_MAX + 1 it would lead to an issue, but we

[PATCH 1/2] test_kmod: remove paranoid UINT_MAX check on uint range processing

From: Dan Carpenter The UINT_MAX comparison is not needed because "max" is already an unsigned int, and we expect developer C code max value input to have a sensible 0 - UINT_MAX range. Note that if it so happens to be UINT_MAX + 1 it would lead to an issue, but we expect the developer to know

[PATCH 2/2] test_kmod: flip INT checks to be consistent

From: Dan Carpenter Most checks will check for min and then max, except the int check. Flip the checks to be consistent with the other code. Signed-off-by: Dan Carpenter [mcgrof: massaged commit log] Signed-off-by: Luis R. Rodriguez

[PATCH 2/2] test_kmod: flip INT checks to be consistent

From: Dan Carpenter Most checks will check for min and then max, except the int check. Flip the checks to be consistent with the other code. Signed-off-by: Dan Carpenter [mcgrof: massaged commit log] Signed-off-by: Luis R. Rodriguez --- lib/test_kmod.c | 2 +- 1 file changed, 1 insertion(+),

[PATCH 1/4] drivers/hwmon/pmbus: Add IBM power supply hwmon driver

From: "Edward A. James" Add the driver to monitor power supplies with hwmon over pmbus. Signed-off-by: Edward A. James --- drivers/hwmon/pmbus/Kconfig | 10 +++ drivers/hwmon/pmbus/Makefile | 1 + drivers/hwmon/pmbus/ibmps.c | 164

[PATCH 1/4] drivers/hwmon/pmbus: Add IBM power supply hwmon driver

From: "Edward A. James" Add the driver to monitor power supplies with hwmon over pmbus. Signed-off-by: Edward A. James --- drivers/hwmon/pmbus/Kconfig | 10 +++ drivers/hwmon/pmbus/Makefile | 1 + drivers/hwmon/pmbus/ibmps.c | 164 +++ 3 files

Re: [PATCH] mm: ratelimit PFNs busy info message

On Wed, 2 Aug 2017 13:44:57 -0400 Jonathan Toppins wrote: > The RDMA subsystem can generate several thousand of these messages per > second eventually leading to a kernel crash. Ratelimit these messages > to prevent this crash. Well... why are all these EBUSY's occurring?

[PATCH 3/4] Documentation: hwmon: Add IBM power supply documentation

From: "Edward A. James" Signed-off-by: Edward A. James --- Documentation/hwmon/ibmps | 53 +++ 1 file changed, 53 insertions(+) create mode 100644 Documentation/hwmon/ibmps diff --git

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