Re: [PATCH 4/4] usb: musb: tusb6010_omap: Convert to DMAengine API

* Peter Ujfalusi [170505 08:20]: > On 2017-05-05 16:37, Peter Ujfalusi wrote: > > On 2017-05-05 00:05, Tony Lindgren wrote: > > > And this sync gpmc issue seems to be timing related. Setting > > > DEBUG in tusb6010_omap.c makes it happen easily while without > > > it it's

Re: [PATCH 4/4] usb: musb: tusb6010_omap: Convert to DMAengine API

* Peter Ujfalusi [170505 08:20]: > On 2017-05-05 16:37, Peter Ujfalusi wrote: > > On 2017-05-05 00:05, Tony Lindgren wrote: > > > And this sync gpmc issue seems to be timing related. Setting > > > DEBUG in tusb6010_omap.c makes it happen easily while without > > > it it's much harder to trigger.

Is iounmap(NULL) safe or not?

Hello, It seems thare are many places where code assumes iounmap(NULL) is safe. Also there are several patches that state it explicitly: ff6defa6a8fa ("ALSA: Deletion of checks before the function call "iounmap") e24bb0ed8179 ("staging: dgnc: remove NULL test") At the same time it seems PPC

Is iounmap(NULL) safe or not?

Hello, It seems thare are many places where code assumes iounmap(NULL) is safe. Also there are several patches that state it explicitly: ff6defa6a8fa ("ALSA: Deletion of checks before the function call "iounmap") e24bb0ed8179 ("staging: dgnc: remove NULL test") At the same time it seems PPC

Re: [PATCH v2] x86, uaccess: introduce copy_from_iter_wt for pmem / writethrough operations

On Fri, 2017-05-05 at 15:25 -0700, Dan Williams wrote: > On Fri, May 5, 2017 at 1:39 PM, Kani, Toshimitsu > wrote: : > > > --- > > > Changes since the initial RFC: > > > * s/writethru/wt/ since we already have ioremap_wt(), > > > set_memory_wt(), etc. (Ingo) > > > > Sorry I

Re: [PATCH v2] x86, uaccess: introduce copy_from_iter_wt for pmem / writethrough operations

On Fri, 2017-05-05 at 15:25 -0700, Dan Williams wrote: > On Fri, May 5, 2017 at 1:39 PM, Kani, Toshimitsu > wrote: : > > > --- > > > Changes since the initial RFC: > > > * s/writethru/wt/ since we already have ioremap_wt(), > > > set_memory_wt(), etc. (Ingo) > > > > Sorry I should have said

[PATCH] scsi: qedf: Avoid reading past end of buffer

Using memcpy() from a string that is shorter than the length copied means the destination buffer is being filled with arbitrary data from the kernel rodata segment. Instead, use strncpy() which will fill the trailing bytes with zeros. This was found with the future CONFIG_FORTIFY_SOURCE feature.

[PATCH] scsi: qedf: Avoid reading past end of buffer

Using memcpy() from a string that is shorter than the length copied means the destination buffer is being filled with arbitrary data from the kernel rodata segment. Instead, use strncpy() which will fill the trailing bytes with zeros. This was found with the future CONFIG_FORTIFY_SOURCE feature.

iommu: Fix incompatible arg type in iommu_put/get_resv_regions

In linux-next struct device dev; was added to struct iommu_device this breaks calls to iommu_put/get_resv_regions function because these functions expect struct device * instead. Please review and consider this patch to fix this. Thanks Manoj Iyer

iommu: Fix incompatible arg type in iommu_put/get_resv_regions

In linux-next struct device dev; was added to struct iommu_device this breaks calls to iommu_put/get_resv_regions function because these functions expect struct device * instead. Please review and consider this patch to fix this. Thanks Manoj Iyer

[PATCH] ray_cs: Avoid reading past end of buffer

Using memcpy() from a buffer that is shorter than the length copied means the destination buffer is being filled with arbitrary data from the kernel rodata segment. In this case, the source was made longer, since it did not match the destination structure size. Additionally removes a needless

[PATCH] iommu: Fix incompatible arg type passed to iommu_get/put_resv_regions

Argument to iommu_get/put_resv_regions function in iommu_get_group_resv_regions function expects a struct device * as first argument, struct device is passed instead. Commit 39ab9555c241 ("iommu: Add sysfs bindings for struct iommu_device") in linux-next adds struct device dev to struct

[PATCH] iommu: Fix incompatible arg type passed to iommu_get/put_resv_regions

Argument to iommu_get/put_resv_regions function in iommu_get_group_resv_regions function expects a struct device * as first argument, struct device is passed instead. Commit 39ab9555c241 ("iommu: Add sysfs bindings for struct iommu_device") in linux-next adds struct device dev to struct

[PATCH] ray_cs: Avoid reading past end of buffer

Using memcpy() from a buffer that is shorter than the length copied means the destination buffer is being filled with arbitrary data from the kernel rodata segment. In this case, the source was made longer, since it did not match the destination structure size. Additionally removes a needless

[PATCH] qlge: Avoid reading past end of buffer

Using memcpy() from a string that is shorter than the length copied means the destination buffer is being filled with arbitrary data from the kernel rodata segment. Instead, use strncpy() which will fill the trailing bytes with zeros. This was found with the future CONFIG_FORTIFY_SOURCE feature.

[PATCH] qlge: Avoid reading past end of buffer

Using memcpy() from a string that is shorter than the length copied means the destination buffer is being filled with arbitrary data from the kernel rodata segment. Instead, use strncpy() which will fill the trailing bytes with zeros. This was found with the future CONFIG_FORTIFY_SOURCE feature.

[PATCH] bna: ethtool: Avoid reading past end of buffer

Using memcpy() from a string that is shorter than the length copied means the destination buffer is being filled with arbitrary data from the kernel rodata segment. Instead, use strncpy() which will fill the trailing bytes with zeros. This was found with the future CONFIG_FORTIFY_SOURCE feature.

[PATCH] bna: ethtool: Avoid reading past end of buffer

Using memcpy() from a string that is shorter than the length copied means the destination buffer is being filled with arbitrary data from the kernel rodata segment. Instead, use strncpy() which will fill the trailing bytes with zeros. This was found with the future CONFIG_FORTIFY_SOURCE feature.

Re: [PATCH v10 3/6] virtio-balloon: VIRTIO_BALLOON_F_PAGE_CHUNKS

On Thu, May 04, 2017 at 04:50:12PM +0800, Wei Wang wrote: > Add a new feature, VIRTIO_BALLOON_F_PAGE_CHUNKS, which enables > the transfer of the ballooned (i.e. inflated/deflated) pages in > chunks to the host. > > The implementation of the previous virtio-balloon is not very > efficient, because

Re: [PATCH v10 3/6] virtio-balloon: VIRTIO_BALLOON_F_PAGE_CHUNKS

On Thu, May 04, 2017 at 04:50:12PM +0800, Wei Wang wrote: > Add a new feature, VIRTIO_BALLOON_F_PAGE_CHUNKS, which enables > the transfer of the ballooned (i.e. inflated/deflated) pages in > chunks to the host. > > The implementation of the previous virtio-balloon is not very > efficient, because

Re: [PATCH v3 1/7] iommu/arm-smmu-v3: Introduce SMMU option PAGE0_REGS_ONLY for ThunderX2 errata #74

On 05.05.17 17:38:05, Geetha sowjanya wrote: > From: Linu Cherian > > Cavium ThunderX2 SMMU implementation doesn't support page 1 register space > and PAGE0_REGS_ONLY option will be enabled as an errata workaround. > > This option when turned on, replaces all page 1

Re: [PATCH v3 1/7] iommu/arm-smmu-v3: Introduce SMMU option PAGE0_REGS_ONLY for ThunderX2 errata #74

On 05.05.17 17:38:05, Geetha sowjanya wrote: > From: Linu Cherian > > Cavium ThunderX2 SMMU implementation doesn't support page 1 register space > and PAGE0_REGS_ONLY option will be enabled as an errata workaround. > > This option when turned on, replaces all page 1 offsets used for >

[PATCH] bna: Avoid reading past end of buffer

Using memcpy() from a string that is shorter than the length copied means the destination buffer is being filled with arbitrary data from the kernel rodata segment. Instead, use strncpy() which will fill the trailing bytes with zeros. This was found with the future CONFIG_FORTIFY_SOURCE feature.

[PATCH] bna: Avoid reading past end of buffer

Using memcpy() from a string that is shorter than the length copied means the destination buffer is being filled with arbitrary data from the kernel rodata segment. Instead, use strncpy() which will fill the trailing bytes with zeros. This was found with the future CONFIG_FORTIFY_SOURCE feature.

Re: [virtio-dev] Re: [PATCH v9 2/5] virtio-balloon: VIRTIO_BALLOON_F_BALLOON_CHUNKS

On Thu, Apr 27, 2017 at 02:31:49PM +0800, Wei Wang wrote: > On 04/27/2017 07:20 AM, Michael S. Tsirkin wrote: > > On Wed, Apr 26, 2017 at 11:03:34AM +, Wang, Wei W wrote: > > > Hi Michael, could you please give some feedback? > > I'm sorry, I'm not sure feedback on what you are requesting. >

Re: [virtio-dev] Re: [PATCH v9 2/5] virtio-balloon: VIRTIO_BALLOON_F_BALLOON_CHUNKS

On Thu, Apr 27, 2017 at 02:31:49PM +0800, Wei Wang wrote: > On 04/27/2017 07:20 AM, Michael S. Tsirkin wrote: > > On Wed, Apr 26, 2017 at 11:03:34AM +, Wang, Wei W wrote: > > > Hi Michael, could you please give some feedback? > > I'm sorry, I'm not sure feedback on what you are requesting. >

Re: [PATCH v2] x86, uaccess: introduce copy_from_iter_wt for pmem / writethrough operations

On Fri, May 5, 2017 at 1:39 PM, Kani, Toshimitsu wrote: > On Fri, 2017-04-28 at 12:39 -0700, Dan Williams wrote: >> The pmem driver has a need to transfer data with a persistent memory >> destination and be able to rely on the fact that the destination >> writes are not

Re: [PATCH v2] x86, uaccess: introduce copy_from_iter_wt for pmem / writethrough operations

On Fri, May 5, 2017 at 1:39 PM, Kani, Toshimitsu wrote: > On Fri, 2017-04-28 at 12:39 -0700, Dan Williams wrote: >> The pmem driver has a need to transfer data with a persistent memory >> destination and be able to rely on the fact that the destination >> writes are not cached. It is sufficient

Re: [PATCH v2] backlight: report error on failure

On Sat, May 6, 2017 at 12:33 AM, Sudip Mukherjee wrote: > It is possible to update the backlight power and the brightness using > the sysfs and on writing it either returns the count or if the callback > function does not exist then returns the error code 'ENXIO'. > >

Re: [PATCH v2] backlight: report error on failure

On Sat, May 6, 2017 at 12:33 AM, Sudip Mukherjee wrote: > It is possible to update the backlight power and the brightness using > the sysfs and on writing it either returns the count or if the callback > function does not exist then returns the error code 'ENXIO'. > > We have a situation where

Re: [PATCH v3 0/7] Cavium ThunderX2 SMMUv3 errata workarounds

On 05.05.17 17:38:04, Geetha sowjanya wrote: > From: Linu Cherian > > Cavium ThunderX2 SMMUv3 implementation has two Silicon Erratas. > 1. Errata ID #74 >SMMU register alias Page 1 is not implemented > 2. Errata ID #126 >SMMU doesnt support unique IRQ lines and

Re: [PATCH v3 0/7] Cavium ThunderX2 SMMUv3 errata workarounds

On 05.05.17 17:38:04, Geetha sowjanya wrote: > From: Linu Cherian > > Cavium ThunderX2 SMMUv3 implementation has two Silicon Erratas. > 1. Errata ID #74 >SMMU register alias Page 1 is not implemented > 2. Errata ID #126 >SMMU doesnt support unique IRQ lines and also MSI for gerror, >

Re: [PATCH V3] cpuidle: check dev before usage in cpuidle_use_deepest_state

On Sat, May 6, 2017 at 12:33 AM, Rafael J. Wysocki wrote: > On Thursday, May 04, 2017 09:00:52 AM Li, Fei wrote: >> Fixes: bb8313b603eb8 ("cpuidle: Allow enforcing deepest idle state >> selection") >> Signed-off-by: Li, Fei >> Tested-by: Shi, Feng

Re: [PATCH V3] cpuidle: check dev before usage in cpuidle_use_deepest_state

On Sat, May 6, 2017 at 12:33 AM, Rafael J. Wysocki wrote: > On Thursday, May 04, 2017 09:00:52 AM Li, Fei wrote: >> Fixes: bb8313b603eb8 ("cpuidle: Allow enforcing deepest idle state >> selection") >> Signed-off-by: Li, Fei >> Tested-by: Shi, Feng >> Reviewed-by: Andy Shevchenko >>

Re: [PATCH v9 5/5] virtio-balloon: VIRTIO_BALLOON_F_MISC_VQ

On Thu, Apr 27, 2017 at 02:33:44PM +0800, Wei Wang wrote: > On 04/14/2017 01:08 AM, Michael S. Tsirkin wrote: > > On Thu, Apr 13, 2017 at 05:35:08PM +0800, Wei Wang wrote: > > > Add a new vq, miscq, to handle miscellaneous requests between the device > > > and the driver. > > > > > > This patch

Re: [PATCH v9 5/5] virtio-balloon: VIRTIO_BALLOON_F_MISC_VQ

On Thu, Apr 27, 2017 at 02:33:44PM +0800, Wei Wang wrote: > On 04/14/2017 01:08 AM, Michael S. Tsirkin wrote: > > On Thu, Apr 13, 2017 at 05:35:08PM +0800, Wei Wang wrote: > > > Add a new vq, miscq, to handle miscellaneous requests between the device > > > and the driver. > > > > > > This patch

Re: [PATCH v3 5/7] ACPI/IORT: Fixup SMMUv3 resource size for Cavium ThunderX2 SMMUv3 model

On 05.05.17 17:38:09, Geetha sowjanya wrote: > From: Linu Cherian > > Cavium ThunderX2 implementation doesn't support second page in SMMU > register space. Hence, resource size is set as 64k for this model. > > Signed-off-by: Linu Cherian >

Re: [PATCH v3 5/7] ACPI/IORT: Fixup SMMUv3 resource size for Cavium ThunderX2 SMMUv3 model

On 05.05.17 17:38:09, Geetha sowjanya wrote: > From: Linu Cherian > > Cavium ThunderX2 implementation doesn't support second page in SMMU > register space. Hence, resource size is set as 64k for this model. > > Signed-off-by: Linu Cherian > Signed-off-by: Geetha Sowjanya > --- >

Re: [PATCH v3 2/7] iommu/arm-smmu-v3: Do resource size checks based on SMMU

On 05.05.17 17:38:06, Geetha sowjanya wrote: > From: Linu Cherian > > With implementations supporting only page 0 register space, > resource size can be 64k as well and hence perform size checks > based on SMMU option PAGE0_REGS_ONLY. > > For this,

Re: [PATCH v3 2/7] iommu/arm-smmu-v3: Do resource size checks based on SMMU

On 05.05.17 17:38:06, Geetha sowjanya wrote: > From: Linu Cherian > > With implementations supporting only page 0 register space, > resource size can be 64k as well and hence perform size checks > based on SMMU option PAGE0_REGS_ONLY. > > For this, arm_smmu_device_dt_probe/acpi_probe has been

Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode

On Fri, Apr 28, 2017 at 8:32 AM, Thomas Garnier wrote: > Ensure that a syscall does not return to user-mode with a kernel address > limit. If that happens, a process can corrupt kernel-mode memory and > elevate privileges [1]. > > The CONFIG_ADDR_LIMIT_CHECK option disables

Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode

On Fri, Apr 28, 2017 at 8:32 AM, Thomas Garnier wrote: > Ensure that a syscall does not return to user-mode with a kernel address > limit. If that happens, a process can corrupt kernel-mode memory and > elevate privileges [1]. > > The CONFIG_ADDR_LIMIT_CHECK option disables the generic check so

Re: [PATCH v10 4/6] mm: function to offer a page block on the free list

e system] > > url: > https://github.com/0day-ci/linux/commits/Wei-Wang/Extend-virtio-balloon-for-fast-de-inflating-fast-live-migration/20170505-052958 > reproduce: make htmldocs > > All warnings (new ones prefixed by >>): > >WARNING: convert(1) not found, for SVG

Re: [PATCH v10 4/6] mm: function to offer a page block on the free list

e system] > > url: > https://github.com/0day-ci/linux/commits/Wei-Wang/Extend-virtio-balloon-for-fast-de-inflating-fast-live-migration/20170505-052958 > reproduce: make htmldocs > > All warnings (new ones prefixed by >>): > >WARNING: convert(1) not found, for SVG

