Re: [PATCH v3 01/18] xen: introduce the pvcalls interface header

On 06/02/2017 03:31 PM, Stefano Stabellini wrote: > Introduce the C header file which defines the PV Calls interface. It is > imported from xen/include/public/io/pvcalls.h. > > Signed-off-by: Stefano Stabellini > CC: konrad.w...@oracle.com > CC: boris.ostrov...@oracle.com >

Re: [PATCH v3 01/18] xen: introduce the pvcalls interface header

On 06/02/2017 03:31 PM, Stefano Stabellini wrote: > Introduce the C header file which defines the PV Calls interface. It is > imported from xen/include/public/io/pvcalls.h. > > Signed-off-by: Stefano Stabellini > CC: konrad.w...@oracle.com > CC: boris.ostrov...@oracle.com > CC: jgr...@suse.com

Re: [PATCH] ARM64: Kconfig: Fix the missing hi655x common clk

On Mon, Jun 12, 2017 at 11:38 AM, Daniel Lezcano wrote: > On Fri, Jun 09, 2017 at 10:48:13PM +0200, Arnd Bergmann wrote: >> On Fri, Jun 9, 2017 at 10:15 PM, John Stultz wrote: >> > On Fri, Jun 9, 2017 at 1:06 PM, Arnd Bergmann

Re: [PATCH] ARM64: Kconfig: Fix the missing hi655x common clk

On Mon, Jun 12, 2017 at 11:38 AM, Daniel Lezcano wrote: > On Fri, Jun 09, 2017 at 10:48:13PM +0200, Arnd Bergmann wrote: >> On Fri, Jun 9, 2017 at 10:15 PM, John Stultz wrote: >> > On Fri, Jun 9, 2017 at 1:06 PM, Arnd Bergmann wrote: >> >> On Fri, Jun 9, 2017 at 5:46 PM, Daniel Lezcano >> >>

[PATCH v2 4/8] ACPI / PM: Clean up device wakeup enable/disable code

From: Rafael J. Wysocki The wakeup.flags.enabled flag in struct acpi_device is not used consistently, as there is no reason why it should only apply to the enabling/disabling of the wakeup GPE, so put the invocation of acpi_enable_wakeup_device_power() under it too.

[PATCH v2 4/8] ACPI / PM: Clean up device wakeup enable/disable code

From: Rafael J. Wysocki The wakeup.flags.enabled flag in struct acpi_device is not used consistently, as there is no reason why it should only apply to the enabling/disabling of the wakeup GPE, so put the invocation of acpi_enable_wakeup_device_power() under it too. Moreover, it is not

Re: [tip:timers/core] posix-timers: Zero out oldval itimerspec

On Mon, Jun 12, 2017 at 12:13:15PM -0700, tip-bot for Thomas Gleixner wrote: > Commit-ID: 5c7a3a3d20a4e175304c0e23809e3d70be8fed8a > Gitweb: http://git.kernel.org/tip/5c7a3a3d20a4e175304c0e23809e3d70be8fed8a > Author: Thomas Gleixner > AuthorDate: Mon, 12 Jun 2017

Re: [tip:timers/core] posix-timers: Zero out oldval itimerspec

On Mon, Jun 12, 2017 at 12:13:15PM -0700, tip-bot for Thomas Gleixner wrote: > Commit-ID: 5c7a3a3d20a4e175304c0e23809e3d70be8fed8a > Gitweb: http://git.kernel.org/tip/5c7a3a3d20a4e175304c0e23809e3d70be8fed8a > Author: Thomas Gleixner > AuthorDate: Mon, 12 Jun 2017 19:44:09 +0200 >

[PATCH v2 3/8] ACPI / PM: Change log level of wakeup-related message

From: Rafael J. Wysocki Change the log level of the "System wakeup enabled/disabled by ACPI" message in acpi_pm_device_sleep_wake() to "debug" to reduce to log noise level. Signed-off-by: Rafael J. Wysocki --- drivers/acpi/device_pm.c |

[PATCH v2 3/8] ACPI / PM: Change log level of wakeup-related message

From: Rafael J. Wysocki Change the log level of the "System wakeup enabled/disabled by ACPI" message in acpi_pm_device_sleep_wake() to "debug" to reduce to log noise level. Signed-off-by: Rafael J. Wysocki --- drivers/acpi/device_pm.c |4 ++-- 1 file changed, 2 insertions(+), 2

[PATCH v2 8/8] ACPI / PM: Ignore spurious SCI wakeups from suspend-to-idle

From: Rafael J. Wysocki The ACPI SCI (System Control Interrupt) is set up as a wakeup IRQ during suspend-to-idle transitions and, consequently, any events signaled through it wake up the system from that state. However, on some systems some of the events signaled via

