[PATCH net] net/ncsi: Don't limit vids based on hot_channel

Currently we drop any new VLAN ids if there are more than the current (or last used) channel can support. Most importantly this is a problem if no channel has been selected yet, resulting in a segfault. Secondly this does not necessarily reflect the capabilities of any other channels. Instead

[PATCH net] net/ncsi: Don't limit vids based on hot_channel

Currently we drop any new VLAN ids if there are more than the current (or last used) channel can support. Most importantly this is a problem if no channel has been selected yet, resulting in a segfault. Secondly this does not necessarily reflect the capabilities of any other channels. Instead

Re: [PATCH V1] pinctrl: qcom: spmi-gpio: Update GPIO EN_CTL when setting pin config

On Mon 09 Oct 17:17 PDT 2017, Fenglin Wu wrote: > On 10/9/2017 1:56 PM, Bjorn Andersson wrote: > > On Sun 08 Oct 22:34 PDT 2017, Fenglin Wu wrote: > > > > > On 10/6/2017 12:27 AM, Bjorn Andersson wrote: [..] > > > > But I spotted another issue while reviewing this; currently the initial > > > >

Re: [PATCH V1] pinctrl: qcom: spmi-gpio: Update GPIO EN_CTL when setting pin config

On Mon 09 Oct 17:17 PDT 2017, Fenglin Wu wrote: > On 10/9/2017 1:56 PM, Bjorn Andersson wrote: > > On Sun 08 Oct 22:34 PDT 2017, Fenglin Wu wrote: > > > > > On 10/6/2017 12:27 AM, Bjorn Andersson wrote: [..] > > > > But I spotted another issue while reviewing this; currently the initial > > > >

Re: [RFC 1/2] ARM: dts: exynos: update the usbdrd phy and ref clk

Hi Vivek, On 10 October 2017 at 11:57, Vivek Gautam wrote: > > > On 10/08/2017 06:06 PM, Anand Moon wrote: >> >> Hi Krzysztof, >> >> On 6 October 2017 at 12:08, Krzysztof Kozlowski wrote: >>> >>> On Fri, Oct 6, 2017 at 6:36 AM, Anand Moon

Re: [RFC 1/2] ARM: dts: exynos: update the usbdrd phy and ref clk

Hi Vivek, On 10 October 2017 at 11:57, Vivek Gautam wrote: > > > On 10/08/2017 06:06 PM, Anand Moon wrote: >> >> Hi Krzysztof, >> >> On 6 October 2017 at 12:08, Krzysztof Kozlowski wrote: >>> >>> On Fri, Oct 6, 2017 at 6:36 AM, Anand Moon wrote: update the usbdrd link control and phy

[PATCH 1/1] vmbus: hvsock: add proper sync for vmbus_hvsock_device_unregister()

From: Dexuan Cui Without the patch, vmbus_hvsock_device_unregister() can destroy the device prematurely when close() is called, and can cause NULl dereferencing or potential data loss (the last portion of the data stream may be dropped prematurely). Please consider this for

[PATCH 1/1] vmbus: hvsock: add proper sync for vmbus_hvsock_device_unregister()

From: Dexuan Cui Without the patch, vmbus_hvsock_device_unregister() can destroy the device prematurely when close() is called, and can cause NULl dereferencing or potential data loss (the last portion of the data stream may be dropped prematurely). Please consider this for 4.14.

[PATCH] ahci: Add support for Cavium's fifth generation SATA controller

From: Radha Mohan Chintakuntla This patch adds support for Cavium's fifth generation SATA controller. It is an on-chip controller and complies with AHCI 1.3.1. As the controller uses 64-bit addresses it cannot use the standard AHCI BAR5 and so uses BAR4. Signed-off-by:

[PATCH] ahci: Add support for Cavium's fifth generation SATA controller

From: Radha Mohan Chintakuntla This patch adds support for Cavium's fifth generation SATA controller. It is an on-chip controller and complies with AHCI 1.3.1. As the controller uses 64-bit addresses it cannot use the standard AHCI BAR5 and so uses BAR4. Signed-off-by: Radha Mohan Chintakuntla

Re: [PATCH 1/2] mm, memory_hotplug: do not fail offlining too early

Michael Ellerman writes: > Michal Hocko writes: >> On Tue 10-10-17 23:05:08, Michael Ellerman wrote: >>> Michal Hocko writes: >>> > From: Michal Hocko >>> > Memory offlining can fail just too eagerly under a heavy

Re: [PATCH 1/2] mm, memory_hotplug: do not fail offlining too early

Michael Ellerman writes: > Michal Hocko writes: >> On Tue 10-10-17 23:05:08, Michael Ellerman wrote: >>> Michal Hocko writes: >>> > From: Michal Hocko >>> > Memory offlining can fail just too eagerly under a heavy memory pressure. >>> > >>> > [ 5410.336792] page:ea22a646bd00 count:255

[PATCH v4 1/5] of/platform: Generalize /reserved-memory handling