Re: [PATCH v2 4/7] staging: rtl8723bs: Move braces to same line as conditional

Bastien Nocera writes: > On Mon, 2017-05-01 at 18:52 -0600, Justin Vreeland wrote: >> Ensure checkpatch compliance >> >> > Signed-off-by: Justin Vreeland >> --- >> v2: >>   - Added commit message >>   - Fixed overly long lines >> >>  

Re: [PATCH v2 4/7] staging: rtl8723bs: Move braces to same line as conditional

Bastien Nocera writes: > On Mon, 2017-05-01 at 18:52 -0600, Justin Vreeland wrote: >> Ensure checkpatch compliance >> >> > Signed-off-by: Justin Vreeland >> --- >> v2: >>   - Added commit message >>   - Fixed overly long lines >> >>  drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c | 18

Re: [PATCH v4] irqchip/gicv3-its: Avoid memory over allocation for ITEs

Hi Marc, On 05/02/2017 11:16 AM, Marc Zyngier wrote: > On Sun, Apr 30 2017 at 3:36:15 pm BST, Shanker Donthineni > wrote: >> We are always allocating extra 255Bytes of memory to handle ITE >> physical address alignment requirement. The kmalloc() satisfies >> the ITE

Re: [PATCH v4] irqchip/gicv3-its: Avoid memory over allocation for ITEs