[PATCH v2 8/8] ACPI / PM: Ignore spurious SCI wakeups from suspend-to-idle

From: Rafael J. Wysocki The ACPI SCI (System Control Interrupt) is set up as a wakeup IRQ during suspend-to-idle transitions and, consequently, any events signaled through it wake up the system from that state. However, on some systems some of the events signaled via the ACPI SCI while

[PATCH v2 2/8] USB / PCI / PM: Allow the PCI core to do the resume cleanup

From: Rafael J. Wysocki hcd_pci_resume_noirq() used as a universal _resume_noirq handler for PCI USB controllers calls pci_back_from_sleep() which is unnecessary and may become problematic. It is unnecessary, because the PCI bus type carries out post-suspend cleanup

[PATCH v2 2/8] USB / PCI / PM: Allow the PCI core to do the resume cleanup

From: Rafael J. Wysocki hcd_pci_resume_noirq() used as a universal _resume_noirq handler for PCI USB controllers calls pci_back_from_sleep() which is unnecessary and may become problematic. It is unnecessary, because the PCI bus type carries out post-suspend cleanup of all PCI devices during

[PATCH v2 7/8] platform/x86: Add driver for ACPI INT0002 Virtual GPIO device

From: Hans de Goede Some peripherals on Bay Trail and Cherry Trail platforms signal a Power Management Event (PME) to the Power Management Controller (PMC) to wakeup the system. When this happens software needs to explicitly clear the PME bus 0 status bit in the GPE0a_STS

[PATCH v2 0/8] ACPI / PM: Suspend-to-idle rework to deal with spurious ACPI wakeups

Hi All, On Thursday, June 08, 2017 02:00:40 AM Rafael J. Wysocki wrote: > Hi All, > > This series is a replacement for commit eed4d47efe95 (ACPI / sleep: Ignore > spurious SCI wakeups from suspend-to-idle) which is still there in 4.12-rc4 > but > will be reverted shortly, because it triggered

[PATCH v2 7/8] platform/x86: Add driver for ACPI INT0002 Virtual GPIO device

From: Hans de Goede Some peripherals on Bay Trail and Cherry Trail platforms signal a Power Management Event (PME) to the Power Management Controller (PMC) to wakeup the system. When this happens software needs to explicitly clear the PME bus 0 status bit in the GPE0a_STS register to avoid an

[PATCH v2 0/8] ACPI / PM: Suspend-to-idle rework to deal with spurious ACPI wakeups

Hi All, On Thursday, June 08, 2017 02:00:40 AM Rafael J. Wysocki wrote: > Hi All, > > This series is a replacement for commit eed4d47efe95 (ACPI / sleep: Ignore > spurious SCI wakeups from suspend-to-idle) which is still there in 4.12-rc4 > but > will be reverted shortly, because it triggered

[PATCH] kernel/groups.c: use sort library function

setgroups is not exactly a hot path, so we might as well use the library function instead of open-coding the sorting. Saves ~150 bytes. Signed-off-by: Rasmus Villemoes --- kernel/groups.c | 35 +++ 1 file changed, 11 insertions(+), 24

[PATCH] kernel/groups.c: use sort library function

setgroups is not exactly a hot path, so we might as well use the library function instead of open-coding the sorting. Saves ~150 bytes. Signed-off-by: Rasmus Villemoes --- kernel/groups.c | 35 +++ 1 file changed, 11 insertions(+), 24 deletions(-) diff --git

[PATCH v2 5/8] PM / sleep: Print timing information if debug is enabled

From: Rafael J. Wysocki Avoid printing the device suspend/resume timing information if CONFIG_PM_DEBUG is not set to reduce the log noise level. Signed-off-by: Rafael J. Wysocki --- drivers/base/power/main.c |4 1 file changed,

[PATCH v2 5/8] PM / sleep: Print timing information if debug is enabled

From: Rafael J. Wysocki Avoid printing the device suspend/resume timing information if CONFIG_PM_DEBUG is not set to reduce the log noise level. Signed-off-by: Rafael J. Wysocki --- drivers/base/power/main.c |4 1 file changed, 4 insertions(+) Index:

[PATCH v2 6/8] PCI / PM: Restore PME Enable if skipping wakeup setup

From: Rafael J. Wysocki The wakeup_prepared PCI device flag is used for preventing subsequent changes of PCI device wakeup settings in the same way (e.g. enabling device wakeup twice in a row). However, in some cases PME Enable may be updated by things like PCI

[PATCH v2 6/8] PCI / PM: Restore PME Enable if skipping wakeup setup

From: Rafael J. Wysocki The wakeup_prepared PCI device flag is used for preventing subsequent changes of PCI device wakeup settings in the same way (e.g. enabling device wakeup twice in a row). However, in some cases PME Enable may be updated by things like PCI configuration space restoration