By iterating over all /reserved-memory child nodes and match each one to a list of compatibles that we want to treat specially, we can easily extend the list of compatibles to handle - without having to resort to of_platform_populate() that would create unnecessary platform_devices. Reviewed-by:

[PATCH v4 1/5] of/platform: Generalize /reserved-memory handling

By iterating over all /reserved-memory child nodes and match each one to a list of compatibles that we want to treat specially, we can easily extend the list of compatibles to handle - without having to resort to of_platform_populate() that would create unnecessary platform_devices. Reviewed-by:

[PATCH v4 2/5] of: reserved_mem: Accessor for acquiring reserved_mem

In some cases drivers referencing a reserved-memory region might want to remap the entire region, but when defining the reserved-memory by "size" the client driver has no means to know the associated base address of the reserved memory region. This patch adds an accessor for such drivers to

[PATCH v4 2/5] of: reserved_mem: Accessor for acquiring reserved_mem

In some cases drivers referencing a reserved-memory region might want to remap the entire region, but when defining the reserved-memory by "size" the client driver has no means to know the associated base address of the reserved memory region. This patch adds an accessor for such drivers to

[PATCH v4 5/5] arm64: dts: msm8916: Mark rmtfs node as qcom,rmtfs-mem compatible

Now that we have a binding defined for the shared file system memory use this to describe the rmtfs memory region. Signed-off-by: Bjorn Andersson --- Changes since v3: - None Changes since v2: - Update compatible Changes since v1: - New patch

[PATCH v4 5/5] arm64: dts: msm8916: Mark rmtfs node as qcom,rmtfs-mem compatible

Now that we have a binding defined for the shared file system memory use this to describe the rmtfs memory region. Signed-off-by: Bjorn Andersson --- Changes since v3: - None Changes since v2: - Update compatible Changes since v1: - New patch arch/arm64/boot/dts/qcom/msm8916.dtsi | 3 +++ 1

[PATCH v4 4/5] soc: qcom: Remote filesystem memory driver

The Qualcomm remote file system protocol is used by certain remoteprocs, in particular the modem, to read and write persistent storage in platforms where only the application CPU has physical storage access. The protocol is based on a set of QMI-encoded control-messages and a shared memory buffer

[PATCH v4 0/5] Qualcomm remote filesystem shared memory driver

Some remote processors (in particular the modem) found in Qualcomm platforms stores configuration parameters and other data in a file system. As the remotes does not have direct storage access it needs to relay block accesses through a service running on the application CPU. The memory is

[PATCH v4 0/5] Qualcomm remote filesystem shared memory driver

Some remote processors (in particular the modem) found in Qualcomm platforms stores configuration parameters and other data in a file system. As the remotes does not have direct storage access it needs to relay block accesses through a service running on the application CPU. The memory is

[PATCH v4 4/5] soc: qcom: Remote filesystem memory driver

The Qualcomm remote file system protocol is used by certain remoteprocs, in particular the modem, to read and write persistent storage in platforms where only the application CPU has physical storage access. The protocol is based on a set of QMI-encoded control-messages and a shared memory buffer

[PATCH v4 3/5] dt-binding: soc: qcom: Add binding for rmtfs memory

This adds the binding for describing shared memory used to exchange file system blocks between the RMTFS client and service. A client for this is generally found in the modem firmware and is used for accessing persistent storage for things such as radio calibration. Acked-by: Rob Herring

[PATCH v4 3/5] dt-binding: soc: qcom: Add binding for rmtfs memory

This adds the binding for describing shared memory used to exchange file system blocks between the RMTFS client and service. A client for this is generally found in the modem firmware and is used for accessing persistent storage for things such as radio calibration. Acked-by: Rob Herring

[Intel-gfx] [GVT-g] [ANNOUNCE] 2017-Q3 release of XenGT (Intel GVT-g for Xen)

Hi all, We are pleased to announce an update of Intel GVT-g for Xen. Intel GVT-g is a full GPU virtualization solution with mediated pass-through, starting from 4th generation Intel Core(TM) processors with Intel processor graphics. A virtual GPU instance is maintained for each VM, with part

[Intel-gfx] [GVT-g] [ANNOUNCE] 2017-Q3 release of XenGT (Intel GVT-g for Xen)

Hi all, We are pleased to announce an update of Intel GVT-g for Xen. Intel GVT-g is a full GPU virtualization solution with mediated pass-through, starting from 4th generation Intel Core(TM) processors with Intel processor graphics. A virtual GPU instance is maintained for each VM, with part

Re: [PATCH v5 03/10] kexec_file: factor out arch_kexec_kernel_*() from x86, powerpc

On Tue, Oct 10, 2017 at 12:02:01PM +0100, Julien Thierry wrote: [snip] > >--- a/kernel/kexec_file.c > >+++ b/kernel/kexec_file.c > >@@ -26,30 +26,79 @@ > > #include > > #include "kexec_internal.h" > > > >+const __weak struct kexec_file_ops * const kexec_file_loaders[] = {NULL}; > >+ > >

