[PATCH] ARM: dts: bcm283x: Move the BCM2837 DT contents from arm64 to arm.

BCM2837 is somewhat unusual in that we build its DT on both arm32 and arm64. Most devices are being run in arm32 mode. Having the body of the DT for 2837 separate from 2835/6 has been a source of pain, as we often need to make changes that span both directories simultaneously (for example, the

[PATCH] ARM: dts: bcm283x: Move the BCM2837 DT contents from arm64 to arm.

BCM2837 is somewhat unusual in that we build its DT on both arm32 and arm64. Most devices are being run in arm32 mode. Having the body of the DT for 2837 separate from 2835/6 has been a source of pain, as we often need to make changes that span both directories simultaneously (for example, the

RE: [PATCH v1 4/6] vmbus: Switch to use new generic UUID API

> -Original Message- > From: Andy Shevchenko [mailto:andriy.shevche...@linux.intel.com] > Sent: Wednesday, July 19, 2017 2:29 PM > To: linux-a...@vger.kernel.org; de...@linuxdriverproject.org; > sparmaintai...@unisys.com; de...@driverdev.osuosl.org; linux- > wirel...@vger.kernel.org;

RE: [PATCH v1 4/6] vmbus: Switch to use new generic UUID API

> -Original Message- > From: Andy Shevchenko [mailto:andriy.shevche...@linux.intel.com] > Sent: Wednesday, July 19, 2017 2:29 PM > To: linux-a...@vger.kernel.org; de...@linuxdriverproject.org; > sparmaintai...@unisys.com; de...@driverdev.osuosl.org; linux- > wirel...@vger.kernel.org;

Re: [PATCH 3/3] ghes_edac: add platform check to enable ghes_edac

On Wed, 2017-07-19 at 14:55 -0400, Aristeu Rozanski wrote: > On Wed, Jul 19, 2017 at 06:22:04PM +0200, Borislav Petkov wrote: > > On Wed, Jul 19, 2017 at 04:10:07PM +, Kani, Toshimitsu wrote: > > > I do prefer to avoid any white / black listing.  But I do not see > > > how > > > it solves the

Re: [PATCH 3/3] ghes_edac: add platform check to enable ghes_edac

On Wed, 2017-07-19 at 14:55 -0400, Aristeu Rozanski wrote: > On Wed, Jul 19, 2017 at 06:22:04PM +0200, Borislav Petkov wrote: > > On Wed, Jul 19, 2017 at 04:10:07PM +, Kani, Toshimitsu wrote: > > > I do prefer to avoid any white / black listing.  But I do not see > > > how > > > it solves the

Re: [PATCH] MAINTAINERS: update mailing list name for Hyper-V files

On Wed, Jul 19, 2017 at 12:38:11PM -0700, Haiyang Zhang wrote: > From: Haiyang Zhang > > "de...@linuxdriverproject.org" is an outdated name, this patch > updates it to the current mailing list name of the Linux > Driver project. > > Signed-off-by: Haiyang Zhang

Re: [PATCH] MAINTAINERS: update mailing list name for Hyper-V files

On Wed, Jul 19, 2017 at 12:38:11PM -0700, Haiyang Zhang wrote: > From: Haiyang Zhang > > "de...@linuxdriverproject.org" is an outdated name, this patch > updates it to the current mailing list name of the Linux > Driver project. > > Signed-off-by: Haiyang Zhang > --- > MAINTAINERS |2 +- >

[PATCH v4 1/2] wire: export w1_touch_bit

The w1_ds28e17 driver from the next part of this patch needs to emit single-bit read timeslots to the DS28E17. The w1 subsystem already has this function but it is not exported outside drivers/w1/w1_io.c This subpatch exports the w1_touch_bit symbol with EXPORT_SYMBOL_GPL, same as the other

[PATCH v4 2/2] add w1_ds28e17 driver for the DS28E17 Onewire to I2C master bridge

This subpatch adds a driver for the DS28E17 Onewire to I2C master bridge. Signed-off-by: Jan Kandziora --- Changes in v4 against v3 in this subpatch: - adapted to linux-4.12.0 Changes in v3 against v2 in this subpatch: - fixed a bug in using the i2c_adapter_quirks structure

[PATCH v4 1/2] wire: export w1_touch_bit

The w1_ds28e17 driver from the next part of this patch needs to emit single-bit read timeslots to the DS28E17. The w1 subsystem already has this function but it is not exported outside drivers/w1/w1_io.c This subpatch exports the w1_touch_bit symbol with EXPORT_SYMBOL_GPL, same as the other

[PATCH v4 2/2] add w1_ds28e17 driver for the DS28E17 Onewire to I2C master bridge

This subpatch adds a driver for the DS28E17 Onewire to I2C master bridge. Signed-off-by: Jan Kandziora --- Changes in v4 against v3 in this subpatch: - adapted to linux-4.12.0 Changes in v3 against v2 in this subpatch: - fixed a bug in using the i2c_adapter_quirks structure Changes in v2

Re: [Nouveau] [PATCH] drm: disable vblank only if it got previously enabled

I believe the solution is to not call drm_crtc_vblank_off for atomic modesetting in nouveau_display_fini. I think Ben's working on it. On Wed, Jul 19, 2017 at 1:25 PM, Tobias Klausmann wrote: > mimic the behavior of vblank_disable_fn(), another caller of >

Re: [Nouveau] [PATCH] drm: disable vblank only if it got previously enabled

I believe the solution is to not call drm_crtc_vblank_off for atomic modesetting in nouveau_display_fini. I think Ben's working on it. On Wed, Jul 19, 2017 at 1:25 PM, Tobias Klausmann wrote: > mimic the behavior of vblank_disable_fn(), another caller of > drm_vblank_disable_and_save(). > > This

Re: [PATCH 0/1] acpi: apei: Enable APEI multiple GHES source to share an single external IRQ

On Wed, 2017-07-19 at 21:23 +0200, Rafael J. Wysocki wrote: > On Wed, Jul 19, 2017 at 7:24 PM, Mark Salter wrote: > > Rafael, > > > > What do you think of this one? > > Please ask this question to Boris Petkov in the first place. Yes, I should have included Boris. The last

Re: [PATCH 0/1] acpi: apei: Enable APEI multiple GHES source to share an single external IRQ

On Wed, 2017-07-19 at 21:23 +0200, Rafael J. Wysocki wrote: > On Wed, Jul 19, 2017 at 7:24 PM, Mark Salter wrote: > > Rafael, > > > > What do you think of this one? > > Please ask this question to Boris Petkov in the first place. Yes, I should have included Boris. The last time this came up,

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

Hi Rob, Thank you for the patch. On Tuesday 18 Jul 2017 16:43:04 Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob

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

Hi Rob, Thank you for the patch. On Tuesday 18 Jul 2017 16:43:04 Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob

Re: [PATCH v6 2/2] x86/refcount: Implement fast refcount overflow protection

On Wed, Jul 19, 2017 at 12:45:19PM -0700, Kees Cook wrote: > > diff --git a/arch/x86/include/asm/refcount.h > > b/arch/x86/include/asm/refcount.h > > index 13b91e850a02..e7587db3487c 100644 > > --- a/arch/x86/include/asm/refcount.h > > +++ b/arch/x86/include/asm/refcount.h > > @@ -15,6 +15,7 @@ >

Re: [PATCH v6 2/2] x86/refcount: Implement fast refcount overflow protection

On Wed, Jul 19, 2017 at 12:45:19PM -0700, Kees Cook wrote: > > diff --git a/arch/x86/include/asm/refcount.h > > b/arch/x86/include/asm/refcount.h > > index 13b91e850a02..e7587db3487c 100644 > > --- a/arch/x86/include/asm/refcount.h > > +++ b/arch/x86/include/asm/refcount.h > > @@ -15,6 +15,7 @@ >

Re: [PATCH 2/3][staging-next] staging: pi433: Make functions rf69_set_bandwidth_intern static

Hi Colin, thanks for your patches. #1 is fine. Same fix was provided by Joseph Wright. I tested it and it works fine. #2 looks fine, too. Conerning #3, I would suggest to declare rf69_set_dc_cut_off_frequency static, as well. Would you prefer to remove rf69_set_dc_cut_off_frequency from the

Re: [PATCH 2/3][staging-next] staging: pi433: Make functions rf69_set_bandwidth_intern static

Hi Colin, thanks for your patches. #1 is fine. Same fix was provided by Joseph Wright. I tested it and it works fine. #2 looks fine, too. Conerning #3, I would suggest to declare rf69_set_dc_cut_off_frequency static, as well. Would you prefer to remove rf69_set_dc_cut_off_frequency from the

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

Rob Herring writes: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. For bcm283x: Acked-by: Eric Anholt signature.asc

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

Rob Herring writes: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. For bcm283x: Acked-by: Eric Anholt signature.asc Description: PGP signature

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

Rob Herring writes: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > For bcm283x: Acked-by: Eric Anholt signature.asc

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

Rob Herring writes: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > For bcm283x: Acked-by: Eric Anholt signature.asc Description: PGP signature

[PATCH 4/4] time: rtc-lib: Add CONFIG_RTC_SHOW_TIME_RTC

Add an option to report REALTIME in RTC time format for rtc_show_time() function. Feature activated by CONFIG_RTC_SHOW_TIME_RTC. Signed-off-by: Mark Salyzyn --- kernel/time/Kconfig | 17 + kernel/time/rtc_show_time.c | 12 2 files

[PATCH 4/4] time: rtc-lib: Add CONFIG_RTC_SHOW_TIME_RTC

Add an option to report REALTIME in RTC time format for rtc_show_time() function. Feature activated by CONFIG_RTC_SHOW_TIME_RTC. Signed-off-by: Mark Salyzyn --- kernel/time/Kconfig | 17 + kernel/time/rtc_show_time.c | 12 2 files changed, 29 insertions(+)

[PATCH v2 3/4] PM: Print wall time at suspend & hibernate entry and exit

Permits power state and battery life diagnosis. Since one is not guaranteed to have a persistent hardware clock to report Suspended for in milliseconds, we report at a higher level at just the entry and exit points for suspend and hibernate. Feature activated by CONFIG_RTC_SHOW_TIME_*

[PATCH v2 3/4] PM: Print wall time at suspend & hibernate entry and exit

Permits power state and battery life diagnosis. Since one is not guaranteed to have a persistent hardware clock to report Suspended for in milliseconds, we report at a higher level at just the entry and exit points for suspend and hibernate. Feature activated by CONFIG_RTC_SHOW_TIME_*

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

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

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

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

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

On 07/18/2017 02:42 PM, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc: Benjamin

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

On 07/18/2017 02:42 PM, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc: Benjamin Herrenschmidt > Cc: Paul

[PATCH 3/6] cgroup: introduce cgroup->dom_cgrp and threaded css_set handling

cgroup v2 is in the process of growing thread granularity support. A threaded subtree is composed of a thread root and threaded cgroups which are proper members of the subtree. The root cgroup of the subtree serves as the domain cgroup to which the processes (as opposed to threads / tasks) of

[PATCH 3/6] cgroup: introduce cgroup->dom_cgrp and threaded css_set handling

cgroup v2 is in the process of growing thread granularity support. A threaded subtree is composed of a thread root and threaded cgroups which are proper members of the subtree. The root cgroup of the subtree serves as the domain cgroup to which the processes (as opposed to threads / tasks) of

[PATCH 2/6] cgroup: add @flags to css_task_iter_start() and implement CSS_TASK_ITER_PROCS

css_task_iter currently always walks all tasks. With the scheduled cgroup v2 thread support, the iterator would need to handle multiple types of iteration. As a preparation, add @flags to css_task_iter_start() and implement CSS_TASK_ITER_PROCS. If the flag is not specified, it walks all tasks

[PATCH 2/6] cgroup: add @flags to css_task_iter_start() and implement CSS_TASK_ITER_PROCS

css_task_iter currently always walks all tasks. With the scheduled cgroup v2 thread support, the iterator would need to handle multiple types of iteration. As a preparation, add @flags to css_task_iter_start() and implement CSS_TASK_ITER_PROCS. If the flag is not specified, it walks all tasks

[PATCH 1/6] cgroup: reorganize cgroup.procs / task write path

Currently, writes "cgroup.procs" and "cgroup.tasks" files are all handled by __cgroup_procs_write() on both v1 and v2. This patch reoragnizes the write path so that there are common helper functions that different write paths use. While this somewhat increases LOC, the different paths are no

[PATCH 1/6] cgroup: reorganize cgroup.procs / task write path

Currently, writes "cgroup.procs" and "cgroup.tasks" files are all handled by __cgroup_procs_write() on both v1 and v2. This patch reoragnizes the write path so that there are common helper functions that different write paths use. While this somewhat increases LOC, the different paths are no

[PATCH v2 3/4] PM: Print wall time at suspend & hibernate entry and exit

Permits power state and battery life diagnosis. Since one is not guaranteed to have a persistent hardware clock to report Suspended for in milliseconds, we report at a higher level at just the entry and exit points for suspend and hibernate. Feature activated by CONFIG_RTC_SHOW_TIME_*

Re: [PATCH 4/8] x86: io: add "memory" clobber to insb/insw/insl/outsb/outsw/outsl

On Wed, Jul 19, 2017 at 5:53 AM, Arnd Bergmann wrote: > > I tried to mark the exact input buffer as an output here, but couldn't > figure it out. As suggested by Linus, marking all memory as clobbered > however is good enough too. For the outs operations, I also add the > memory

[PATCH v2 3/4] PM: Print wall time at suspend & hibernate entry and exit

Permits power state and battery life diagnosis. Since one is not guaranteed to have a persistent hardware clock to report Suspended for in milliseconds, we report at a higher level at just the entry and exit points for suspend and hibernate. Feature activated by CONFIG_RTC_SHOW_TIME_*

Re: [PATCH 4/8] x86: io: add "memory" clobber to insb/insw/insl/outsb/outsw/outsl

On Wed, Jul 19, 2017 at 5:53 AM, Arnd Bergmann wrote: > > I tried to mark the exact input buffer as an output here, but couldn't > figure it out. As suggested by Linus, marking all memory as clobbered > however is good enough too. For the outs operations, I also add the > memory clobber, to force

[PATCH v2 2/4] time: Print wall time at die and reboot

Permits power state and battery life diagnosis. Feature activated by CONFIG_RTC_SHOW_TIME. Signed-off-by: Mark Salyzyn v2: - react to implementation move to kernel timekeeping from rtc_lib - use late_initcall to ensure rtc_lib driver(s) are loaded ---

[PATCH 6/6] cgroup: update debug controller to print out thread mode information

From: Waiman Long Update debug controller so that it prints out debug info about thread mode. 1) The relationship between proc_cset and threaded_csets are displayed. 2) The status of being a thread root or threaded cgroup is displayed. This patch is extracted from