[PATCH v2 1/8] ACPI / PM: Run wakeup notify handlers synchronously

From: Rafael J. Wysocki The work functions provided by the users of acpi_add_pm_notifier() should be run synchronously before re-enabling the wakeup GPE in case they are used to clear the status and/or disable the wakeup signaling at the source. Otherwise, which is

[PATCH v2 1/8] ACPI / PM: Run wakeup notify handlers synchronously

From: Rafael J. Wysocki The work functions provided by the users of acpi_add_pm_notifier() should be run synchronously before re-enabling the wakeup GPE in case they are used to clear the status and/or disable the wakeup signaling at the source. Otherwise, which is the case currently in the PCI

An inconsistent behaviour if using built-in initramfs and damaged external one

Hi, during my experiments with initramfs I have noticed there is something that looks like a bug in the 9-year old code[1] of the clean_rootfs() function in init/initramfs.c. An inconsistent behaviour appears when I have both the built-in initramfs and the one in the external file but the

An inconsistent behaviour if using built-in initramfs and damaged external one

Hi, during my experiments with initramfs I have noticed there is something that looks like a bug in the 9-year old code[1] of the clean_rootfs() function in init/initramfs.c. An inconsistent behaviour appears when I have both the built-in initramfs and the one in the external file but the

Re: [PATCH 2/2] include: warn for inconsistent endian config definition

On Mon, Jun 12, 2017 at 1:51 PM, Arnd Bergmann wrote: > That way, we don't have to guess what the toolchain does, but rather > tell it to do whatever is configured, like we do for most other architectures. > > Unfortunately we can't do the same thing on xtensa, as that no longer >

Re: [PATCH 2/2] include: warn for inconsistent endian config definition

On Mon, Jun 12, 2017 at 1:51 PM, Arnd Bergmann wrote: > That way, we don't have to guess what the toolchain does, but rather > tell it to do whatever is configured, like we do for most other architectures. > > Unfortunately we can't do the same thing on xtensa, as that no longer > supports the

Re: [10/10] Staging: rtl8712: ieee80211: fixed coding style issue

On Mon, Jun 12, 2017 at 12:14:06AM +0530, Jaya Durga wrote: > Fixed WARNING: line over 80 characters > > Signed-off-by: Jaya Durga > --- > drivers/staging/rtl8712/ieee80211.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > -- > 1.9.1 > > diff --git

Re: [10/10] Staging: rtl8712: ieee80211: fixed coding style issue

On Mon, Jun 12, 2017 at 12:14:06AM +0530, Jaya Durga wrote: > Fixed WARNING: line over 80 characters > > Signed-off-by: Jaya Durga > --- > drivers/staging/rtl8712/ieee80211.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > -- > 1.9.1 > > diff --git

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

On 06/12/2017 01:34 PM, Michael S. Tsirkin wrote: > On Mon, Jun 12, 2017 at 09:42:36AM -0700, Dave Hansen wrote: >> On 06/12/2017 09:28 AM, Michael S. Tsirkin wrote: >>> The hypervisor is going to throw away the contents of these pages, right? >>> It should be careful and only throw away

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

On 06/12/2017 01:34 PM, Michael S. Tsirkin wrote: > On Mon, Jun 12, 2017 at 09:42:36AM -0700, Dave Hansen wrote: >> On 06/12/2017 09:28 AM, Michael S. Tsirkin wrote: >>> The hypervisor is going to throw away the contents of these pages, right? >>> It should be careful and only throw away

Re: [PATCH 2/3] dt-bindings: Add Broadcom STB USB PHY binding document

On Mon, Jun 12, 2017 at 4:19 PM, Al Cooper wrote: > On Thu, Jun 8, 2017 at 6:11 PM, Rob Herring wrote: >>> +- brcm,device: String, PHY Device mode. >>> + Possible values are: off (Host), on (Device), dual (DRD) >>> + or typec-pd (Type-C PD control) >>

[RESEND x3][PATCH v4] arm64: dts: hi6220: Add k3-dma and i2s/hdmi audio support

Add entry for k3-dma driver and i2s/hdmi audio devices. This enables HDMI audio output. Cc: Zhangfei Gao Cc: Liam Girdwood Cc: Mark Brown Cc: Jaroslav Kysela Cc: Takashi Iwai Cc: Wei Xu

Re: [PATCH 2/3] dt-bindings: Add Broadcom STB USB PHY binding document

On Mon, Jun 12, 2017 at 4:19 PM, Al Cooper wrote: > On Thu, Jun 8, 2017 at 6:11 PM, Rob Herring wrote: >>> +- brcm,device: String, PHY Device mode. >>> + Possible values are: off (Host), on (Device), dual (DRD) >>> + or typec-pd (Type-C PD control) >> >> I believe we have standard property for