Re: [PATCH v5 03/10] kexec_file: factor out arch_kexec_kernel_*() from x86, powerpc

On Tue, Oct 10, 2017 at 12:02:01PM +0100, Julien Thierry wrote: [snip] > >--- a/kernel/kexec_file.c > >+++ b/kernel/kexec_file.c > >@@ -26,30 +26,79 @@ > > #include > > #include "kexec_internal.h" > > > >+const __weak struct kexec_file_ops * const kexec_file_loaders[] = {NULL}; > >+ > >

[PATCH] VFS: Handle lazytime in do_mount()

Since commit e462ec50cb5fa ("VFS: Differentiate mount flags (MS_*) from internal superblock flags") the lazytime mount option doesn't get passed on anymore. Fix the issue by handling the option in do_mount(). Reviewed-by: Lukas Czerner Signed-off-by: Markus Trippelsdorf

[PATCH] VFS: Handle lazytime in do_mount()

Since commit e462ec50cb5fa ("VFS: Differentiate mount flags (MS_*) from internal superblock flags") the lazytime mount option doesn't get passed on anymore. Fix the issue by handling the option in do_mount(). Reviewed-by: Lukas Czerner Signed-off-by: Markus Trippelsdorf --- fs/namespace.c | 3

[Intel-gfx] [GVT-g] [ANNOUNCE] 2017-Q3 release of KVMGT (Intel GVT-g for KVM)

Hi all, We are pleased to announce an update of Intel GVT-g for KVM. Intel GVT-g for KVM (a.k.a. KVMGT) is a full GPU virtualization solution with mediated pass-through, starting from 5th generation Intel Core(TM) processors with Intel processor graphics.  A virtual GPU instance is maintained

[Intel-gfx] [GVT-g] [ANNOUNCE] 2017-Q3 release of KVMGT (Intel GVT-g for KVM)

Hi all, We are pleased to announce an update of Intel GVT-g for KVM. Intel GVT-g for KVM (a.k.a. KVMGT) is a full GPU virtualization solution with mediated pass-through, starting from 5th generation Intel Core(TM) processors with Intel processor graphics.  A virtual GPU instance is maintained

[git pull] vfs.git fixes

Fairly old DIO bug caught by Andreas (3.10+) and several slightly younger blk_rq_map_user_iov() bugs, both on map and copy codepaths (Vitaly and me). The following changes since commit 8a5776a5f49812d29fe4b2d0a2d71675c3facf3f: Linux 4.14-rc4 (2017-10-08 20:53:29 -0700) are available

[git pull] vfs.git fixes

Fairly old DIO bug caught by Andreas (3.10+) and several slightly younger blk_rq_map_user_iov() bugs, both on map and copy codepaths (Vitaly and me). The following changes since commit 8a5776a5f49812d29fe4b2d0a2d71675c3facf3f: Linux 4.14-rc4 (2017-10-08 20:53:29 -0700) are available

Re: [PATCH] powerpc/perf: Fix IMC initialization crash

On Wednesday 11 October 2017 09:41 AM, Michael Ellerman wrote: Anju T Sudhakar writes: Call trace observed with latest firmware, and upstream kernel. [ 14.499938] NIP [c00f318c] init_imc_pmu+0x8c/0xcf0 [ 14.499973] LR [c00f33f8]

Re: [PATCH] powerpc/perf: Fix IMC initialization crash

On Wednesday 11 October 2017 09:41 AM, Michael Ellerman wrote: Anju T Sudhakar writes: Call trace observed with latest firmware, and upstream kernel. [ 14.499938] NIP [c00f318c] init_imc_pmu+0x8c/0xcf0 [ 14.499973] LR [c00f33f8] init_imc_pmu+0x2f8/0xcf0 [ 14.57]

Re: BUG: KASAN: global-out-of-bounds in strscpy+0x807/0x970

On 10/10/2017 10:32 PM, Simon Brewer wrote: > Hint start looking at this thread. https://lkml.org/lkml/2017/7/18/874 > > Summary: strscpy and KASAN are currently incompatible. strscpy does a > 64 bit speculative fetch on a char pointer (for efficiency reasons). > KASAN spots this and flags an

Re: BUG: KASAN: global-out-of-bounds in strscpy+0x807/0x970

On 10/10/2017 10:32 PM, Simon Brewer wrote: > Hint start looking at this thread. https://lkml.org/lkml/2017/7/18/874 > > Summary: strscpy and KASAN are currently incompatible. strscpy does a > 64 bit speculative fetch on a char pointer (for efficiency reasons). > KASAN spots this and flags an

Re: [PATCH v15 4/7] drm/i915/gvt: Add opregion support

On Tue, Oct 10, 2017 at 05:50:04PM +0800, Tina Zhang wrote: > Windows guest driver needs vbt in opregion, to configure the setting > for display. Without opregion support, the display registers won't > be set and this blocks display model to get the correct information > of the guest display