[PATCH v2 2/4] time: Print wall time at die and reboot

Permits power state and battery life diagnosis. Feature activated by CONFIG_RTC_SHOW_TIME. Signed-off-by: Mark Salyzyn v2: - react to implementation move to kernel timekeeping from rtc_lib - use late_initcall to ensure rtc_lib driver(s) are loaded --- kernel/time/rtc_show_time.c | 59

[PATCH 6/6] cgroup: update debug controller to print out thread mode information

From: Waiman Long Update debug controller so that it prints out debug info about thread mode. 1) The relationship between proc_cset and threaded_csets are displayed. 2) The status of being a thread root or threaded cgroup is displayed. This patch is extracted from Waiman's larger patch. v2:

[PATCH 4/6] cgroup: implement CSS_TASK_ITER_THREADED

cgroup v2 is in the process of growing thread granularity support. Once thread mode is enabled, the root cgroup of the subtree serves as the dom_cgrp to which the processes of the subtree conceptually belong and domain-level resource consumptions not tied to any specific task are charged. In the

[PATCH 4/6] cgroup: implement CSS_TASK_ITER_THREADED

cgroup v2 is in the process of growing thread granularity support. Once thread mode is enabled, the root cgroup of the subtree serves as the dom_cgrp to which the processes of the subtree conceptually belong and domain-level resource consumptions not tied to any specific task are charged. In the