[RESEND x3][PATCH v4] arm64: dts: hi6220: Add k3-dma and i2s/hdmi audio support

Add entry for k3-dma driver and i2s/hdmi audio devices. This enables HDMI audio output. Cc: Zhangfei Gao Cc: Liam Girdwood Cc: Mark Brown Cc: Jaroslav Kysela Cc: Takashi Iwai Cc: Wei Xu Cc: Rob Herring Cc: Andy Green Cc: Dave Long Cc: Guodong Xu Cc: Antonio Borneo Cc: Olof Johansson

Re: [PATCH 2/2] include: warn for inconsistent endian config definition

On Mon, Jun 12, 2017 at 10:30 PM, Babu Moger wrote: > > Looks like microblaze can be configured to either little or big endian > formats. How about > adding a choice statement to address this. > Here is my proposed patch. Hi Babu, This part looks fine, but I think we

Re: [PATCH 2/2] include: warn for inconsistent endian config definition

On Mon, Jun 12, 2017 at 10:30 PM, Babu Moger wrote: > > Looks like microblaze can be configured to either little or big endian > formats. How about > adding a choice statement to address this. > Here is my proposed patch. Hi Babu, This part looks fine, but I think we also need this one: diff

Re: [PATCH] arm64/dma-mapping: Fix null-pointer check