Hi Marc, On 05/02/2017 11:16 AM, Marc Zyngier wrote: > On Sun, Apr 30 2017 at 3:36:15 pm BST, Shanker Donthineni > wrote: >> We are always allocating extra 255Bytes of memory to handle ITE >> physical address alignment requirement. The kmalloc() satisfies >> the ITE alignment since the ITS

Re: [PATCH v2 4/7] staging: rtl8723bs: Move braces to same line as conditional

Bastien Nocera writes: > On Mon, 2017-05-01 at 18:52 -0600, Justin Vreeland wrote: >> Ensure checkpatch compliance >> >> > Signed-off-by: Justin Vreeland >> --- >> v2: >>   - Added commit message >>   - Fixed overly long lines >> >>  

Re: [PATCH v2 4/7] staging: rtl8723bs: Move braces to same line as conditional

Bastien Nocera writes: > On Mon, 2017-05-01 at 18:52 -0600, Justin Vreeland wrote: >> Ensure checkpatch compliance >> >> > Signed-off-by: Justin Vreeland >> --- >> v2: >>   - Added commit message >>   - Fixed overly long lines >> >>  drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c | 18

[PATCH 1/3] staging: rtl8723bs: merge fix for add/change_virtual-intf API change

From: Stephen Rothwell This fixes the add/change_virtual-intf API change that happened in the wifi tree in the rtl8723bs driver. Signed-off-by: Stephen Rothwell Signed-off-by: Greg Kroah-Hartman ---

