RE: [PATCH] acpi: Fix format string type mistakes

> -Original Message- > From: keesc...@google.com [mailto:keesc...@google.com] On Behalf Of Kees > Cook > Sent: Friday, December 16, 2016 3:04 PM > To: Rafael J. Wysocki > Cc: Moore, Robert ; Linux Kernel Mailing List >

RE: [PATCH] acpi: Fix format string type mistakes

> -Original Message- > From: keesc...@google.com [mailto:keesc...@google.com] On Behalf Of Kees > Cook > Sent: Friday, December 16, 2016 3:04 PM > To: Rafael J. Wysocki > Cc: Moore, Robert ; Linux Kernel Mailing List > ; Zheng, Lv ; Wysocki, > Rafael J ; Len Brown ; ACPI > Devel Maling

Re: [v3] net: ethernet: cavium: octeon: octeon_mgmt: Handle return NULL error from devm_ioremap

On 12/19/2016 08:04 AM, David Miller wrote: From: Arvind Yadav Date: Thu, 15 Dec 2016 00:33:30 +0530 Here, If devm_ioremap will fail. It will return NULL. Kernel can run into a NULL-pointer dereference. This error check will avoid NULL pointer dereference.

Re: [v3] net: ethernet: cavium: octeon: octeon_mgmt: Handle return NULL error from devm_ioremap

On 12/19/2016 08:04 AM, David Miller wrote: From: Arvind Yadav Date: Thu, 15 Dec 2016 00:33:30 +0530 Here, If devm_ioremap will fail. It will return NULL. Kernel can run into a NULL-pointer dereference. This error check will avoid NULL pointer dereference. Signed-off-by: Arvind Yadav

Re: [PATCH v3 2/5] lib: Add Sed-opal library

On Mon, Dec 19, 2016 at 12:35:46PM -0700, Scott Bauer wrote: > This patch implements the necessary logic to bring an Opal > enabled drive out of a factory-enabled into a working > Opal state. > > This patch set also enables logic to save a password to > be replayed during a resume from suspend. >

Re: [PATCH 2/3] arm64: Work around Falkor erratum 1003

Hi Catalin, On 12/08/2016 05:31 AM, Catalin Marinas wrote: > On Wed, Dec 07, 2016 at 03:00:26PM -0500, Christopher Covington wrote: >> From: Shanker Donthineni >> >> On the Qualcomm Datacenter Technologies Falkor v1 CPU, memory accesses may >> allocate TLB entries using

Re: [PATCH v3 2/5] lib: Add Sed-opal library

On Mon, Dec 19, 2016 at 12:35:46PM -0700, Scott Bauer wrote: > This patch implements the necessary logic to bring an Opal > enabled drive out of a factory-enabled into a working > Opal state. > > This patch set also enables logic to save a password to > be replayed during a resume from suspend. >

Re: [PATCH 2/3] arm64: Work around Falkor erratum 1003

Hi Catalin, On 12/08/2016 05:31 AM, Catalin Marinas wrote: > On Wed, Dec 07, 2016 at 03:00:26PM -0500, Christopher Covington wrote: >> From: Shanker Donthineni >> >> On the Qualcomm Datacenter Technologies Falkor v1 CPU, memory accesses may >> allocate TLB entries using an incorrect ASID when

Re: [PATCH 2/9] xfs: introduce and use KM_NOLOCKDEP to silence reclaim lockdep false positives

On Thu, Dec 15, 2016 at 03:07:08PM +0100, Michal Hocko wrote: > From: Michal Hocko > > Now that the page allocator offers __GFP_NOLOCKDEP let's introduce > KM_NOLOCKDEP alias for the xfs allocation APIs. While we are at it > also change KM_NOFS users introduced by b17cb364dbbb

Re: [PATCH 2/9] xfs: introduce and use KM_NOLOCKDEP to silence reclaim lockdep false positives

On Thu, Dec 15, 2016 at 03:07:08PM +0100, Michal Hocko wrote: > From: Michal Hocko > > Now that the page allocator offers __GFP_NOLOCKDEP let's introduce > KM_NOLOCKDEP alias for the xfs allocation APIs. While we are at it > also change KM_NOFS users introduced by b17cb364dbbb ("xfs: fix missing

Re: Potential issues (security and otherwise) with the current cgroup-bpf API

On Mon, Dec 19, 2016 at 12:56 PM, Alexei Starovoitov wrote: > On Sat, Dec 17, 2016 at 10:18:44AM -0800, Andy Lutomirski wrote: >> Hi all- >> >> I apologize for being rather late with this. I didn't realize that >> cgroup-bpf was going to be submitted for Linux 4.10,

Re: Potential issues (security and otherwise) with the current cgroup-bpf API