Re: [PATCH v6 2/2] x86/refcount: Implement fast refcount overflow protection

On Wed, Jul 19, 2017 at 12:37 PM, Josh Poimboeuf wrote: > On Tue, Jul 18, 2017 at 05:03:34PM -0700, Kees Cook wrote: >> +/* >> + * Body of refcount error handling: in .text.unlikely, saved into CX the >> + * address of the refcount that has entered a bad state, and trigger an

Re: [PATCH v6 2/2] x86/refcount: Implement fast refcount overflow protection

On Wed, Jul 19, 2017 at 12:37 PM, Josh Poimboeuf wrote: > On Tue, Jul 18, 2017 at 05:03:34PM -0700, Kees Cook wrote: >> +/* >> + * Body of refcount error handling: in .text.unlikely, saved into CX the >> + * address of the refcount that has entered a bad state, and trigger an >> + * exception.

[PATCH v4 1/4] time: rtc-lib: Add rtc_show_time(const char *prefix_msg)

Primary purpose of rtc_show_time is to provide a marker used for post-mortem Battery and Power analysis. These markers occur at major discontinuities of time, and thus optionally add a timestamp to aid the analysis. This function is to be called at a higher level, and were added because of a

[PATCH v4 1/4] time: rtc-lib: Add rtc_show_time(const char *prefix_msg)

Primary purpose of rtc_show_time is to provide a marker used for post-mortem Battery and Power analysis. These markers occur at major discontinuities of time, and thus optionally add a timestamp to aid the analysis. This function is to be called at a higher level, and were added because of a

[PATCH 5/6] cgroup: implement cgroup v2 thread support

This patch implements cgroup v2 thread support. The goal of the thread mode is supporting hierarchical accounting and control at thread granularity while staying inside the resource domain model which allows coordination across different resource controllers and handling of anonymous resource

[PATCH 5/6] cgroup: implement cgroup v2 thread support

This patch implements cgroup v2 thread support. The goal of the thread mode is supporting hierarchical accounting and control at thread granularity while staying inside the resource domain model which allows coordination across different resource controllers and handling of anonymous resource

[PATCHSET for-4.13] cgroup: implement cgroup2 thread mode, v4

Hello, This is v4 of cgroup2 thread mode patchset. The changes from v3[L] are all fairly minor. Peter and Waiman are okay with the approach and I'll apply these patches to cgorup/for-4.14 unless there are further objections. Please speak up if there are any further concerns. * Documentation

[PATCHSET for-4.13] cgroup: implement cgroup2 thread mode, v4

Hello, This is v4 of cgroup2 thread mode patchset. The changes from v3[L] are all fairly minor. Peter and Waiman are okay with the approach and I'll apply these patches to cgorup/for-4.14 unless there are further objections. Please speak up if there are any further concerns. * Documentation

Re: [PATCH 2/2] Staging: pi433: check error after kthread_run()

Hi Joseph, tested your patch and didn't observe a problem. Thanks for your help :-) Marcus > Joseph Wright hat am 16. Juli 2017 um 16:48 > geschrieben: > > > Error should be checked with IS_ERR after calling kthread_run() > instead of comparing the returned pointer to

Re: [PATCH 2/2] Staging: pi433: check error after kthread_run()

Hi Joseph, tested your patch and didn't observe a problem. Thanks for your help :-) Marcus > Joseph Wright hat am 16. Juli 2017 um 16:48 > geschrieben: > > > Error should be checked with IS_ERR after calling kthread_run() > instead of comparing the returned pointer to an int. > > Found by

[PATCH] MAINTAINERS: update mailing list name for Hyper-V files

From: Haiyang Zhang "de...@linuxdriverproject.org" is an outdated name, this patch updates it to the current mailing list name of the Linux Driver project. Signed-off-by: Haiyang Zhang --- MAINTAINERS |2 +- 1 files changed, 1 insertions(+),

[PATCH] MAINTAINERS: update mailing list name for Hyper-V files

From: Haiyang Zhang "de...@linuxdriverproject.org" is an outdated name, this patch updates it to the current mailing list name of the Linux Driver project. Signed-off-by: Haiyang Zhang --- MAINTAINERS |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/MAINTAINERS

Re: [PATCH v2 12/25] dt-bindings: qcom_nandc: QPIC NAND documentation

On Wed, 19 Jul 2017 17:18:00 +0530 Abhishek Sahu wrote: > 1. QPIC NAND will use compatible string "qcom,qpic-nandc-v1.4.0" > 2. QPIC NAND will 3 BAM channels: command, data tx and data rx >while EBI2 NAND uses only single ADM channel. > 3. CRCI is only required for ADM

Re: [PATCH v2 12/25] dt-bindings: qcom_nandc: QPIC NAND documentation

On Wed, 19 Jul 2017 17:18:00 +0530 Abhishek Sahu wrote: > 1. QPIC NAND will use compatible string "qcom,qpic-nandc-v1.4.0" > 2. QPIC NAND will 3 BAM channels: command, data tx and data rx >while EBI2 NAND uses only single ADM channel. > 3. CRCI is only required for ADM DMA and its not

Re: [PATCH v6 2/2] x86/refcount: Implement fast refcount overflow protection

On Tue, Jul 18, 2017 at 05:03:34PM -0700, Kees Cook wrote: > +/* > + * Body of refcount error handling: in .text.unlikely, saved into CX the > + * address of the refcount that has entered a bad state, and trigger an > + * exception. Fixup address is back in regular execution flow in .text. > + */