[PATCH 3/3] staging: rtl8723bs: fix up for cfg80211_roamed() API change

From: Stephen Rothwell Another fixup for the wifi changes that came from that tree for the rtl8723bs driver. Signed-off-by: Stephen Rothwell Signed-off-by: Greg Kroah-Hartman ---

[PATCH 1/3] staging: rtl8723bs: merge fix for add/change_virtual-intf API change

From: Stephen Rothwell This fixes the add/change_virtual-intf API change that happened in the wifi tree in the rtl8723bs driver. Signed-off-by: Stephen Rothwell Signed-off-by: Greg Kroah-Hartman --- drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 4 ++-- 1 file changed, 2 insertions(+),

[PATCH 3/3] staging: rtl8723bs: fix up for cfg80211_roamed() API change

From: Stephen Rothwell Another fixup for the wifi changes that came from that tree for the rtl8723bs driver. Signed-off-by: Stephen Rothwell Signed-off-by: Greg Kroah-Hartman --- drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 20 1 file changed, 12 insertions(+), 8

Re: Q. drm/i915 shrinker, synchronize_rcu_expedited() from handlers

On Fri, 5 May 2017, Joonas Lahtinen wrote: > On ma, 2017-05-01 at 11:05 +0900, J. R. Okajima wrote: > > Thanx for the reply. > > > > Andrea Arcangeli: > > > > > > Yes I already reported this, my original fix was way more efficient > > > (and also safer considering the above) than what landed