On Mon, Dec 19, 2016 at 12:56 PM, Alexei Starovoitov wrote: > On Sat, Dec 17, 2016 at 10:18:44AM -0800, Andy Lutomirski wrote: >> Hi all- >> >> I apologize for being rather late with this. I didn't realize that >> cgroup-bpf was going to be submitted for Linux 4.10, and I didn't see >> it on the

possible dmar_init_reserved_ranges() error

Hi guys, I have some questions about dmar_init_reserved_ranges(). On systems where CPU physical address space is not identity-mapped to PCI bus address space, e.g., where the PCI host bridge windows have _TRA offsets, I'm not sure we're doing the right thing. Assume we have a PCI host bridge

possible dmar_init_reserved_ranges() error

Hi guys, I have some questions about dmar_init_reserved_ranges(). On systems where CPU physical address space is not identity-mapped to PCI bus address space, e.g., where the PCI host bridge windows have _TRA offsets, I'm not sure we're doing the right thing. Assume we have a PCI host bridge

Re: [PATCH] serial: 8250: Avoid "too much work" from bogus rx timeout interrupt

Hi, On Mon, Dec 19, 2016 at 12:18 PM, Andy Shevchenko wrote: > On Mon, 2016-12-19 at 09:54 -0800, Doug Anderson wrote: >> Hi, >> >> Yes. Almost all Intel HW is using DesignWare IP for HS UARTs. >> >> OK, so possibly we could add this workaround in just the

Re: [PATCH] serial: 8250: Avoid "too much work" from bogus rx timeout interrupt

Hi, On Mon, Dec 19, 2016 at 12:18 PM, Andy Shevchenko wrote: > On Mon, 2016-12-19 at 09:54 -0800, Doug Anderson wrote: >> Hi, >> >> Yes. Almost all Intel HW is using DesignWare IP for HS UARTs. >> >> OK, so possibly we could add this workaround in just the DesignWare >> code and then we could be

Re: DAX mapping detection (was: Re: [PATCH] Fix region lost in /proc/self/smaps)

On Fri, Sep 16, 2016 at 03:54:05PM +1000, Nicholas Piggin wrote: <> > Definitely the first step would be your simple preallocated per > inode approach until it is shown to be insufficient. Reviving this thread a few months later... Dave, we're interested in taking a serious look at what it would

Re: DAX mapping detection (was: Re: [PATCH] Fix region lost in /proc/self/smaps)

On Fri, Sep 16, 2016 at 03:54:05PM +1000, Nicholas Piggin wrote: <> > Definitely the first step would be your simple preallocated per > inode approach until it is shown to be insufficient. Reviving this thread a few months later... Dave, we're interested in taking a serious look at what it would

Re: [PATCH 2/3] iio: core: Add double tap as possible gesture

On 06/12/16 11:25, Peter Meerwald-Stadler wrote: > >> This adds the IIO_MOD_DOUBLE_TAP entry to the iio_modifier enum and the >> corresponding "double_tap" string to the iio_modifier_names array. > > I don't think we should have gestures as channel modifiers Agreed, though treating it like other

Re: [PATCH 2/3] iio: core: Add double tap as possible gesture

On 06/12/16 11:25, Peter Meerwald-Stadler wrote: > >> This adds the IIO_MOD_DOUBLE_TAP entry to the iio_modifier enum and the >> corresponding "double_tap" string to the iio_modifier_names array. > > I don't think we should have gestures as channel modifiers Agreed, though treating it like other

Re: [PATCHSET v4] blk-mq-scheduling framework

On 12/19/2016 11:21 AM, Paolo Valente wrote: > >> Il giorno 19 dic 2016, alle ore 16:20, Jens Axboe ha scritto: >> >> On 12/19/2016 04:32 AM, Paolo Valente wrote: >>> Il giorno 17 dic 2016, alle ore 01:12, Jens Axboe ha scritto: This is version 4

Re: [PATCHSET v4] blk-mq-scheduling framework

On 12/19/2016 11:21 AM, Paolo Valente wrote: > >> Il giorno 19 dic 2016, alle ore 16:20, Jens Axboe ha scritto: >> >> On 12/19/2016 04:32 AM, Paolo Valente wrote: >>> Il giorno 17 dic 2016, alle ore 01:12, Jens Axboe ha scritto: This is version 4 of this patchset, version 3

Re: HalfSipHash Acceptable Usage

Hi JP, On Mon, Dec 19, 2016 at 9:49 PM, Jean-Philippe Aumasson wrote: > > On Mon, Dec 19, 2016 at 6:32 PM Jason A. Donenfeld wrote: >> >> Hi JP, >> >> With the threads getting confusing, I've been urged to try and keep >> the topics and threads