Re: [PATCH v6 2/2] x86/refcount: Implement fast refcount overflow protection

On Tue, Jul 18, 2017 at 05:03:34PM -0700, Kees Cook wrote: > +/* > + * Body of refcount error handling: in .text.unlikely, saved into CX the > + * address of the refcount that has entered a bad state, and trigger an > + * exception. Fixup address is back in regular execution flow in .text. > + */

Re: [PATCH] mmc: core: Fix access to HS400-ES devices

On Wed, Jul 19, 2017 at 11:12:45AM -0700, Doug Anderson wrote: > Hi, > > On Tue, Mar 14, 2017 at 9:22 AM, Ulf Hansson wrote: > > On 1 March 2017 at 23:11, Guenter Roeck wrote: > >> HS400-ES devices fail to initialize with the following error messages.

Re: [PATCH] mmc: core: Fix access to HS400-ES devices

On Wed, Jul 19, 2017 at 11:12:45AM -0700, Doug Anderson wrote: > Hi, > > On Tue, Mar 14, 2017 at 9:22 AM, Ulf Hansson wrote: > > On 1 March 2017 at 23:11, Guenter Roeck wrote: > >> HS400-ES devices fail to initialize with the following error messages. > >> > >> mmc1: power class selection to

Re: [PATCH] libkmod-elf: resolve CRC if module is built with MODULE_REL_CRCS