Re: Q. drm/i915 shrinker, synchronize_rcu_expedited() from handlers

On Fri, 5 May 2017, Joonas Lahtinen wrote: > On ma, 2017-05-01 at 11:05 +0900, J. R. Okajima wrote: > > Thanx for the reply. > > > > Andrea Arcangeli: > > > > > > Yes I already reported this, my original fix was way more efficient > > > (and also safer considering the above) than what landed

[PATCH 2/3] staging: rtl8723bs: merge fix for "nl80211: allow multiple active scheduled scan requests"

From: Stephen Rothwell Fix up the rtl8723bs driver for the nl80211 api change that came in from the wifi tree. Signed-off-by: Stephen Rothwell Signed-off-by: Greg Kroah-Hartman ---

[PATCH 2/3] staging: rtl8723bs: merge fix for "nl80211: allow multiple active scheduled scan requests"

From: Stephen Rothwell Fix up the rtl8723bs driver for the nl80211 api change that came in from the wifi tree. Signed-off-by: Stephen Rothwell Signed-off-by: Greg Kroah-Hartman --- drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [PATCH] ACPI: SPCR: Use access width to determine mmio usage

On Thu, May 4, 2017 at 11:09 PM, Zheng, Lv wrote: > Hi, > >> From: Jon Mason [mailto:jon.ma...@broadcom.com] >> Sent: Thursday, May 4, 2017 11:06 PM >> Subject: [PATCH] ACPI: SPCR: Use access width to determine mmio usage >> >> The current SPCR code does not check the access

RE: RFC: WMI Enhancements

> -Original Message- > From: Darren Hart [mailto:dvh...@infradead.org] > Sent: Thursday, April 20, 2017 3:45 PM > To: Pali Rohár > Cc: Limonciello, Mario ; r...@rjwysocki.net; > l...@amacapital.net; len.br...@intel.com;

[PATCH v2] ACPI: SPCR: Use access width to determine mmio usage

The current SPCR code does not check the access width of the mmio, and uses a default of 8bit register accesses. This prevents devices that only do 16 or 32bit register accesses from working. By simply checking this field and setting the mmio string appropriately, this issue can be corrected.

Re: [PATCH] ACPI: SPCR: Use access width to determine mmio usage