Re: HalfSipHash Acceptable Usage

Hi JP, On Mon, Dec 19, 2016 at 9:49 PM, Jean-Philippe Aumasson wrote: > > On Mon, Dec 19, 2016 at 6:32 PM Jason A. Donenfeld wrote: >> >> Hi JP, >> >> With the threads getting confusing, I've been urged to try and keep >> the topics and threads more closely constrained. Here's where we're >>

[PATCH net v4 4/4] fsl/fman: enable compilation on ARM64

Signed-off-by: Madalin Bucur --- drivers/net/ethernet/freescale/fman/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/freescale/fman/Kconfig b/drivers/net/ethernet/freescale/fman/Kconfig index 79b7c84..dc0850b 100644 ---

[PATCH net v4 4/4] fsl/fman: enable compilation on ARM64

Signed-off-by: Madalin Bucur --- drivers/net/ethernet/freescale/fman/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/freescale/fman/Kconfig b/drivers/net/ethernet/freescale/fman/Kconfig index 79b7c84..dc0850b 100644 ---

Re: Potential issues (security and otherwise) with the current cgroup-bpf API

On Sat, Dec 17, 2016 at 10:18:44AM -0800, Andy Lutomirski wrote: > Hi all- > > I apologize for being rather late with this. I didn't realize that > cgroup-bpf was going to be submitted for Linux 4.10, and I didn't see > it on the linux-api list, so I missed the discussion. > > I think that the

Re: Potential issues (security and otherwise) with the current cgroup-bpf API

On Sat, Dec 17, 2016 at 10:18:44AM -0800, Andy Lutomirski wrote: > Hi all- > > I apologize for being rather late with this. I didn't realize that > cgroup-bpf was going to be submitted for Linux 4.10, and I didn't see > it on the linux-api list, so I missed the discussion. > > I think that the

Re: [PATCH v2 3/5] KVM: VMX: Move skip_emulated_instruction out of nested_vmx_check_vmcs12

On Tue, Nov 29, 2016 at 12:40 PM, Kyle Huey wrote: > We can't return both the pass/fail boolean for the vmcs and the upcoming > continue/exit-to-userspace boolean for skip_emulated_instruction out of > nested_vmx_check_vmcs, so move skip_emulated_instruction out of it instead.

Re: [PATCH v2 3/5] KVM: VMX: Move skip_emulated_instruction out of nested_vmx_check_vmcs12

On Tue, Nov 29, 2016 at 12:40 PM, Kyle Huey wrote: > We can't return both the pass/fail boolean for the vmcs and the upcoming > continue/exit-to-userspace boolean for skip_emulated_instruction out of > nested_vmx_check_vmcs, so move skip_emulated_instruction out of it instead. > > Additionally,

[PATCH 1/2] PM / core: Clean up kerneldoc comments in pm.h

From: Rafael J. Wysocki Refresh the struct dev_pm_ops kerneldoc comment, so that it looks better and is more readable after processing by Sphinx, and drop the kerneldoc marker from the "PM_EVENT_ messages" comment which is not a proper kerneldoc and causes Sphinx to

[PATCH 1/2] PM / core: Clean up kerneldoc comments in pm.h

From: Rafael J. Wysocki Refresh the struct dev_pm_ops kerneldoc comment, so that it looks better and is more readable after processing by Sphinx, and drop the kerneldoc marker from the "PM_EVENT_ messages" comment which is not a proper kerneldoc and causes Sphinx to generate confusing mess.

[PATCH 0/2] PM / docs: linux/pm.h kerneldocs update and power/devices.txt conversion

Hi Everyone, These two patches update kerneldoc comments in include/linux/pm.h ([1/2]) and convert Documentation/power/devices.txt to reST ([2/2], RFC). Please have a look, especially at patch [2/2], and let me know what can be done in a better way. Thanks, Rafael

[PATCH 0/2] PM / docs: linux/pm.h kerneldocs update and power/devices.txt conversion

Hi Everyone, These two patches update kerneldoc comments in include/linux/pm.h ([1/2]) and convert Documentation/power/devices.txt to reST ([2/2], RFC). Please have a look, especially at patch [2/2], and let me know what can be done in a better way. Thanks, Rafael

[RFC][PATCH 2/2] PM / core / docs: Convert sleep states API document to reST

From: Rafael J. Wysocki Move the document describing the system sleep states transition API for devices to Documentation/driver-api/pm/, convert it to reST and update it to use current terminology. Also remove the remaining reference to the old version from pm.h.

[RFC][PATCH 2/2] PM / core / docs: Convert sleep states API document to reST

From: Rafael J. Wysocki Move the document describing the system sleep states transition API for devices to Documentation/driver-api/pm/, convert it to reST and update it to use current terminology. Also remove the remaining reference to the old version from pm.h. The new document still