Re: [PATCH v15 4/7] drm/i915/gvt: Add opregion support

On Tue, Oct 10, 2017 at 05:50:04PM +0800, Tina Zhang wrote: > Windows guest driver needs vbt in opregion, to configure the setting > for display. Without opregion support, the display registers won't > be set and this blocks display model to get the correct information > of the guest display

Re: [alsa-devel] [Patch v6 2/7] slimbus: Add messaging APIs to slimbus framework

On Fri, Oct 06, 2017 at 05:51:31PM +0200, srinivas.kandaga...@linaro.org wrote: > mutex_init(>m_ctrl); > + spin_lock_init(>tx.lock); > + spin_lock_init(>rx.lock); locks galore :) My assumption is that you want to optimize these? But given that audio user is going to be serialized

Re: [alsa-devel] [Patch v6 2/7] slimbus: Add messaging APIs to slimbus framework

On Fri, Oct 06, 2017 at 05:51:31PM +0200, srinivas.kandaga...@linaro.org wrote: > mutex_init(>m_ctrl); > + spin_lock_init(>tx.lock); > + spin_lock_init(>rx.lock); locks galore :) My assumption is that you want to optimize these? But given that audio user is going to be serialized

Re: [PATCH 2/3] watchdog: orion: don't enable rstout if an interrupt is configured

On 11/10/17 16:42, Guenter Roeck wrote: > On 10/10/2017 07:29 PM, Chris Packham wrote: >> The orion_wdt_irq invokes panic() so we are going to reset the CPU >> regardless. By not setting this bit we get a chance to gather debug >> from the panic output before the system is reset. >> >>

Re: [PATCH 2/3] watchdog: orion: don't enable rstout if an interrupt is configured

On 11/10/17 16:42, Guenter Roeck wrote: > On 10/10/2017 07:29 PM, Chris Packham wrote: >> The orion_wdt_irq invokes panic() so we are going to reset the CPU >> regardless. By not setting this bit we get a chance to gather debug >> from the panic output before the system is reset. >> >>

Re: [PATCH 4.4 00/47] 4.4.92-stable review

Hi Greg, On 11 October 2017 at 09:16, Tom Gall wrote: > >> On Oct 10, 2017, at 2:50 PM, Greg Kroah-Hartman >> wrote: >> >> This is the start of the stable review cycle for the 4.4.92 release. >> There are 47 patches in this series, all will be

Re: [PATCH 4.4 00/47] 4.4.92-stable review

Hi Greg, On 11 October 2017 at 09:16, Tom Gall wrote: > >> On Oct 10, 2017, at 2:50 PM, Greg Kroah-Hartman >> wrote: >> >> This is the start of the stable review cycle for the 4.4.92 release. >> There are 47 patches in this series, all will be posted as a response >> to this one. If anyone

RE: [PATCH 01/10] perf record: new interfaces to read ring buffer to file