On Thu, May 4, 2017 at 11:09 PM, Zheng, Lv wrote: > Hi, > >> From: Jon Mason [mailto:jon.ma...@broadcom.com] >> Sent: Thursday, May 4, 2017 11:06 PM >> Subject: [PATCH] ACPI: SPCR: Use access width to determine mmio usage >> >> The current SPCR code does not check the access width of the mmio,

RE: RFC: WMI Enhancements

> -Original Message- > From: Darren Hart [mailto:dvh...@infradead.org] > Sent: Thursday, April 20, 2017 3:45 PM > To: Pali Rohár > Cc: Limonciello, Mario ; r...@rjwysocki.net; > l...@amacapital.net; len.br...@intel.com; corentin.ch...@gmail.com; > l...@kernel.org;

[PATCH v2] ACPI: SPCR: Use access width to determine mmio usage

The current SPCR code does not check the access width of the mmio, and uses a default of 8bit register accesses. This prevents devices that only do 16 or 32bit register accesses from working. By simply checking this field and setting the mmio string appropriately, this issue can be corrected.

Re: [PATCH] pinctrl: use non-devm kmalloc versions for free functions

Hello, Maxime. On Fri, May 05, 2017 at 09:55:18PM +0200, Maxime Ripard wrote: > > It doesn't make any sense to use the managed functions from the > > release functions and if you're always matching devm_kmalloc() with > > devm_kfree(), the only thing it'd do is confusing its readers. > > I

Re: [PATCH] pinctrl: use non-devm kmalloc versions for free functions

Hello, Maxime. On Fri, May 05, 2017 at 09:55:18PM +0200, Maxime Ripard wrote: > > It doesn't make any sense to use the managed functions from the > > release functions and if you're always matching devm_kmalloc() with > > devm_kfree(), the only thing it'd do is confusing its readers. > > I

[Resend][PATCH] cpufreq: intel_pstate: Document the current behavior and user interface

From: Rafael J. Wysocki Add a document describing the current behavior and user space interface of the intel_pstate driver in the RST format and drop the existing outdated intel_pstate.txt document. Also update admin-guide/pm/cpufreq.rst with proper RST references to

[Resend][PATCH] cpufreq: intel_pstate: Document the current behavior and user interface

From: Rafael J. Wysocki Add a document describing the current behavior and user space interface of the intel_pstate driver in the RST format and drop the existing outdated intel_pstate.txt document. Also update admin-guide/pm/cpufreq.rst with proper RST references to the new intel_pstate.rst

Re: [PATCH v3 2/4] dt-binding: meson_uart: add documentation for the UARTs of amlogic

Hi Helmut, On Fri, Mar 31, 2017 at 6:54 PM, Helmut Klein wrote: > Add the documentation for the device tree binding of meson_uart > > Signed-off-by: Helmut Klein > --- > .../bindings/serial/amlogic,meson_uart.txt | 30 >

Re: [PATCH v3 2/4] dt-binding: meson_uart: add documentation for the UARTs of amlogic

Hi Helmut, On Fri, Mar 31, 2017 at 6:54 PM, Helmut Klein wrote: > Add the documentation for the device tree binding of meson_uart > > Signed-off-by: Helmut Klein > --- > .../bindings/serial/amlogic,meson_uart.txt | 30 > ++ > 1 file changed, 30 insertions(+) >

[GIT PULL] libnvdimm for 4.12

Hi Linus, please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-for-4.12 ...to receive the libnvdimm update for 4.12. The bulk of this has been in multiple -next releases. There were a few late breaking fixes and small features that got added in the last

[GIT PULL] libnvdimm for 4.12

Hi Linus, please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-for-4.12 ...to receive the libnvdimm update for 4.12. The bulk of this has been in multiple -next releases. There were a few late breaking fixes and small features that got added in the last

Re: [PATCH V3] cpuidle: check dev before usage in cpuidle_use_deepest_state

On Thursday, May 04, 2017 09:00:52 AM Li, Fei wrote: > In case of there is no cpuidle devices registered, dev will be null, and > panic will be triggered like below; > In this patch, add checking of dev before usage, like that done in > cpuidle_idle_call. > > Panic without fix: > [ 184.961328]

Re: [PATCH V3] cpuidle: check dev before usage in cpuidle_use_deepest_state

On Thursday, May 04, 2017 09:00:52 AM Li, Fei wrote: > In case of there is no cpuidle devices registered, dev will be null, and > panic will be triggered like below; > In this patch, add checking of dev before usage, like that done in > cpuidle_idle_call. > > Panic without fix: > [ 184.961328]

Re: [Intel-gfx] [PATCH RESEND] drm/i915: Fix pipe/transcoder enum mismatches