[PATCH 1/1] kernel: futex: fixed to else and initcall

The include/linux/init.h file have to content; to not used __initcall functions. I think, needs to be replaced to device_initcall. device_initcall() or more appropriate function instead of __initcall. else doesn't need to be used, if should be enclosed in parentheses. Also, I used checkpatch

[PATCH 1/1] kernel: futex: fixed to else and initcall

The include/linux/init.h file have to content; to not used __initcall functions. I think, needs to be replaced to device_initcall. device_initcall() or more appropriate function instead of __initcall. else doesn't need to be used, if should be enclosed in parentheses. Also, I used checkpatch

Re: [PATCH v3 2/2] iio: adc: hx711: Add IIO driver for AVIA HX711

On 14/12/16 16:17, Andreas Klinger wrote: > This is the IIO driver for AVIA HX711 ADC which ist mostly used in weighting > cells. > > The protocol is quite simple and using GPIOs: > One GPIO is used as clock (SCK) while another GPIO is read (DOUT) Youch. Controlling the next conversion via the

Re: [PATCH v3 2/2] iio: adc: hx711: Add IIO driver for AVIA HX711

On 14/12/16 16:17, Andreas Klinger wrote: > This is the IIO driver for AVIA HX711 ADC which ist mostly used in weighting > cells. > > The protocol is quite simple and using GPIOs: > One GPIO is used as clock (SCK) while another GPIO is read (DOUT) Youch. Controlling the next conversion via the

Re: [PATCH 5/5] firmware: add DECLARE_FW_CUSTOM_FALLBACK() annotation

On 12/19/2016 09:08 PM, Pavel Machek wrote: > Hi! > >> On 12/17/2016 01:14 AM, Luis R. Rodriguez wrote: >>> Milo if sysfs is used can't the old userspace be mapped to use the new >>> sysfs interface through a wrapper of some sort ? What exactly would be >>> needed to ensure old userspace will not

Re: [PATCH 5/5] firmware: add DECLARE_FW_CUSTOM_FALLBACK() annotation

On 12/19/2016 09:08 PM, Pavel Machek wrote: > Hi! > >> On 12/17/2016 01:14 AM, Luis R. Rodriguez wrote: >>> Milo if sysfs is used can't the old userspace be mapped to use the new >>> sysfs interface through a wrapper of some sort ? What exactly would be >>> needed to ensure old userspace will not

Re: [PATCH v3] usb: musb: debugfs: allow forcing host mode together with speed in testmode

On Mon, Dec 19, 2016 at 04:23:47PM +0100, Pali Rohár wrote: > Based on the musb ug, force_host bit is allowed to be set along with > force_hs or force_fs bit. > > It could help to implement forced host mode via testmode on Nokia N900. > > Signed-off-by: Pali Rohár

Re: [PATCH v3] usb: musb: debugfs: allow forcing host mode together with speed in testmode

On Mon, Dec 19, 2016 at 04:23:47PM +0100, Pali Rohár wrote: > Based on the musb ug, force_host bit is allowed to be set along with > force_hs or force_fs bit. > > It could help to implement forced host mode via testmode on Nokia N900. > > Signed-off-by: Pali Rohár Applied. Thanks. -Bin. > ---

[PATCH net v4 0/4] fsl/fman: fixes for ARM

The patch set fixes advertised speeds for QSGMII interfaces, disables A007273 erratum workaround on non-PowerPC platforms where it does not apply, enables compilation on ARM64 and addresses a probing issue on non PPC platforms. Changes from v3: removed redundant comment, added ack by Scott

[PATCH net v4 0/4] fsl/fman: fixes for ARM

The patch set fixes advertised speeds for QSGMII interfaces, disables A007273 erratum workaround on non-PowerPC platforms where it does not apply, enables compilation on ARM64 and addresses a probing issue on non PPC platforms. Changes from v3: removed redundant comment, added ack by Scott

[PATCH net v4 2/4] powerpc: fsl/fman: remove fsl,fman from of_device_ids[]

The fsl/fman drivers will use of_platform_populate() on all supported platforms. Call of_platform_populate() to probe the FMan sub-nodes. Signed-off-by: Igal Liberman Signed-off-by: Madalin Bucur Acked-by: Scott Wood ---

[PATCH net v4 2/4] powerpc: fsl/fman: remove fsl,fman from of_device_ids[]

The fsl/fman drivers will use of_platform_populate() on all supported platforms. Call of_platform_populate() to probe the FMan sub-nodes. Signed-off-by: Igal Liberman Signed-off-by: Madalin Bucur Acked-by: Scott Wood --- arch/powerpc/platforms/85xx/corenet_generic.c | 3 ---