Hi, Ard! > On Wed, 19 Jul 2017 20:10:17 +0100, Ard Biesheuvel wrote: > On 19 July 2017 at 20:04, Yauheni Kaliuta wrote: >> Hi, Lucas! >> >>> On Wed, 19 Jul 2017 10:51:44 -0700, Lucas De Marchi wrote: >> > On Wed, Jul 19, 2017 at 7:56 AM, Yauheni

Re: [PATCH] libkmod-elf: resolve CRC if module is built with MODULE_REL_CRCS

Hi, Ard! > On Wed, 19 Jul 2017 20:10:17 +0100, Ard Biesheuvel wrote: > On 19 July 2017 at 20:04, Yauheni Kaliuta wrote: >> Hi, Lucas! >> >>> On Wed, 19 Jul 2017 10:51:44 -0700, Lucas De Marchi wrote: >> > On Wed, Jul 19, 2017 at 7:56 AM, Yauheni Kaliuta >> > wrote: >> >>

Re: [PATCH v2] [media] fix warning on v4l2_subdev_call() result interpreted as bool

Looks good. regards, dan carpenter

Re: [PATCH v2] [media] fix warning on v4l2_subdev_call() result interpreted as bool

Looks good. regards, dan carpenter

Re: [PATCH v1 6/6] device property: Switch to use new generic UUID API