Hi, El Fri, May 05, 2017 at 01:29:32PM -0700 Grant Grundler ha dit: > On Fri, May 5, 2017 at 1:08 PM, Ville Syrjälä > wrote: > ... > >> > I'm not convinced the patch is making things any better really. To > >> > fix this really properly, I think we'd need to

Re: [Intel-gfx] [PATCH RESEND] drm/i915: Fix pipe/transcoder enum mismatches

Hi, El Fri, May 05, 2017 at 01:29:32PM -0700 Grant Grundler ha dit: > On Fri, May 5, 2017 at 1:08 PM, Ville Syrjälä > wrote: > ... > >> > I'm not convinced the patch is making things any better really. To > >> > fix this really properly, I think we'd need to introduce a new enum > >> >

[PATCH v2] backlight: report error on failure

It is possible to update the backlight power and the brightness using the sysfs and on writing it either returns the count or if the callback function does not exist then returns the error code 'ENXIO'. We have a situation where the userspace client is writing to the sysfs to update the power and

[PATCH v2] backlight: report error on failure

It is possible to update the backlight power and the brightness using the sysfs and on writing it either returns the count or if the callback function does not exist then returns the error code 'ENXIO'. We have a situation where the userspace client is writing to the sysfs to update the power and

Re: [tip:x86/urgent] x86/mm/kaslr: Use the _ASM_MUL macro for multiplication to work around Clang incompatibility

Hi Peter, El Fri, May 05, 2017 at 12:37:23PM -0700 h...@zytor.com ha dit: > On May 5, 2017 11:44:05 AM PDT, Matthias Kaehlcke wrote: > >El Fri, May 05, 2017 at 07:50:39PM +0200 Ingo Molnar ha dit: > > > >> > >> * Peter Zijlstra wrote: > >> > >> > On

Re: [tip:x86/urgent] x86/mm/kaslr: Use the _ASM_MUL macro for multiplication to work around Clang incompatibility

Hi Peter, El Fri, May 05, 2017 at 12:37:23PM -0700 h...@zytor.com ha dit: > On May 5, 2017 11:44:05 AM PDT, Matthias Kaehlcke wrote: > >El Fri, May 05, 2017 at 07:50:39PM +0200 Ingo Molnar ha dit: > > > >> > >> * Peter Zijlstra wrote: > >> > >> > On Fri, May 05, 2017 at 01:11:47AM -0700,

Re: [PATCH 1/1 linux-next] efi/capsule: kmap() can't fail

On Tue, 25 Apr, at 08:10:51PM, Fabian Frederick wrote: > Remove NULL test on kmap() > > Signed-off-by: Fabian Frederick > --- > drivers/firmware/efi/capsule-loader.c | 5 - > drivers/firmware/efi/capsule.c| 4 > 2 files changed, 9 deletions(-) > > diff --git

Re: [PATCH 1/1 linux-next] efi/capsule: kmap() can't fail

On Tue, 25 Apr, at 08:10:51PM, Fabian Frederick wrote: > Remove NULL test on kmap() > > Signed-off-by: Fabian Frederick > --- > drivers/firmware/efi/capsule-loader.c | 5 - > drivers/firmware/efi/capsule.c| 4 > 2 files changed, 9 deletions(-) > > diff --git

Re: kernel-trace: Fine-tuning for seven function implementations

> Just to let you know, it's never a good idea to send new patches out > during the merge window. Thanks for such information. > They are most likely to be missed and forgotten during this time. This can happen then occasionally. > Unless they are critical bug fixes, it's best to wait till

Re: kernel-trace: Fine-tuning for seven function implementations

> Just to let you know, it's never a good idea to send new patches out > during the merge window. Thanks for such information. > They are most likely to be missed and forgotten during this time. This can happen then occasionally. > Unless they are critical bug fixes, it's best to wait till

[PATCH 7/7] kernel-trace: Delete an error message for a failed memory allocation in create_trace_uprobe()

From: Markus Elfring Date: Fri, 5 May 2017 22:38:51 +0200 The script "checkpatch.pl" pointed information out like the following. WARNING: Possible unnecessary 'out of memory' message Thus remove such a statement here. Link:

[PATCH 7/7] kernel-trace: Delete an error message for a failed memory allocation in create_trace_uprobe()

From: Markus Elfring Date: Fri, 5 May 2017 22:38:51 +0200 The script "checkpatch.pl" pointed information out like the following. WARNING: Possible unnecessary 'out of memory' message Thus remove such a statement here. Link:

[PATCH 6/7] kernel-trace: Adjust two checks for null pointers in uprobe_buffer_init()

From: Markus Elfring Date: Fri, 5 May 2017 22:30:16 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written !… Thus

[PATCH 6/7] kernel-trace: Adjust two checks for null pointers in uprobe_buffer_init()