[PATCH net v4 1/4] fsl/fman: fix 1G support for QSGMII interfaces

QSGMII ports were not advertising 1G speed. Signed-off-by: Madalin Bucur Reviewed-by: Camelia Groza --- drivers/net/ethernet/freescale/fman/mac.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/ethernet/freescale/fman/mac.c

[PATCH net v4 1/4] fsl/fman: fix 1G support for QSGMII interfaces

QSGMII ports were not advertising 1G speed. Signed-off-by: Madalin Bucur Reviewed-by: Camelia Groza --- drivers/net/ethernet/freescale/fman/mac.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/ethernet/freescale/fman/mac.c b/drivers/net/ethernet/freescale/fman/mac.c index

[PATCH net v4 3/4] fsl/fman: A007273 only applies to PPC SoCs

Signed-off-by: Madalin Bucur Reviewed-by: Camelia Groza --- drivers/net/ethernet/freescale/fman/fman.c | 8 1 file changed, 8 insertions(+) diff --git a/drivers/net/ethernet/freescale/fman/fman.c

[PATCH net v4 3/4] fsl/fman: A007273 only applies to PPC SoCs

Signed-off-by: Madalin Bucur Reviewed-by: Camelia Groza --- drivers/net/ethernet/freescale/fman/fman.c | 8 1 file changed, 8 insertions(+) diff --git a/drivers/net/ethernet/freescale/fman/fman.c b/drivers/net/ethernet/freescale/fman/fman.c index 4b83263..f60845f 100644 ---

[PATCH] iommu/arm-smmu-v3: prevent corruption of ste stage-1 context ptr

To ensure that the stage-1 context ptr for an ste points to the intended context descriptor, this patch adds code to clear away the stale context ptr value prior to or'ing in the new one. Signed-off-by: Nate Watterson --- drivers/iommu/arm-smmu-v3.c | 2 ++ 1 file

[PATCH] iommu/arm-smmu-v3: prevent corruption of ste stage-1 context ptr

To ensure that the stage-1 context ptr for an ste points to the intended context descriptor, this patch adds code to clear away the stale context ptr value prior to or'ing in the new one. Signed-off-by: Nate Watterson --- drivers/iommu/arm-smmu-v3.c | 2 ++ 1 file changed, 2 insertions(+) diff

[PATCH] PM / docs: Drop confusing kernel-doc references from infrastructure.rst

From: Rafael J. Wysocki The references to drivers/base/power/main.c and drivers/acpi/scan.c from Documentation/driver-api/infrastructure.rst are confusing. They both cause descriptions of functions that are not relevant to device drivers at all to be generated and

[PATCH] PM / docs: Drop confusing kernel-doc references from infrastructure.rst

From: Rafael J. Wysocki The references to drivers/base/power/main.c and drivers/acpi/scan.c from Documentation/driver-api/infrastructure.rst are confusing. They both cause descriptions of functions that are not relevant to device drivers at all to be generated and none of them is sufficient to

[PATCH] iommu/arm-smmu-v3: avoid over allocating for l2 stream tables