On Wed, Jul 19, 2017 at 8:28 PM, Andy Shevchenko wrote: > There are new types and helpers that are supposed to be used in new code. > > As a preparation to get rid of legacy types and API functions do > the conversion here. Please talk to Mika about this one.

Re: [PATCH v1 6/6] device property: Switch to use new generic UUID API

On Wed, Jul 19, 2017 at 8:28 PM, Andy Shevchenko wrote: > There are new types and helpers that are supposed to be used in new code. > > As a preparation to get rid of legacy types and API functions do > the conversion here. Please talk to Mika about this one. Thanks, Rafael

Re: [PATCH 4/8] x86: io: add "memory" clobber to insb/insw/insl/outsb/outsw/outsl

[adding Linus to Cc, apparently git send-email ignores the Suggested-by tag for the cc-list] On Wed, Jul 19, 2017 at 2:53 PM, Arnd Bergmann wrote: > The x86 version of insb/insw/insl uses an inline assembly that does > not have the target buffer listed as an output. This can

Re: [PATCH 4/8] x86: io: add "memory" clobber to insb/insw/insl/outsb/outsw/outsl

[adding Linus to Cc, apparently git send-email ignores the Suggested-by tag for the cc-list] On Wed, Jul 19, 2017 at 2:53 PM, Arnd Bergmann wrote: > The x86 version of insb/insw/insl uses an inline assembly that does > not have the target buffer listed as an output. This can confuse > the

[PATCH v2] [media] fix warning on v4l2_subdev_call() result interpreted as bool