On 17-06-12 13:29:04, Catalin Marinas wrote: > On Sat, Jun 10, 2017 at 12:41:10PM -0700, Olav Haugan wrote: > > @@ -149,6 +140,11 @@ static void *__dma_alloc(struct device *dev, size_t > > size, > > bool coherent = is_device_dma_coherent(dev); > > pgprot_t prot = __get_dma_pgprot(attrs,

Re: [PATCH 1/3] scsi:ufs:add AHIT for hi3660 ufs

On 2017-06-09 18:20, butao wrote: add Auto-Hibernate Idle Timer value for hi3660 ufs Signed-off-by: Bu Tao Signed-off-by: Geng Jianfeng Signed-off-by: Zang Leigang Signed-off-by: Yu Jianfeng

Re: [PATCH] arm64/dma-mapping: Fix null-pointer check

On 17-06-12 13:29:04, Catalin Marinas wrote: > On Sat, Jun 10, 2017 at 12:41:10PM -0700, Olav Haugan wrote: > > @@ -149,6 +140,11 @@ static void *__dma_alloc(struct device *dev, size_t > > size, > > bool coherent = is_device_dma_coherent(dev); > > pgprot_t prot = __get_dma_pgprot(attrs,

Re: [PATCH 1/3] scsi:ufs:add AHIT for hi3660 ufs

On 2017-06-09 18:20, butao wrote: add Auto-Hibernate Idle Timer value for hi3660 ufs Signed-off-by: Bu Tao Signed-off-by: Geng Jianfeng Signed-off-by: Zang Leigang Signed-off-by: Yu Jianfeng --- drivers/scsi/ufs/ufshci.h | 3 +++ 1 file changed, 3 insertions(+) mode change 100644 =>

Re: [PATCH] pci: endpoint: fix endpoint test build error

On Sun, Jun 11, 2017 at 07:10:38PM -0700, Randy Dunlap wrote: > From: Randy Dunlap > > PCI endpoint test driver uses crc32_le() so it should select > CRC32. Fixes this build error (when CRC32=m): > > drivers/built-in.o: In function `pci_epf_test_cmd_handler': >

Re: [PATCH] pci: endpoint: fix endpoint test build error

On Sun, Jun 11, 2017 at 07:10:38PM -0700, Randy Dunlap wrote: > From: Randy Dunlap > > PCI endpoint test driver uses crc32_le() so it should select > CRC32. Fixes this build error (when CRC32=m): > > drivers/built-in.o: In function `pci_epf_test_cmd_handler': >

Re: [PATCH 3/4] watchdog: Split up config options

On Mon, Jun 12, 2017 at 06:07:39PM +1000, Nicholas Piggin wrote: > > > This would probably be the right direction to go in, but it will take > > > slightly more I think. We first need to remove HAVE_NMI_WATCHDOG from > > > meaning that an arch has its own watchdog and does not want any HLD > > >

Re: [PATCH 3/4] watchdog: Split up config options

On Mon, Jun 12, 2017 at 06:07:39PM +1000, Nicholas Piggin wrote: > > > This would probably be the right direction to go in, but it will take > > > slightly more I think. We first need to remove HAVE_NMI_WATCHDOG from > > > meaning that an arch has its own watchdog and does not want any HLD > > >

Re: udf: allow implicit blocksize specification during mount

Hi! I found that following UDF patch was included into linus tree: https://patchwork.kernel.org/patch/9524557/ It is really a good improvement to recognize UDF file system which have block size different from disk sector size and also different from 2048. But should not detection on 4K native

Re: udf: allow implicit blocksize specification during mount

Hi! I found that following UDF patch was included into linus tree: https://patchwork.kernel.org/patch/9524557/ It is really a good improvement to recognize UDF file system which have block size different from disk sector size and also different from 2048. But should not detection on 4K native

Re: [PATCH v5 3/3] drivers:power:twl4030-charger: add deferred probing for phy and iio

Hi, >> >>> As for me it more reasonable to move forward using smaller steps. >> >> Well, I wonder what it does help to fix a bug which does not even become >> visible >> if we don't add EPROBE_DEFER? > > Sry, but have you tried test I've proposed (I can't try it by myself now, > sry)? No

Re: [PATCH v5 3/3] drivers:power:twl4030-charger: add deferred probing for phy and iio

Hi, >> >>> As for me it more reasonable to move forward using smaller steps. >> >> Well, I wonder what it does help to fix a bug which does not even become >> visible >> if we don't add EPROBE_DEFER? > > Sry, but have you tried test I've proposed (I can't try it by myself now, > sry)? No

Re: [RFC PATCH v3 09/11] [media] vimc: Subdevices as modules

Hi Hans, Thank you for your review. Please check my comments below On 2017-06-12 07:37 AM, Hans Verkuil wrote: On 06/03/2017 04:58 AM, Helen Koike wrote: Change the core structure for adding subdevices in the topology. Instead of calling the specific create function for each subdevice, inject

Re: [PATCH] arm64/dma-mapping: Fix null-pointer check

On 17-06-10 23:03:54, Russell King - ARM Linux wrote: > On Sat, Jun 10, 2017 at 12:41:10PM -0700, Olav Haugan wrote: > > @@ -149,6 +140,11 @@ static void *__dma_alloc(struct device *dev, size_t > > size, > > bool coherent = is_device_dma_coherent(dev); >

Re: [RFC PATCH v3 09/11] [media] vimc: Subdevices as modules

Hi Hans, Thank you for your review. Please check my comments below On 2017-06-12 07:37 AM, Hans Verkuil wrote: On 06/03/2017 04:58 AM, Helen Koike wrote: Change the core structure for adding subdevices in the topology. Instead of calling the specific create function for each subdevice, inject

Re: [PATCH] arm64/dma-mapping: Fix null-pointer check

On 17-06-10 23:03:54, Russell King - ARM Linux wrote: > On Sat, Jun 10, 2017 at 12:41:10PM -0700, Olav Haugan wrote: > > @@ -149,6 +140,11 @@ static void *__dma_alloc(struct device *dev, size_t > > size, > > bool coherent = is_device_dma_coherent(dev); >

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

On Mon, Jun 12, 2017 at 09:42:36AM -0700, Dave Hansen wrote: > On 06/12/2017 09:28 AM, Michael S. Tsirkin wrote: > > > >> The hypervisor is going to throw away the contents of these pages, > >> right? > > It should be careful and only throw away contents that was there before > >

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

On Mon, Jun 12, 2017 at 09:42:36AM -0700, Dave Hansen wrote: > On 06/12/2017 09:28 AM, Michael S. Tsirkin wrote: > > > >> The hypervisor is going to throw away the contents of these pages, > >> right? > > It should be careful and only throw away contents that was there before > >

Re: [PATCH] arm64/dma-mapping: Fix null-pointer check

On 17-06-12 13:29:04, Catalin Marinas wrote: > On Sat, Jun 10, 2017 at 12:41:10PM -0700, Olav Haugan wrote: > > @@ -149,6 +140,11 @@ static void *__dma_alloc(struct device *dev, size_t > > size, > > bool coherent = is_device_dma_coherent(dev); > > pgprot_t prot = __get_dma_pgprot(attrs,

Re: [PATCH] arm64/dma-mapping: Fix null-pointer check

On 17-06-12 13:29:04, Catalin Marinas wrote: > On Sat, Jun 10, 2017 at 12:41:10PM -0700, Olav Haugan wrote: > > @@ -149,6 +140,11 @@ static void *__dma_alloc(struct device *dev, size_t > > size, > > bool coherent = is_device_dma_coherent(dev); > > pgprot_t prot = __get_dma_pgprot(attrs,

Re: [PATCH 2/2] include: warn for inconsistent endian config definition

Hi All, On 6/10/2017 9:06 AM, kbuild test robot wrote: Hi Babu, [auto build test WARNING on linus/master] [also build test WARNING on v4.12-rc4 next-20170609] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 2/2] include: warn for inconsistent endian config definition

Hi All, On 6/10/2017 9:06 AM, kbuild test robot wrote: Hi Babu, [auto build test WARNING on linus/master] [also build test WARNING on v4.12-rc4 next-20170609] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v1 2/2] selftests: kselftest_harness: Fix compile warning

On 06/11/2017 08:22 PM, Kees Cook wrote: > On Sun, Jun 11, 2017 at 5:32 AM, Mickaël Salaün wrote: >> Do not confuse the compiler with a semicolon preceding a block. Replace >> the semicolon with an empty block to avoid a warning: >> >> gcc -Wl,-no-as-needed -Wall -lpthread

Re: [PATCH v1 2/2] selftests: kselftest_harness: Fix compile warning

On 06/11/2017 08:22 PM, Kees Cook wrote: > On Sun, Jun 11, 2017 at 5:32 AM, Mickaël Salaün wrote: >> Do not confuse the compiler with a semicolon preceding a block. Replace >> the semicolon with an empty block to avoid a warning: >> >> gcc -Wl,-no-as-needed -Wall -lpthread seccomp_bpf.c -o >>

Re: usb/gadget: potential deadlock in gadgetfs_suspend

On Mon, 12 Jun 2017, Andrey Konovalov wrote: > Aha, got KASAN report: > > == > BUG: KASAN: use-after-free in __lock_acquire+0x3069/0x3690 > kernel/locking/lockdep.c:3246 > Read of size 8 at addr 88003a2bdaf8 by task

Re: usb/gadget: potential deadlock in gadgetfs_suspend

On Mon, 12 Jun 2017, Andrey Konovalov wrote: > Aha, got KASAN report: > > == > BUG: KASAN: use-after-free in __lock_acquire+0x3069/0x3690 > kernel/locking/lockdep.c:3246 > Read of size 8 at addr 88003a2bdaf8 by task

Re: [PATCH] drivers/watchdog: Add sys files to modify watchdog behavior

On 6/1/17 5:03 PM, Guenter Roeck wrote: On Thu, Jun 01, 2017 at 04:35:21PM -0500, Christopher Bostic wrote: Add files to enable/disable Aspeed watchdog: * External signal after timeout * Reset system after timeout The subject line is heavily misleading. Signed-off-by: Christopher Bostic

Re: [PATCH] drivers/watchdog: Add sys files to modify watchdog behavior

On 6/1/17 5:03 PM, Guenter Roeck wrote: On Thu, Jun 01, 2017 at 04:35:21PM -0500, Christopher Bostic wrote: Add files to enable/disable Aspeed watchdog: * External signal after timeout * Reset system after timeout The subject line is heavily misleading. Signed-off-by: Christopher Bostic

[PATCH v1 2/2] ptp: Add a ptp clock driver for Broadcom DTE

This patch adds a ptp clock driver for the Broadcom SoCs using the Digital timing Engine (DTE) nco. Signed-off-by: Arun Parameswaran --- drivers/ptp/Kconfig | 16 +++ drivers/ptp/Makefile | 1 + drivers/ptp/ptp_dte.c | 353

Re: [PATCH] staging: lustre: headers: potential UAPI headers

Greg said to go ahead... I think you misread something. We've all agreed to move the uapi directories into a separate dir and later we can discuss if it should be one enormous file or 12 huge files. regards, dan carpenter

[PATCH v1 0/2] Add support for Broadcom DTE based PTP clock

Hi, This patchset adds support for the DTE based PTP clock for Broadcom SoCs. The DTE nco based PTP clock can be used in both wired and wireless networks for precision time-stmaping purposes. Arun Parameswaran (2): dt-binding: ptp: add bindings document for dte based ptp clock ptp: Add a

[PATCH v1 1/2] dt-binding: ptp: add bindings document for dte based ptp clock

Add device tree binding documentation for the Broadcom DTE PTP clock driver. Signed-off-by: Arun Parameswaran --- Documentation/devicetree/bindings/ptp/brcm,ptp-dte.txt | 13 + 1 file changed, 13 insertions(+) create mode 100644

Re: [PATCH] staging: lustre: headers: potential UAPI headers

Greg said to go ahead... I think you misread something. We've all agreed to move the uapi directories into a separate dir and later we can discuss if it should be one enormous file or 12 huge files. regards, dan carpenter

[PATCH v1 0/2] Add support for Broadcom DTE based PTP clock

Hi, This patchset adds support for the DTE based PTP clock for Broadcom SoCs. The DTE nco based PTP clock can be used in both wired and wireless networks for precision time-stmaping purposes. Arun Parameswaran (2): dt-binding: ptp: add bindings document for dte based ptp clock ptp: Add a

[PATCH v1 1/2] dt-binding: ptp: add bindings document for dte based ptp clock

Add device tree binding documentation for the Broadcom DTE PTP clock driver. Signed-off-by: Arun Parameswaran --- Documentation/devicetree/bindings/ptp/brcm,ptp-dte.txt | 13 + 1 file changed, 13 insertions(+) create mode 100644

[PATCH v1 2/2] ptp: Add a ptp clock driver for Broadcom DTE

This patch adds a ptp clock driver for the Broadcom SoCs using the Digital timing Engine (DTE) nco. Signed-off-by: Arun Parameswaran --- drivers/ptp/Kconfig | 16 +++ drivers/ptp/Makefile | 1 + drivers/ptp/ptp_dte.c | 353 ++ 3 files

Re: [PATCH] staging: lustre: headers: potential UAPI headers

On Jan 21, 2017, at 02:24, Greg Kroah-Hartman wrote: > > On Fri, Jan 20, 2017 at 11:33:11PM +, James Simmons wrote: >> > On Mon, Dec 19, 2016 at 12:06:47PM -0500, James Simmons wrote: >> Not for landing. This is the purposed UAPI headers >> with the

Re: [PATCH] staging: lustre: headers: potential UAPI headers

On Jan 21, 2017, at 02:24, Greg Kroah-Hartman wrote: > > On Fri, Jan 20, 2017 at 11:33:11PM +, James Simmons wrote: >> > On Mon, Dec 19, 2016 at 12:06:47PM -0500, James Simmons wrote: >> Not for landing. This is the purposed UAPI headers >> with the removal of unlikely and

Re: [PATCH] libnvdimm, pmem: Add sysfs notifications to badblocks

On Mon, 2017-06-12 at 10:42 -0600, Toshi Kani wrote: > Sysfs "badblocks" information may be updated during run-time via > MCE, SCI, and sysfs "scrub". > > Add support to send sysfs notifications to sysfs "badblocks" file > under region and pmem directories when their badblocks information > is

Re: [PATCH 2/3] dt-bindings: Add Broadcom STB USB PHY binding document

On Thu, Jun 8, 2017 at 6:11 PM, Rob Herring wrote: >> +- brcm,device: String, PHY Device mode. >> + Possible values are: off (Host), on (Device), dual (DRD) >> + or typec-pd (Type-C PD control) > > I believe we have standard property for this though maybe not type C. > > off/on

Re: [PATCH] libnvdimm, pmem: Add sysfs notifications to badblocks

On Mon, 2017-06-12 at 10:42 -0600, Toshi Kani wrote: > Sysfs "badblocks" information may be updated during run-time via > MCE, SCI, and sysfs "scrub". > > Add support to send sysfs notifications to sysfs "badblocks" file > under region and pmem directories when their badblocks information > is

Re: [PATCH 2/3] dt-bindings: Add Broadcom STB USB PHY binding document

On Thu, Jun 8, 2017 at 6:11 PM, Rob Herring wrote: >> +- brcm,device: String, PHY Device mode. >> + Possible values are: off (Host), on (Device), dual (DRD) >> + or typec-pd (Type-C PD control) > > I believe we have standard property for this though maybe not type C. > > off/on seem strange for

Re: [PATCH] staging: wlan-ng: Amend type mismatch warnings

No, sorry. This doesn't look right at all. regards, dan carpenter

Re: [PATCH] staging: wlan-ng: Amend type mismatch warnings

No, sorry. This doesn't look right at all. regards, dan carpenter

Ftrace vs perf user page fault statistics differences

Dear Mr. Rostedt and Kernel community, I hope that this is an appropriate place to ask this question, Please forgive me for wasting your time if it is not. I've searched for answers to this question on LKML and the "net" before asking. I apologize if I already missed the question and answer

Ftrace vs perf user page fault statistics differences

Dear Mr. Rostedt and Kernel community, I hope that this is an appropriate place to ask this question, Please forgive me for wasting your time if it is not. I've searched for answers to this question on LKML and the "net" before asking. I apologize if I already missed the question and answer

Re: [PATCH 0/6] {sched_,}find_first{_zero}_bit optimizations

Ping again. Is there still any interest in the patchset? Arnd, Ingo? On Fri, Jun 02, 2017 at 02:34:43PM +0300, Yury Norov wrote: > Ping? > > On Tue, May 23, 2017 at 09:43:15PM +0300, Yury Norov wrote: > > The series is the result of this discussion: > > https://lkml.org/lkml/2017/5/12/665 > >

Re: [PATCH 0/6] {sched_,}find_first{_zero}_bit optimizations

Ping again. Is there still any interest in the patchset? Arnd, Ingo? On Fri, Jun 02, 2017 at 02:34:43PM +0300, Yury Norov wrote: > Ping? > > On Tue, May 23, 2017 at 09:43:15PM +0300, Yury Norov wrote: > > The series is the result of this discussion: > > https://lkml.org/lkml/2017/5/12/665 > >

[PATCH] staging: fsl-mc: fix misspelled comment identified by checkpatch

Signed-off-by: Gabriel Somlo --- drivers/staging/fsl-mc/bus/dpio/dpio-service.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/fsl-mc/bus/dpio/dpio-service.c b/drivers/staging/fsl-mc/bus/dpio/dpio-service.c index e5d6674..8c45f81 100644 ---

[PATCH] staging: fsl-mc: fix misspelled comment identified by checkpatch

Signed-off-by: Gabriel Somlo --- drivers/staging/fsl-mc/bus/dpio/dpio-service.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/fsl-mc/bus/dpio/dpio-service.c b/drivers/staging/fsl-mc/bus/dpio/dpio-service.c index e5d6674..8c45f81 100644 ---

Re: [PATCH 03/11] Creation of "usb_device_auth" LSM hook

On Mon, Jun 12, 2017 at 06:56:52PM +0200, Salvatore Mesoraca wrote: > Creation of a new LSM hook that can be used to authorize or deauthorize > new USB devices via the usb authorization interface. > The same hook can also prevent the authorization of a USB device via >

Re: [PATCH 03/11] Creation of "usb_device_auth" LSM hook

On Mon, Jun 12, 2017 at 06:56:52PM +0200, Salvatore Mesoraca wrote: > Creation of a new LSM hook that can be used to authorize or deauthorize > new USB devices via the usb authorization interface. > The same hook can also prevent the authorization of a USB device via >

Re: [PATCH] libata: Convert bare printks to pr_cont

On Mon, Jun 12, 2017 at 12:17:39PM -0700, Joe Perches wrote: > Linus Torvalds changed the behavior of printks without KERN_. > > Convert the continuation prints to use pr_cont. > > At the same time, convert the existing printks with KERN_ to > pr_ > > Miscellanea: > > o Coalesce a multiline

Re: [PATCH] libata: Convert bare printks to pr_cont

On Mon, Jun 12, 2017 at 12:17:39PM -0700, Joe Perches wrote: > Linus Torvalds changed the behavior of printks without KERN_. > > Convert the continuation prints to use pr_cont. > > At the same time, convert the existing printks with KERN_ to > pr_ > > Miscellanea: > > o Coalesce a multiline

[tip:x86/urgent] x86/debug: Handle early WARN_ONs proper

Commit-ID: 8a524f803a3e0290cdba6d373361b2cef9752934 Gitweb: http://git.kernel.org/tip/8a524f803a3e0290cdba6d373361b2cef9752934 Author: Peter Zijlstra AuthorDate: Mon, 12 Jun 2017 13:52:46 +0200 Committer: Thomas Gleixner CommitDate: Mon, 12 Jun

[tip:x86/urgent] x86/debug: Handle early WARN_ONs proper

Commit-ID: 8a524f803a3e0290cdba6d373361b2cef9752934 Gitweb: http://git.kernel.org/tip/8a524f803a3e0290cdba6d373361b2cef9752934 Author: Peter Zijlstra AuthorDate: Mon, 12 Jun 2017 13:52:46 +0200 Committer: Thomas Gleixner CommitDate: Mon, 12 Jun 2017 21:17:48 +0200 x86/debug: Handle

Re: [RFC PATCH v3 08/11] [media] vimc: Optimize frame generation through the pipe

Hi Hans, Thank you for your review On 2017-06-12 07:03 AM, Hans Verkuil wrote: On 06/03/2017 04:58 AM, Helen Koike wrote: Add a parameter called vsen_tpg, if true then vimc will work as before: frames will be generated in the sensor nodes then propagated through the pipe and processed by each

Re: [RFC PATCH v3 08/11] [media] vimc: Optimize frame generation through the pipe

Hi Hans, Thank you for your review On 2017-06-12 07:03 AM, Hans Verkuil wrote: On 06/03/2017 04:58 AM, Helen Koike wrote: Add a parameter called vsen_tpg, if true then vimc will work as before: frames will be generated in the sensor nodes then propagated through the pipe and processed by each

Re: [net v1 PATCH] hsr: fix incorrect warning

From: Murali Karicheri Date: Mon, 12 Jun 2017 15:06:26 -0400 > When HSR interface is setup using ip link command, an annoying warning > appears with the trace as below:- > > [ 203.019828] hsr_get_node: Non-HSR frame > [ 203.019833] Modules linked in: > [ 203.019848] CPU:

Re: [net v1 PATCH] hsr: fix incorrect warning

From: Murali Karicheri Date: Mon, 12 Jun 2017 15:06:26 -0400 > When HSR interface is setup using ip link command, an annoying warning > appears with the trace as below:- > > [ 203.019828] hsr_get_node: Non-HSR frame > [ 203.019833] Modules linked in: > [ 203.019848] CPU: 0 PID: 158 Comm:

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