Currently, all l2 stream tables are being allocated with space for (1<

[PATCH] iommu/arm-smmu-v3: avoid over allocating for l2 stream tables

Currently, all l2 stream tables are being allocated with space for (1< --- drivers/iommu/arm-smmu-v3.c | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/drivers/iommu/arm-smmu-v3.c b/drivers/iommu/arm-smmu-v3.c index 4d6ec44..5dca671 100644 ---

Re: RFC: capabilities(7): notes for kernel developers

On Friday, December 16, 2016 01:16:15 PM John Stultz wrote: > On Fri, Dec 16, 2016 at 1:05 PM, Serge E. Hallyn wrote: > > Quoting John Stultz (john.stu...@linaro.org): > >> On Fri, Dec 16, 2016 at 12:10 PM, Serge E. Hallyn wrote: > >> > Quoting Michael Kerrisk

Re: RFC: capabilities(7): notes for kernel developers

On Friday, December 16, 2016 01:16:15 PM John Stultz wrote: > On Fri, Dec 16, 2016 at 1:05 PM, Serge E. Hallyn wrote: > > Quoting John Stultz (john.stu...@linaro.org): > >> On Fri, Dec 16, 2016 at 12:10 PM, Serge E. Hallyn wrote: > >> > Quoting Michael Kerrisk (man-pages)

Re: [PATCH] serial: 8250: Avoid "too much work" from bogus rx timeout interrupt

On Mon, 2016-12-19 at 09:54 -0800, Doug Anderson wrote: > Hi, > > Yes. Almost all Intel HW is using DesignWare IP for HS UARTs. > > OK, so possibly we could add this workaround in just the DesignWare > code and then we could be more sure we're not breaking other UARTs? > That would work for me.  

Re: [PATCH] serial: 8250: Avoid "too much work" from bogus rx timeout interrupt

On Mon, 2016-12-19 at 09:54 -0800, Doug Anderson wrote: > Hi, > > Yes. Almost all Intel HW is using DesignWare IP for HS UARTs. > > OK, so possibly we could add this workaround in just the DesignWare > code and then we could be more sure we're not breaking other UARTs? > That would work for me.  

[PATCH 1/2] cpufreq: brcmstb-avs-cpufreq: extend sysfs entry brcm_avs_pmap

From: Markus Mayer We extend the brcm_avs_pmap sysfs entry (which issues the GET_PMAP command to AVS) to include all fields from struct pmap. This means adding mode (AVS, DVS, DVFS) and state (the P-state) to the output. Signed-off-by: Markus Mayer ---

[PATCH 1/2] cpufreq: brcmstb-avs-cpufreq: extend sysfs entry brcm_avs_pmap

From: Markus Mayer We extend the brcm_avs_pmap sysfs entry (which issues the GET_PMAP command to AVS) to include all fields from struct pmap. This means adding mode (AVS, DVS, DVFS) and state (the P-state) to the output. Signed-off-by: Markus Mayer --- drivers/cpufreq/brcmstb-avs-cpufreq.c |

[PATCH 0/2] cpufreq: brcmstb-avs-cpufreq: properly retrieve P-state upon suspend

From: Markus Mayer This fix is for 4.10. The driver needs to save the proper P-state on suspend, so it'll resume at the same speed. We also add the P-state and the mode as returned by the AVS firmware GET_PMAP command to the existing brcm_avs_pmap sysfs entry. This will

[PATCH 2/2] cpufreq: brcmstb-avs-cpufreq: properly retrieve P-state upon suspend

From: Markus Mayer The AVS GET_PMAP command does return a P-state along with the P-map information. However, that P-state is the initial P-state when the P-map was first downloaded to AVS. It is *not* the current P-state. Therefore, we explicitly retrieve the P-state using

[PATCH 0/2] cpufreq: brcmstb-avs-cpufreq: properly retrieve P-state upon suspend

From: Markus Mayer This fix is for 4.10. The driver needs to save the proper P-state on suspend, so it'll resume at the same speed. We also add the P-state and the mode as returned by the AVS firmware GET_PMAP command to the existing brcm_avs_pmap sysfs entry. This will make it easier to

[PATCH 2/2] cpufreq: brcmstb-avs-cpufreq: properly retrieve P-state upon suspend

From: Markus Mayer The AVS GET_PMAP command does return a P-state along with the P-map information. However, that P-state is the initial P-state when the P-map was first downloaded to AVS. It is *not* the current P-state. Therefore, we explicitly retrieve the P-state using the GET_PSTATE

Re: [PATCH 5/5] firmware: add DECLARE_FW_CUSTOM_FALLBACK() annotation

Hi! > On 12/17/2016 01:14 AM, Luis R. Rodriguez wrote: > >Milo if sysfs is used can't the old userspace be mapped to use the new > >sysfs interface through a wrapper of some sort ? What exactly would be > >needed to ensure old userspace will not break? > > LP5521 and LP5523 have two ways to load

Re: [PATCH 5/5] firmware: add DECLARE_FW_CUSTOM_FALLBACK() annotation

Hi! > On 12/17/2016 01:14 AM, Luis R. Rodriguez wrote: > >Milo if sysfs is used can't the old userspace be mapped to use the new > >sysfs interface through a wrapper of some sort ? What exactly would be > >needed to ensure old userspace will not break? > > LP5521 and LP5523 have two ways to load

Re: [PATCH] PM / Hibernate: use rb_entry instead of container_of

On Mon 2016-12-19 23:03:11, Geliang Tang wrote: > To make the code clearer, use rb_entry() instead of container_of() to > deal with rbtree. > > Signed-off-by: Geliang Tang Acked-by: Pavel Machek -- (english) http://www.livejournal.com/~pavelmachek (cesky,

Re: [PATCH] PM / Hibernate: use rb_entry instead of container_of

On Mon 2016-12-19 23:03:11, Geliang Tang wrote: > To make the code clearer, use rb_entry() instead of container_of() to > deal with rbtree. > > Signed-off-by: Geliang Tang Acked-by: Pavel Machek -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures)

Re: [PATCH 2/2] regulator: rn5t618: add RC5T619 PMIC support

Hi all, I believe this hasn't been merged. Is there anything preventing the merge of this patch? Thanks, 2016-11-09 15:02 GMT+01:00 Mark Brown : > On Sat, Nov 05, 2016 at 05:19:25PM +0100, Pierre-Hugues Husson wrote: >> Extend the driver to support Ricoh RC5T619. >> Support

Re: [PATCH 2/2] regulator: rn5t618: add RC5T619 PMIC support

Hi all, I believe this hasn't been merged. Is there anything preventing the merge of this patch? Thanks, 2016-11-09 15:02 GMT+01:00 Mark Brown : > On Sat, Nov 05, 2016 at 05:19:25PM +0100, Pierre-Hugues Husson wrote: >> Extend the driver to support Ricoh RC5T619. >> Support the additional

Re: [PATCH] solo6x10: use designated initializers

On Fri, Dec 16, 2016 at 05:05:36PM -0800, Kees Cook wrote: > Prepare to mark sensitive kernel structures for randomization by making > sure they're using designated initializers. These were identified during > allyesconfig builds of x86, arm, and arm64, with most initializer fixes > extracted from

Re: [PATCH] solo6x10: use designated initializers

On Fri, Dec 16, 2016 at 05:05:36PM -0800, Kees Cook wrote: > Prepare to mark sensitive kernel structures for randomization by making > sure they're using designated initializers. These were identified during > allyesconfig builds of x86, arm, and arm64, with most initializer fixes > extracted from

Re: [PATCH] kernel/watchdog: Prevent false hardlockup on overloaded system

On Tue, 6 Dec 2016 11:17:13 -0500 Don Zickus wrote: > On an overloaded system, it is possible that a change in the watchdog > threshold > can be delayed long enough to trigger a false positive. > > This can easily be achieved by having a cpu spinning indefinitely on a

Re: [PATCH] kernel/watchdog: Prevent false hardlockup on overloaded system

On Tue, 6 Dec 2016 11:17:13 -0500 Don Zickus wrote: > On an overloaded system, it is possible that a change in the watchdog > threshold > can be delayed long enough to trigger a false positive. > > This can easily be achieved by having a cpu spinning indefinitely on a task, > while another

[PATCH v3 1/5] include: Add definitions for sed

This patch adds the definitions and structures for the SED Opal code. Signed-off-by: Scott Bauer Signed-off-by: Rafael Antognolli --- include/linux/sed-opal.h | 38 + include/linux/sed.h | 76

[PATCH v3 1/5] include: Add definitions for sed

This patch adds the definitions and structures for the SED Opal code. Signed-off-by: Scott Bauer Signed-off-by: Rafael Antognolli --- include/linux/sed-opal.h | 38 + include/linux/sed.h | 76 ++ include/uapi/linux/sed-opal.h | 94

Re: [PATCH 2/7] PM / devfreq: exynos-ppmu: Use the regmap interface to handle the registers

Hello, I was just wondering what is improved by moving to regmap. For me this looks like it only complicates the code. Lots of regmap_{read,write}() and for each one of these we need to check the return code. Also when exactly did __raw_writel() and friends become legacy? With best wishes,

Re: [PATCH 2/7] PM / devfreq: exynos-ppmu: Use the regmap interface to handle the registers

Hello, I was just wondering what is improved by moving to regmap. For me this looks like it only complicates the code. Lots of regmap_{read,write}() and for each one of these we need to check the return code. Also when exactly did __raw_writel() and friends become legacy? With best wishes,

Re: [upstream-release] [PATCH net v3 2/4] powerpc: fsl/fman: remove fsl, fman from of_device_ids[]

On Mon, 2016-12-19 at 18:13 +0200, Madalin Bucur wrote: > The fsl/fman drivers will use of_platform_populate() on all > supported platforms. Call of_platform_populate() to probe the > FMan sub-nodes. > > Signed-off-by: Igal Liberman > Signed-off-by: Madalin Bucur

Re: [upstream-release] [PATCH net v3 2/4] powerpc: fsl/fman: remove fsl, fman from of_device_ids[]

On Mon, 2016-12-19 at 18:13 +0200, Madalin Bucur wrote: > The fsl/fman drivers will use of_platform_populate() on all > supported platforms. Call of_platform_populate() to probe the > FMan sub-nodes. > > Signed-off-by: Igal Liberman > Signed-off-by: Madalin Bucur > --- >  

[PATCH v3 2/5] lib: Add Sed-opal library

This patch implements the necessary logic to bring an Opal enabled drive out of a factory-enabled into a working Opal state. This patch set also enables logic to save a password to be replayed during a resume from suspend. Signed-off-by: Scott Bauer Signed-off-by: Rafael

[PATCH v3 2/5] lib: Add Sed-opal library

This patch implements the necessary logic to bring an Opal enabled drive out of a factory-enabled into a working Opal state. This patch set also enables logic to save a password to be replayed during a resume from suspend. Signed-off-by: Scott Bauer Signed-off-by: Rafael Antognolli ---

[PATCH v3 3/5] fs: Wire up SED/Opal to ioctl

Adds a new sed_context pointer to file struct, for char devs who wish to suppor SED. Adds ioctl handling code. Signed-off-by: Scott Bauer Signed-off-by: Rafael Antognolli --- fs/ioctl.c | 3 +++ include/linux/fs.h | 2 ++ 2 files

[PATCH v3 3/5] fs: Wire up SED/Opal to ioctl

Adds a new sed_context pointer to file struct, for char devs who wish to suppor SED. Adds ioctl handling code. Signed-off-by: Scott Bauer Signed-off-by: Rafael Antognolli --- fs/ioctl.c | 3 +++ include/linux/fs.h | 2 ++ 2 files changed, 5 insertions(+) diff --git a/fs/ioctl.c

[PATCH v3 4/5] nvme: Implement resume_from_suspend and SED Allocation code.

This patch implements the necessary logic to unlock a SED enabled device coming back from an S3. The patch also implements the necessary logic to allocate the appropriate opal_dev structures to support the OPAL protocol. Signed-off-by: Scott Bauer Signed-off-by: Rafael

[PATCH v3 4/5] nvme: Implement resume_from_suspend and SED Allocation code.

This patch implements the necessary logic to unlock a SED enabled device coming back from an S3. The patch also implements the necessary logic to allocate the appropriate opal_dev structures to support the OPAL protocol. Signed-off-by: Scott Bauer Signed-off-by: Rafael Antognolli ---

[PATCH v3 5/5] Maintainers: Add Information for SED Opal library

Signed-off-by: Scott Bauer Signed-off-by: Rafael Antognolli --- MAINTAINERS | 10 ++ 1 file changed, 10 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index f6eb97b..76d542c 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -11051,6

[PATCH v3 0/5] SED OPAL Library

Changes from v2->v3: 1) Removed the necessity of passing around block devices into the opal code. We now pass around a sed_context structure which contains a previously allocated opal_dev structure, sec_ops fn pointers, and opaque data for the send/recv functions to use. 2) Removed the