v4l2_subdev_call is a macro returning whatever the callback return type is, usually 'int'. With gcc-7 and ccache, this can lead to many wanings like: media/platform/pxa_camera.c: In function 'pxa_mbus_build_fmts_xlate': media/platform/pxa_camera.c:766:27: error: ?: using integer constants in

[PATCH v2] [media] fix warning on v4l2_subdev_call() result interpreted as bool

v4l2_subdev_call is a macro returning whatever the callback return type is, usually 'int'. With gcc-7 and ccache, this can lead to many wanings like: media/platform/pxa_camera.c: In function 'pxa_mbus_build_fmts_xlate': media/platform/pxa_camera.c:766:27: error: ?: using integer constants in

Re: [PATCH 0/1] acpi: apei: Enable APEI multiple GHES source to share an single external IRQ

On Wed, Jul 19, 2017 at 7:24 PM, Mark Salter wrote: > Rafael, > > What do you think of this one? Please ask this question to Boris Petkov in the first place. > I was submitted a long time ago but > there was never any real resolution to it. > > > Loc Ho (1): > acpi: apei:

Re: [PATCH 0/1] acpi: apei: Enable APEI multiple GHES source to share an single external IRQ

On Wed, Jul 19, 2017 at 7:24 PM, Mark Salter wrote: > Rafael, > > What do you think of this one? Please ask this question to Boris Petkov in the first place. > I was submitted a long time ago but > there was never any real resolution to it. > > > Loc Ho (1): > acpi: apei: Enable APEI multiple

Re: [RFC][PATCH v3] drm: kirin: Add mode_valid logic to avoid mode clocks we can't generate

On Wed, Jul 19, 2017 at 3:16 AM, Jose Abreu wrote: > Hi John, > > > On 18-07-2017 18:59, John Stultz wrote: >> Currently the hikey dsi logic cannot generate accurate byte >> clocks values for all pixel clock values. Thus if a mode clock >> is selected that cannot match

Re: [PATCH v4] Bluetooth: btusb: Fix memory leak in play_deferred