From: Markus Elfring Date: Fri, 5 May 2017 22:30:16 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written !… Thus fix the affected source code

Re: [PATCH v3 0/2] usb: Check for DMA capable buffer sanity

On 04/25/2017 05:56 PM, Florian Fainelli wrote: > Changes in v3: > > - added check in usb_gadget_map_request_by_dev (Felipe), new patch > - improved commit message description (Clemens) > - added additiona checks for urb->setup_packet (Alan) > > Changes in v2: > > - moved the check from

Re: [PATCH v3 0/2] usb: Check for DMA capable buffer sanity

On 04/25/2017 05:56 PM, Florian Fainelli wrote: > Changes in v3: > > - added check in usb_gadget_map_request_by_dev (Felipe), new patch > - improved commit message description (Clemens) > - added additiona checks for urb->setup_packet (Alan) > > Changes in v2: > > - moved the check from

Re: [RESEND PATCH] spi: bcm63xx-hsspi: Export OF device ID table as module aliases

On 05/01/2017 01:13 PM, Andres Galacho wrote: > The device table is required to load modules based on > modaliases. After adding MODULE_DEVICE_TABLE, below entries > for example will be added to module.alias: > alias: of:N*T*Cbrcm,bcm6328-hsspiC* > alias:

Re: [RESEND PATCH] spi: bcm63xx-hsspi: Export OF device ID table as module aliases

On 05/01/2017 01:13 PM, Andres Galacho wrote: > The device table is required to load modules based on > modaliases. After adding MODULE_DEVICE_TABLE, below entries > for example will be added to module.alias: > alias: of:N*T*Cbrcm,bcm6328-hsspiC* > alias:

Re: [PATCH] rtc: rtc-efi: Add an enable parameter and make it false for X86 by default

On Tue, 02 May, at 08:51:47AM, Ocean HY1 He wrote: > The commit 7efe665903d0 ("rtc: Disable EFI rtc for x86") turns off rtc-efi > option completely for x86 in rtc/Kconfig, to avoid possible crash caused by > buggy implementations of the time-related EFI runtime services. > > In fact, there are

Re: [PATCH] rtc: rtc-efi: Add an enable parameter and make it false for X86 by default

On Tue, 02 May, at 08:51:47AM, Ocean HY1 He wrote: > The commit 7efe665903d0 ("rtc: Disable EFI rtc for x86") turns off rtc-efi > option completely for x86 in rtc/Kconfig, to avoid possible crash caused by > buggy implementations of the time-related EFI runtime services. > > In fact, there are

Re: GFS2: Pull request (merge window)

On Fri, May 5, 2017 at 1:28 PM, Bob Peterson wrote: > > I asked around, but nobody could tell me what went wrong. Strangely, > this command: > > git log --oneline --right-only origin/master...FETCH_HEAD --stat > > doesn't show this, but this one does: > > git diff --stat

Re: GFS2: Pull request (merge window)

On Fri, May 5, 2017 at 1:28 PM, Bob Peterson wrote: > > I asked around, but nobody could tell me what went wrong. Strangely, > this command: > > git log --oneline --right-only origin/master...FETCH_HEAD --stat > > doesn't show this, but this one does: > > git diff --stat --right-only

Re: [PATCH v3 3/3] arm64: Silence first allocation with CONFIG_ARM64_MODULE_PLTS=y

On 05/03/2017 04:18 AM, Will Deacon wrote: > On Thu, Apr 27, 2017 at 11:19:02AM -0700, Florian Fainelli wrote: >> When CONFIG_ARM64_MODULE_PLTS is enabled, the first allocation using the >> module space fails, because the module is too big, and then the module >> allocation is attempted from

Re: [PATCH v3 3/3] arm64: Silence first allocation with CONFIG_ARM64_MODULE_PLTS=y

On 05/03/2017 04:18 AM, Will Deacon wrote: > On Thu, Apr 27, 2017 at 11:19:02AM -0700, Florian Fainelli wrote: >> When CONFIG_ARM64_MODULE_PLTS is enabled, the first allocation using the >> module space fails, because the module is too big, and then the module >> allocation is attempted from

Re: [PATCH 0/7] kernel-trace: Fine-tuning for seven function implementations

On Fri, 5 May 2017 23:00:41 +0200 SF Markus Elfring wrote: > From: Markus Elfring > Date: Fri, 5 May 2017 22:50:05 +0200 > > A few update suggestions were taken into account > from static source code analysis. > > Markus Elfring

[PATCH 5/7] kernel-trace: Replace two seq_printf() calls by seq_puts() in probes_seq_show()

From: Markus Elfring Date: Fri, 5 May 2017 20:30:05 +0200 Two strings which did not contain data format specifications should be put into a sequence. Thus use the corresponding function "seq_puts". This issue was detected by using the Coccinelle software.

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