> > /* When check_messup is true, 'end' must points to a good entry */ > > static union perf_event * perf_mmap__read(struct perf_mmap *md, bool > > check_messup, u64 start, diff --git a/tools/perf/util/evlist.h > > b/tools/perf/util/evlist.h index b1c14f1..1ce4857 100644 > > ---

RE: [PATCH 01/10] perf record: new interfaces to read ring buffer to file

> > /* When check_messup is true, 'end' must points to a good entry */ > > static union perf_event * perf_mmap__read(struct perf_mmap *md, bool > > check_messup, u64 start, diff --git a/tools/perf/util/evlist.h > > b/tools/perf/util/evlist.h index b1c14f1..1ce4857 100644 > > ---

Re: [PATCH] powerpc/perf: Fix IMC initialization crash

Anju T Sudhakar writes: > Call trace observed with latest firmware, and upstream kernel. > > [ 14.499938] NIP [c00f318c] init_imc_pmu+0x8c/0xcf0 > [ 14.499973] LR [c00f33f8] init_imc_pmu+0x2f8/0xcf0 > [ 14.57] Call Trace: > [ 14.500027]

Re: [PATCH] powerpc/perf: Fix IMC initialization crash

Anju T Sudhakar writes: > Call trace observed with latest firmware, and upstream kernel. > > [ 14.499938] NIP [c00f318c] init_imc_pmu+0x8c/0xcf0 > [ 14.499973] LR [c00f33f8] init_imc_pmu+0x2f8/0xcf0 > [ 14.57] Call Trace: > [ 14.500027] [c03fed18f710]

Re: [PATCH] printk: hash addresses printed with %p

On Wed, 2017-10-11 at 14:48 +1100, Tobin C. Harding wrote: > Currently there are many places in the kernel where addresses are being > printed using an unadorned %p. Kernel pointers should be printed using > %pK allowing some control via the kptr_restrict sysctl. Exposing addresses > gives

Re: [PATCH] mm/page-writeback.c: fix bug caused by disable periodic writeback

2017-10-10 17:33 GMT+08:00 Jan Kara : > On Tue 10-10-17 17:14:48, Yafang Shao wrote: >> 2017-10-10 16:48 GMT+08:00 Jan Kara : >> > On Tue 10-10-17 16:00:29, Yafang Shao wrote: >> >> 2017-10-10 6:42 GMT+08:00 Andrew Morton : >> >> > On Sat, 7

Re: [PATCH] mm/page-writeback.c: fix bug caused by disable periodic writeback

2017-10-10 17:33 GMT+08:00 Jan Kara : > On Tue 10-10-17 17:14:48, Yafang Shao wrote: >> 2017-10-10 16:48 GMT+08:00 Jan Kara : >> > On Tue 10-10-17 16:00:29, Yafang Shao wrote: >> >> 2017-10-10 6:42 GMT+08:00 Andrew Morton : >> >> > On Sat, 7 Oct 2017 06:58:04 +0800 Yafang Shao >> >> > wrote: >>

Re: [PATCH] printk: hash addresses printed with %p

On Wed, 2017-10-11 at 14:48 +1100, Tobin C. Harding wrote: > Currently there are many places in the kernel where addresses are being > printed using an unadorned %p. Kernel pointers should be printed using > %pK allowing some control via the kptr_restrict sysctl. Exposing addresses > gives

Re: [alsa-devel] [Patch v6 1/7] slimbus: Device management on SLIMbus

On Tue, Oct 10, 2017 at 06:21:34PM +0100, Srinivas Kandagatla wrote: > On 10/10/17 17:49, Vinod Koul wrote: > +static int slim_device_probe(struct device *dev) > +{ > + struct slim_device *sbdev; > + struct slim_driver *sbdrv; > + int status = 0; > + > +

Re: [alsa-devel] [Patch v6 1/7] slimbus: Device management on SLIMbus

On Tue, Oct 10, 2017 at 06:21:34PM +0100, Srinivas Kandagatla wrote: > On 10/10/17 17:49, Vinod Koul wrote: > +static int slim_device_probe(struct device *dev) > +{ > + struct slim_device *sbdev; > + struct slim_driver *sbdrv; > + int status = 0; > + > +

Re: [PATCH 0/4] RCU: introduce noref debug

On Mon, Oct 09, 2017 at 06:53:12PM +0200, Paolo Abeni wrote: > On Fri, 2017-10-06 at 09:34 -0700, Paul E. McKenney wrote: > > On Fri, Oct 06, 2017 at 05:10:09PM +0200, Paolo Abeni wrote: > > > Hi, > > > > > > On Fri, 2017-10-06 at 06:34 -0700, Paul E. McKenney wrote: > > > > On Fri, Oct 06, 2017

Re: [PATCH 0/4] RCU: introduce noref debug

On Mon, Oct 09, 2017 at 06:53:12PM +0200, Paolo Abeni wrote: > On Fri, 2017-10-06 at 09:34 -0700, Paul E. McKenney wrote: > > On Fri, Oct 06, 2017 at 05:10:09PM +0200, Paolo Abeni wrote: > > > Hi, > > > > > > On Fri, 2017-10-06 at 06:34 -0700, Paul E. McKenney wrote: > > > > On Fri, Oct 06, 2017

Re: [PATCH v2 1/2] kbuild: Add a cache for generated variables

Hi Douglas, 2017-10-05 7:37 GMT+09:00 Douglas Anderson : > While timing a "no-op" build of the kernel (incrementally building the > kernel even though nothing changed) in the Chrome OS build system I > found that it was much slower than I expected. > > Digging into things

Re: [PATCH v2 1/2] kbuild: Add a cache for generated variables

Hi Douglas, 2017-10-05 7:37 GMT+09:00 Douglas Anderson : > While timing a "no-op" build of the kernel (incrementally building the > kernel even though nothing changed) in the Chrome OS build system I > found that it was much slower than I expected. > > Digging into things a bit, I found that

RE: [RFC v5 4/8] platform: x86: Add generic Intel IPC driver

On October 11, 2017 3:39 AM, Kuppuswamy Sathyanarayanan wrote: > Hi, > > > On 10/08/2017 09:53 PM, Chakravarty, Souvik K wrote: > >> From: sathyanarayanan.kuppusw...@linux.intel.com > >> [mailto:sathyanarayanan.kuppusw...@linux.intel.com] > >> Sent: Sunday, October 8, 2017 3:50 AM > >> To:

RE: [RFC v5 4/8] platform: x86: Add generic Intel IPC driver

On October 11, 2017 3:39 AM, Kuppuswamy Sathyanarayanan wrote: > Hi, > > > On 10/08/2017 09:53 PM, Chakravarty, Souvik K wrote: > >> From: sathyanarayanan.kuppusw...@linux.intel.com > >> [mailto:sathyanarayanan.kuppusw...@linux.intel.com] > >> Sent: Sunday, October 8, 2017 3:50 AM > >> To:

Re: [PATCH v16 09/10] x86/arch_prctl: Selftest for ARCH_[GET|SET]_CPUID

On Tue, Oct 10, 2017 at 8:35 PM, Wanpeng Li wrote: > Hi Kyle, > 2017-03-20 16:16 GMT+08:00 Kyle Huey : >> Test disabling and reenabling the cpuid instruction via the new arch_prctl >> ARCH_SET_CPUID, retrieving the current state via ARCH_GET_CPUID, and the

Re: [PATCH v16 09/10] x86/arch_prctl: Selftest for ARCH_[GET|SET]_CPUID

On Tue, Oct 10, 2017 at 8:35 PM, Wanpeng Li wrote: > Hi Kyle, > 2017-03-20 16:16 GMT+08:00 Kyle Huey : >> Test disabling and reenabling the cpuid instruction via the new arch_prctl >> ARCH_SET_CPUID, retrieving the current state via ARCH_GET_CPUID, and the >> expected behaviors across fork() and

Re: [PATCH v2] hwmon: xgene: Support hwmon v2

On 10/10/2017 05:10 PM, Hoan Tran wrote: This patch supports xgene-hwmon v2 which uses the non-cachable memory as the PCC shared memory. Signed-off-by: Hoan Tran --- v2 - Map PCC shared mem by ioremap() in case hwmon is v2 So I assume you expect me to replace the (already

Re: [PATCH v2] hwmon: xgene: Support hwmon v2

On 10/10/2017 05:10 PM, Hoan Tran wrote: This patch supports xgene-hwmon v2 which uses the non-cachable memory as the PCC shared memory. Signed-off-by: Hoan Tran --- v2 - Map PCC shared mem by ioremap() in case hwmon is v2 So I assume you expect me to replace the (already accepted) v1 of

[PATCH] kbuild: add forward declaration of default target to Makefile.asm-generic

$(kbuild-file) and Kbuild.include are included before the default target "all". We will add a target into Kbuild.include. In advance, add a forward declaration of the default target. Signed-off-by: Masahiro Yamada --- scripts/Makefile.asm-generic | 3 +++ 1

[PATCH] kbuild: add forward declaration of default target to Makefile.asm-generic

$(kbuild-file) and Kbuild.include are included before the default target "all". We will add a target into Kbuild.include. In advance, add a forward declaration of the default target. Signed-off-by: Masahiro Yamada --- scripts/Makefile.asm-generic | 3 +++ 1 file changed, 3 insertions(+)

Re: [RFC] yamldt v0.5, now a DTS compiler too

On Tue, Oct 10, 2017 at 06:19:03PM +0300, Pantelis Antoniou wrote: > Hi David, > > > On Oct 10, 2017, at 04:50 , David Gibson > > wrote: > > > > On Mon, Oct 09, 2017 at 06:07:28PM +0300, Pantelis Antoniou wrote: > >> Hi David, > >> > >>> On Oct 9, 2017, at 03:00 ,

Re: [RFC] yamldt v0.5, now a DTS compiler too

On Tue, Oct 10, 2017 at 06:19:03PM +0300, Pantelis Antoniou wrote: > Hi David, > > > On Oct 10, 2017, at 04:50 , David Gibson > > wrote: > > > > On Mon, Oct 09, 2017 at 06:07:28PM +0300, Pantelis Antoniou wrote: > >> Hi David, > >> > >>> On Oct 9, 2017, at 03:00 , David Gibson > >>> wrote:

[PATCH] printk: hash addresses printed with %p

Currently there are many places in the kernel where addresses are being printed using an unadorned %p. Kernel pointers should be printed using %pK allowing some control via the kptr_restrict sysctl. Exposing addresses gives attackers sensitive information about the kernel layout in memory. We can

[PATCH] printk: hash addresses printed with %p

Currently there are many places in the kernel where addresses are being printed using an unadorned %p. Kernel pointers should be printed using %pK allowing some control via the kptr_restrict sysctl. Exposing addresses gives attackers sensitive information about the kernel layout in memory. We can

Re: [PATCH] f2fs/crypto: drop crypto key at evict_inode only

On 2017/10/11 1:56, Jaegeuk Kim wrote: > This patch avoids dropping crypto key in f2fs_drop_inode, so we can guarantee > it happens only at evict_inode. > > Signed-off-by: Jaegeuk Kim Reviewed-by: Chao Yu Thanks, > --- > fs/f2fs/super.c | 1 - > 1

Re: [PATCH] f2fs/crypto: drop crypto key at evict_inode only

On 2017/10/11 1:56, Jaegeuk Kim wrote: > This patch avoids dropping crypto key in f2fs_drop_inode, so we can guarantee > it happens only at evict_inode. > > Signed-off-by: Jaegeuk Kim Reviewed-by: Chao Yu Thanks, > --- > fs/f2fs/super.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git

Re: [PATCH 4.4 00/47] 4.4.92-stable review

> On Oct 10, 2017, at 2:50 PM, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 4.4.92 release. > There are 47 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being

Re: [PATCH 4.4 00/47] 4.4.92-stable review

> On Oct 10, 2017, at 2:50 PM, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 4.4.92 release. > There are 47 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. >

[PATCH] checkpatch: statement should end at a close brace at the outermost level.

Statement should end at a close brace at the outermost level in ctx_statement_block. The way to reproduce the bug, 1, Add two external function declarations into line 505 of kernel/stop_machine.c, such as, int foo1(void); int foo2(void); 2, Format a patch for that, and use the checkpatch.pl to

[PATCH] checkpatch: statement should end at a close brace at the outermost level.

Statement should end at a close brace at the outermost level in ctx_statement_block. The way to reproduce the bug, 1, Add two external function declarations into line 505 of kernel/stop_machine.c, such as, int foo1(void); int foo2(void); 2, Format a patch for that, and use the checkpatch.pl to

Re: [PATCH 2/3] watchdog: orion: don't enable rstout if an interrupt is configured

On 10/10/2017 07:29 PM, Chris Packham wrote: The orion_wdt_irq invokes panic() so we are going to reset the CPU regardless. By not setting this bit we get a chance to gather debug from the panic output before the system is reset. Signed-off-by: Chris Packham

Re: [PATCH 2/3] watchdog: orion: don't enable rstout if an interrupt is configured

On 10/10/2017 07:29 PM, Chris Packham wrote: The orion_wdt_irq invokes panic() so we are going to reset the CPU regardless. By not setting this bit we get a chance to gather debug from the panic output before the system is reset. Signed-off-by: Chris Packham Unless I am missing something,

Re: [PATCH 1/3] watchdog: orion: fix typo

On 10/10/2017 07:29 PM, Chris Packham wrote: Correct typo in comment "insterted" -> "inserted". Signed-off-by: Chris Packham Reviewed-by: Guenter Roeck --- drivers/watchdog/orion_wdt.c | 2 +- 1 file changed, 1 insertion(+), 1

Re: [PATCH 1/3] watchdog: orion: fix typo

On 10/10/2017 07:29 PM, Chris Packham wrote: Correct typo in comment "insterted" -> "inserted". Signed-off-by: Chris Packham Reviewed-by: Guenter Roeck --- drivers/watchdog/orion_wdt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/watchdog/orion_wdt.c

Re: [PATCH v16 09/10] x86/arch_prctl: Selftest for ARCH_[GET|SET]_CPUID

Hi Kyle, 2017-03-20 16:16 GMT+08:00 Kyle Huey : > Test disabling and reenabling the cpuid instruction via the new arch_prctl > ARCH_SET_CPUID, retrieving the current state via ARCH_GET_CPUID, and the > expected behaviors across fork() and exec(). > > Signed-off-by: Kyle Huey

Re: [PATCH v16 09/10] x86/arch_prctl: Selftest for ARCH_[GET|SET]_CPUID

Hi Kyle, 2017-03-20 16:16 GMT+08:00 Kyle Huey : > Test disabling and reenabling the cpuid instruction via the new arch_prctl > ARCH_SET_CPUID, retrieving the current state via ARCH_GET_CPUID, and the > expected behaviors across fork() and exec(). > > Signed-off-by: Kyle Huey > --- >

RE: [RFC v5 6/8] platform/x86: intel_punit_ipc: Use generic intel ipc device calls

> -Original Message- > From: platform-driver-x86-ow...@vger.kernel.org [mailto:platform-driver- > x86-ow...@vger.kernel.org] On Behalf Of sathyanarayanan kuppuswamy > Sent: Wednesday, October 11, 2017 3:59 AM > To: Chakravarty, Souvik K ; >

RE: [RFC v5 6/8] platform/x86: intel_punit_ipc: Use generic intel ipc device calls

> -Original Message- > From: platform-driver-x86-ow...@vger.kernel.org [mailto:platform-driver- > x86-ow...@vger.kernel.org] On Behalf Of sathyanarayanan kuppuswamy > Sent: Wednesday, October 11, 2017 3:59 AM > To: Chakravarty, Souvik K ; > a.zu...@towertech.it; x...@kernel.org;

Re: [PATCH] udf: Fix 64-bit sign extension issues affecting blocks > 0x7FFFFFFF

Jan - On 10/10/2017 02:33 AM, Jan Kara wrote: On Mon 09-10-17 10:04:52, Steve Magnani wrote: ...the patch seems to be mixing two changes into one which I'd prefer to be separate patches: 1) Changes so that physical block numbers are stored in uint32_t (and accompanying format string

Re: [PATCH] udf: Fix 64-bit sign extension issues affecting blocks > 0x7FFFFFFF

Jan - On 10/10/2017 02:33 AM, Jan Kara wrote: On Mon 09-10-17 10:04:52, Steve Magnani wrote: ...the patch seems to be mixing two changes into one which I'd prefer to be separate patches: 1) Changes so that physical block numbers are stored in uint32_t (and accompanying format string

Re: [PATCH] scripts/checkpatch.pl: fix false warning of externschecking.

On Wed, 2017-10-11 at 11:21 +0800, jiang.bi...@zte.com.cn wrote: > > On Tue, 2017-10-10 at 16:42 +0800, Jiang Biao wrote: > > > When adding a function declaration in a .c file without an extern > > > keywork decoration, checkpatch.pl will complain *externs should be > > > avoided in .c files*

Re: [PATCH] scripts/checkpatch.pl: fix false warning of externschecking.

On Wed, 2017-10-11 at 11:21 +0800, jiang.bi...@zte.com.cn wrote: > > On Tue, 2017-10-10 at 16:42 +0800, Jiang Biao wrote: > > > When adding a function declaration in a .c file without an extern > > > keywork decoration, checkpatch.pl will complain *externs should be > > > avoided in .c files*

Re: [PATCH 0/3] add %pX specifier

On Wed, 2017-10-11 at 10:32 +1100, Tobin C. Harding wrote: > On Tue, Oct 10, 2017 at 04:15:01PM -0700, Linus Torvalds wrote: > > On Tue, Oct 10, 2017 at 4:09 PM, Tobin C. Harding wrote: > > > > > > I did not understand the code (specifically why the right shift of 16 > > >

Re: [PATCH 0/3] add %pX specifier

On Wed, 2017-10-11 at 10:32 +1100, Tobin C. Harding wrote: > On Tue, Oct 10, 2017 at 04:15:01PM -0700, Linus Torvalds wrote: > > On Tue, Oct 10, 2017 at 4:09 PM, Tobin C. Harding wrote: > > > > > > I did not understand the code (specifically why the right shift of 16 > > > twice?) > > > > It's

Re: [PATCH v1 2/2] mtd: mtk-nor: add suspend/resume support

gentle ping... On Thu, 2017-09-21 at 20:45 +0800, Guochun Mao wrote: > Abstract functions of clock setting, to avoid duplicated code, > these functions been used in new feature. > Implement suspend/resume functions. > > Signed-off-by: Guochun Mao > --- >

Re: [PATCH v1 2/2] mtd: mtk-nor: add suspend/resume support

gentle ping... On Thu, 2017-09-21 at 20:45 +0800, Guochun Mao wrote: > Abstract functions of clock setting, to avoid duplicated code, > these functions been used in new feature. > Implement suspend/resume functions. > > Signed-off-by: Guochun Mao > --- > drivers/mtd/spi-nor/mtk-quadspi.c |

Re: [PATCH v1 1/2] dt-bindings: mtd: add new compatible strings and improve description

gentle ping... On Thu, 2017-09-21 at 20:45 +0800, Guochun Mao wrote: > Add "mediatak,mt2712-nor" and "mediatek,mt7622-nor" > for nor flash node's compatible strings. > Explicate the fallback compatible. > > Acked-by: Rob Herring > Signed-off-by: Guochun Mao

Re: [PATCH v1 1/2] dt-bindings: mtd: add new compatible strings and improve description

gentle ping... On Thu, 2017-09-21 at 20:45 +0800, Guochun Mao wrote: > Add "mediatak,mt2712-nor" and "mediatek,mt7622-nor" > for nor flash node's compatible strings. > Explicate the fallback compatible. > > Acked-by: Rob Herring > Signed-off-by: Guochun Mao > --- >

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

On 10/11/2017 10:26 AM, Tetsuo Handa wrote: > Wei Wang wrote: >> On 10/10/2017 09:09 PM, Tetsuo Handa wrote: >>> Wei Wang wrote: > And even if we could remove balloon_lock, you still cannot use > __GFP_DIRECT_RECLAIM at xb_set_page(). I think you will need to use > "whether it is safe

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

On 10/11/2017 10:26 AM, Tetsuo Handa wrote: > Wei Wang wrote: >> On 10/10/2017 09:09 PM, Tetsuo Handa wrote: >>> Wei Wang wrote: > And even if we could remove balloon_lock, you still cannot use > __GFP_DIRECT_RECLAIM at xb_set_page(). I think you will need to use > "whether it is safe

Re: [PATCH 0/2] Add support for ZSTD-compressed kernel

On Wed, Oct 11, 2017 at 02:01:41AM +, Nick Terrell wrote: > On 10/10/17, 5:08 PM, "Adam Borowski" wrote: > > On Tue, Oct 10, 2017 at 10:40:13PM +, Nick Terrell wrote: > > > On 10/10/17, 2:56 PM, "h...@zytor.com" wrote: > > > >On October 10, 2017

Re: [PATCH 0/2] Add support for ZSTD-compressed kernel

On Wed, Oct 11, 2017 at 02:01:41AM +, Nick Terrell wrote: > On 10/10/17, 5:08 PM, "Adam Borowski" wrote: > > On Tue, Oct 10, 2017 at 10:40:13PM +, Nick Terrell wrote: > > > On 10/10/17, 2:56 PM, "h...@zytor.com" wrote: > > > >On October 10, 2017 2:22:42 PM PDT, Nick Terrell wrote: > > >

  1   2   3   4   5   6   7   8   9   10   >