[PATCH v3 5/5] Maintainers: Add Information for SED Opal library

Signed-off-by: Scott Bauer Signed-off-by: Rafael Antognolli --- MAINTAINERS | 10 ++ 1 file changed, 10 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index f6eb97b..76d542c 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -11051,6 +11051,16 @@ L: linux-...@vger.kernel.org S:

[PATCH v3 0/5] SED OPAL Library

Changes from v2->v3: 1) Removed the necessity of passing around block devices into the opal code. We now pass around a sed_context structure which contains a previously allocated opal_dev structure, sec_ops fn pointers, and opaque data for the send/recv functions to use. 2) Removed the

Re: [PATCH] ASoC: wm_adsp: Don't overrun firmware file buffer when reading region data

Hi Richard, [auto build test WARNING on asoc/for-next] [also build test WARNING on v4.9 next-20161219] [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/Richard-Fitzgerald/ASoC-wm_adsp-Don-t

Re: [PATCH] ASoC: wm_adsp: Don't overrun firmware file buffer when reading region data

Hi Richard, [auto build test WARNING on asoc/for-next] [also build test WARNING on v4.9 next-20161219] [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/Richard-Fitzgerald/ASoC-wm_adsp-Don-t

Re: [PATCH] ASoC: wm_adsp: Don't overrun firmware file buffer when reading region data

Hi Richard, [auto build test WARNING on asoc/for-next] [also build test WARNING on v4.9 next-20161219] [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/Richard-Fitzgerald/ASoC-wm_adsp-Don-t

Re: [PATCH] ASoC: wm_adsp: Don't overrun firmware file buffer when reading region data

Hi Richard, [auto build test WARNING on asoc/for-next] [also build test WARNING on v4.9 next-20161219] [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/Richard-Fitzgerald/ASoC-wm_adsp-Don-t

Re: [PATCH v10 0/8] power: add power sequence library

On Mon, Nov 14, 2016 at 09:35:51AM +0800, Peter Chen wrote: > Hi all, > > This is a follow-up for my last power sequence framework patch set [1]. > According to Rob Herring and Ulf Hansson's comments[2]. The kinds of > power sequence instances will be added at postcore_initcall, the match >

Re: [PATCH v10 0/8] power: add power sequence library

On Mon, Nov 14, 2016 at 09:35:51AM +0800, Peter Chen wrote: > Hi all, > > This is a follow-up for my last power sequence framework patch set [1]. > According to Rob Herring and Ulf Hansson's comments[2]. The kinds of > power sequence instances will be added at postcore_initcall, the match >

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