Hi Jeffy, [auto build test WARNING on bluetooth-next/master] [also build test WARNING on v4.13-rc1 next-20170719] [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/Jeffy-Chen/Bluetooth-btusb-Fix

Re: [RFC][PATCH v3] drm: kirin: Add mode_valid logic to avoid mode clocks we can't generate

On Wed, Jul 19, 2017 at 3:16 AM, Jose Abreu wrote: > Hi John, > > > On 18-07-2017 18:59, John Stultz wrote: >> Currently the hikey dsi logic cannot generate accurate byte >> clocks values for all pixel clock values. Thus if a mode clock >> is selected that cannot match the calculated byte clock,

Re: [PATCH v4] Bluetooth: btusb: Fix memory leak in play_deferred

Hi Jeffy, [auto build test WARNING on bluetooth-next/master] [also build test WARNING on v4.13-rc1 next-20170719] [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/Jeffy-Chen/Bluetooth-btusb-Fix

[PATCH v3] ath10k: ath10k_htt_rx_amsdu_allowed() use ath10k_dbg()

Each time we get disconencted from AP we get flooded with messages like: ... ath10k_pci :03:00.0: no channel configured; ignoring frame(s)! ath10k_warn: 155 callbacks suppressed ... Use ath10k_dbg() here too Signed-off-by: Gabriel Craciunescu ---

[PATCH v3] ath10k: ath10k_htt_rx_amsdu_allowed() use ath10k_dbg()

Each time we get disconencted from AP we get flooded with messages like: ... ath10k_pci :03:00.0: no channel configured; ignoring frame(s)! ath10k_warn: 155 callbacks suppressed ... Use ath10k_dbg() here too Signed-off-by: Gabriel Craciunescu --- drivers/net/wireless/ath/ath10k/htt_rx.c

[PATCH V2 0/9] Bug fixes and improvements to Broadcom BDC driver

V2 Changes: - Add support for USB phys. We need to handle systems with either a single phy or systems with both a USB2.0 and USB3.0 phy - Fixes to the dt-bindings document based on feedback from Rob Herring. Changes include changing the compatible base name to "brcm,bdc" because

[PATCH V2 0/9] Bug fixes and improvements to Broadcom BDC driver

V2 Changes: - Add support for USB phys. We need to handle systems with either a single phy or systems with both a USB2.0 and USB3.0 phy - Fixes to the dt-bindings document based on feedback from Rob Herring. Changes include changing the compatible base name to "brcm,bdc" because

Re: [PATCH 09/10] percpu: replace area map allocator with bitmap allocator

On Sat, Jul 15, 2017 at 10:23:14PM -0400, Dennis Zhou wrote: > From: "Dennis Zhou (Facebook)" > > The percpu memory allocator is experiencing scalability issues when > allocating and freeing large numbers of counters as in BPF. > Additionally, there is a corner case where

Re: [PATCH 09/10] percpu: replace area map allocator with bitmap allocator

On Sat, Jul 15, 2017 at 10:23:14PM -0400, Dennis Zhou wrote: > From: "Dennis Zhou (Facebook)" > > The percpu memory allocator is experiencing scalability issues when > allocating and freeing large numbers of counters as in BPF. > Additionally, there is a corner case where iteration is triggered

[PATCH V2 1/9] usb: bdc: Fix misleading register names

The BDC endpoint status registers 0-7 were originally each going to be an array of regsiters. This was later changed to being a single register. The register definitions are being changed from: "#define BDC_EPSTS0(n) (0x60 + (n * 0x10))" to "#define BDC_EPSTS0 0x60" to reflect this change and

[PATCH V2 4/9] usb: bdc: Small code cleanup

Signed-off-by: Al Cooper --- drivers/usb/gadget/udc/bdc/bdc_core.c | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/drivers/usb/gadget/udc/bdc/bdc_core.c b/drivers/usb/gadget/udc/bdc/bdc_core.c index dda7b43..c2bfae2 100644 ---

[PATCH V2 1/9] usb: bdc: Fix misleading register names

The BDC endpoint status registers 0-7 were originally each going to be an array of regsiters. This was later changed to being a single register. The register definitions are being changed from: "#define BDC_EPSTS0(n) (0x60 + (n * 0x10))" to "#define BDC_EPSTS0 0x60" to reflect this change and

[PATCH V2 4/9] usb: bdc: Small code cleanup

Signed-off-by: Al Cooper --- drivers/usb/gadget/udc/bdc/bdc_core.c | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/drivers/usb/gadget/udc/bdc/bdc_core.c b/drivers/usb/gadget/udc/bdc/bdc_core.c index dda7b43..c2bfae2 100644 ---

[PATCH V2 2/9] dt-bindings: usb: bdc: Add Device Tree binding for Broadcom UDC driver

Add Device Tree binding document for Broadcom USB Device Controller (BDC). Signed-off-by: Al Cooper --- Documentation/devicetree/bindings/usb/brcm,bdc.txt | 29 ++ 1 file changed, 29 insertions(+) create mode 100644

[PATCH V2 2/9] dt-bindings: usb: bdc: Add Device Tree binding for Broadcom UDC driver

Add Device Tree binding document for Broadcom USB Device Controller (BDC). Signed-off-by: Al Cooper --- Documentation/devicetree/bindings/usb/brcm,bdc.txt | 29 ++ 1 file changed, 29 insertions(+) create mode 100644 Documentation/devicetree/bindings/usb/brcm,bdc.txt diff

[PATCH V2 5/9] usb: bdc: hook a quick Device Tree compatible string

From: Florian Fainelli Allows Device Tree probing Signed-off-by: Florian Fainelli Signed-off-by: Al Cooper --- drivers/usb/gadget/udc/bdc/bdc.h | 4 ++-- drivers/usb/gadget/udc/bdc/bdc_core.c | 8 2 files changed,

[PATCH V2 5/9] usb: bdc: hook a quick Device Tree compatible string

From: Florian Fainelli Allows Device Tree probing Signed-off-by: Florian Fainelli Signed-off-by: Al Cooper --- drivers/usb/gadget/udc/bdc/bdc.h | 4 ++-- drivers/usb/gadget/udc/bdc/bdc_core.c | 8 2 files changed, 10 insertions(+), 2 deletions(-) diff --git

[PATCH V2 7/9] usb: bdc: fix "xsf for ep not enabled" errror

This patch essentially clears the port status change bits at the correct times. It is necessary because the driver was not handling the change bits correctly for events during device connection/disconnection and bus enumeration. So, one of them (PCC) was left stuck sometimes causing the "xsf for

[PATCH V2 7/9] usb: bdc: fix "xsf for ep not enabled" errror

This patch essentially clears the port status change bits at the correct times. It is necessary because the driver was not handling the change bits correctly for events during device connection/disconnection and bus enumeration. So, one of them (PCC) was left stuck sometimes causing the "xsf for

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