Applied "dt-bindings: stm32: sai: fix DT example" to the asoc tree

The patch dt-bindings: stm32: sai: fix DT example has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Applied "dt-bindings: stm32: sai: fix DT example" to the asoc tree

The patch dt-bindings: stm32: sai: fix DT example has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Re: [PATCH 1/7] dt-bindings: stm32: sai: fix DT example

On Fri, Jun 16, 2017 at 02:15:28PM +0200, olivier moysan wrote: > Correct the device tree example. Please submit patches using subject lines reflecting the style for the subsystem. This makes it easier for people to identify relevant patches. Look at what existing commits in the area you're

Re: [PATCH 1/7] dt-bindings: stm32: sai: fix DT example

On Fri, Jun 16, 2017 at 02:15:28PM +0200, olivier moysan wrote: > Correct the device tree example. Please submit patches using subject lines reflecting the style for the subsystem. This makes it easier for people to identify relevant patches. Look at what existing commits in the area you're

Applied "dt-bindings: stm32: add h7 support for sai" to the asoc tree

The patch dt-bindings: stm32: add h7 support for sai has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "ASoC: stm32: sai: change stop sequence" to the asoc tree

The patch ASoC: stm32: sai: change stop sequence has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Applied "dt-bindings: stm32: add h7 support for sai" to the asoc tree

The patch dt-bindings: stm32: add h7 support for sai has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "ASoC: stm32: sai: change stop sequence" to the asoc tree

The patch ASoC: stm32: sai: change stop sequence has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Applied "ASoC: stm32: sai: fix clock management" to the asoc tree

The patch ASoC: stm32: sai: fix clock management has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Applied "ASoC: stm32: sai: fix clock management" to the asoc tree

The patch ASoC: stm32: sai: fix clock management has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Applied "ASoC: stm32: sai: add h7 support" to the asoc tree

The patch ASoC: stm32: sai: add h7 support has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during

Applied "ASoC: stm32: sai: add h7 support" to the asoc tree

The patch ASoC: stm32: sai: add h7 support has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during

Re: [PATCH 0/5] perf: add support for capturing skid IP

> > Yeah, I think it is easier and more portable, especially on hardware with a > > PEBS-like mechanism but no branch buffer (like LBR). FYI, I did do a test > > implementation yesterday to evaluate the difficulty. > > > A more generalized usage of the feature is to evaluate the amount of skid >

Re: [PATCH 0/5] perf: add support for capturing skid IP

> > Yeah, I think it is easier and more portable, especially on hardware with a > > PEBS-like mechanism but no branch buffer (like LBR). FYI, I did do a test > > implementation yesterday to evaluate the difficulty. > > > A more generalized usage of the feature is to evaluate the amount of skid >

Re: [PATCH] MIPS: Make individual platforms select ARCH_MIGHT_HAVE_PC_SERIO

On 06/15/2017 06:56 PM, Maciej W. Rozycki wrote: > On Mon, 5 Jun 2017, Florian Fainelli wrote: > >> Out of the many MIPS platforms only 3 appear to be actually using an >> I8042 keyboard controller: SGI, JAZZ and LOOGSON64, remove >> ARCH_MIGHT_HAVE_PC_SERIO from the top-level MIPS Kconfig symbol

Re: [PATCH] MIPS: Make individual platforms select ARCH_MIGHT_HAVE_PC_SERIO

On 06/15/2017 06:56 PM, Maciej W. Rozycki wrote: > On Mon, 5 Jun 2017, Florian Fainelli wrote: > >> Out of the many MIPS platforms only 3 appear to be actually using an >> I8042 keyboard controller: SGI, JAZZ and LOOGSON64, remove >> ARCH_MIGHT_HAVE_PC_SERIO from the top-level MIPS Kconfig symbol

Re: xgetbv nondeterminism

On Fri, Jun 16, 2017 at 9:38 AM, Andy Lutomirski wrote: > On Fri, Jun 16, 2017 at 9:17 AM, H.J. Lu wrote: >> On Fri, Jun 16, 2017 at 9:01 AM, Andy Lutomirski wrote: >>> On Thu, Jun 15, 2017 at 9:34 PM, H.J. Lu wrote:

Re: xgetbv nondeterminism

On Fri, Jun 16, 2017 at 9:38 AM, Andy Lutomirski wrote: > On Fri, Jun 16, 2017 at 9:17 AM, H.J. Lu wrote: >> On Fri, Jun 16, 2017 at 9:01 AM, Andy Lutomirski wrote: >>> On Thu, Jun 15, 2017 at 9:34 PM, H.J. Lu wrote: On Thu, Jun 15, 2017 at 8:05 PM, Andy Lutomirski wrote: > On Thu,

Re: [PATCH v2] serial: Delete dead code for CIR serial ports

On Fri, Jun 16, 2017 at 6:17 PM, Matthias Brugger wrote: > Commit e4fda3a04275 ("serial: don't register CIR serial ports") adds a > check for PORT_8250_CIR to serial8250_register_8250_port(). But the code > isn't needed as the function never takes the branch when the port is

Re: [PATCH v2] serial: Delete dead code for CIR serial ports

On Fri, Jun 16, 2017 at 6:17 PM, Matthias Brugger wrote: > Commit e4fda3a04275 ("serial: don't register CIR serial ports") adds a > check for PORT_8250_CIR to serial8250_register_8250_port(). But the code > isn't needed as the function never takes the branch when the port is CIR > serial port. >

Re: [RFC PATCH 00/13] Switchtec NTB Support

On Fri, Jun 16, 2017 at 10:47:21AM -0600, Logan Gunthorpe wrote: > > > On 16/06/17 09:34 AM, Allen Hubbe wrote: > > In code review, I really only have found minor nits. Overall, the driver > > looks good. > > Great, thanks for such a quick review! > > > In

Re: [RFC PATCH 00/13] Switchtec NTB Support

On Fri, Jun 16, 2017 at 10:47:21AM -0600, Logan Gunthorpe wrote: > > > On 16/06/17 09:34 AM, Allen Hubbe wrote: > > In code review, I really only have found minor nits. Overall, the driver > > looks good. > > Great, thanks for such a quick review! > > > In switchtec_ntb_part_op, there is a

[PATCH] staging: fusb302: don't bitshift __le16 type

The header field in struct pd_message is declared as an __le16 type. The data in the message is supposed to be little endian. This means we don't have to go and shift the individual bytes into position when we're filling the buffer, we can just copy the contents right away. As an added benefit we

[PATCH] staging: fusb302: don't bitshift __le16 type

The header field in struct pd_message is declared as an __le16 type. The data in the message is supposed to be little endian. This means we don't have to go and shift the individual bytes into position when we're filling the buffer, we can just copy the contents right away. As an added benefit we

Re: WARN_ON_ONCE() in process_one_work()?

On Thu, Jun 15, 2017 at 08:38:57AM -0700, Paul E. McKenney wrote: > On Wed, Jun 14, 2017 at 08:15:48AM -0700, Paul E. McKenney wrote: > > On Tue, Jun 13, 2017 at 03:31:03PM -0700, Paul E. McKenney wrote: > > > On Tue, Jun 13, 2017 at 04:58:37PM -0400, Tejun Heo wrote: > > > > Hello, Paul. > > > >

Re: WARN_ON_ONCE() in process_one_work()?

On Thu, Jun 15, 2017 at 08:38:57AM -0700, Paul E. McKenney wrote: > On Wed, Jun 14, 2017 at 08:15:48AM -0700, Paul E. McKenney wrote: > > On Tue, Jun 13, 2017 at 03:31:03PM -0700, Paul E. McKenney wrote: > > > On Tue, Jun 13, 2017 at 04:58:37PM -0400, Tejun Heo wrote: > > > > Hello, Paul. > > > >

Re: [PATCH 2/2] perf report: report module before querying isactivation in dwfl unwind

Em Fri, Jun 16, 2017 at 01:06:52PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Fri, Jun 02, 2017 at 12:25:08PM -0300, Arnaldo Carvalho de Melo escreveu: > > Em Fri, Jun 02, 2017 at 04:37:53PM +0200, Milian Wolff escreveu: > > > The PC returned by dwfl_frame_pc may map into a not-yet-reported >

Re: [PATCH 2/2] perf report: report module before querying isactivation in dwfl unwind

Em Fri, Jun 16, 2017 at 01:06:52PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Fri, Jun 02, 2017 at 12:25:08PM -0300, Arnaldo Carvalho de Melo escreveu: > > Em Fri, Jun 02, 2017 at 04:37:53PM +0200, Milian Wolff escreveu: > > > The PC returned by dwfl_frame_pc may map into a not-yet-reported >

Re: [PATCH 1/2] iommu/s390: Use iommu_group_get_for_dev() in s390_iommu_add_device()

On Thu, 15 Jun 2017 15:11:51 +0200 Joerg Roedel wrote: > From: Joerg Roedel > > The iommu_group_get_for_dev() function also attaches the > device to its group, so this code doesn't need to be in the > iommu driver. > > Further by using this function the

Re: [PATCH 1/2] iommu/s390: Use iommu_group_get_for_dev() in s390_iommu_add_device()

On Thu, 15 Jun 2017 15:11:51 +0200 Joerg Roedel wrote: > From: Joerg Roedel > > The iommu_group_get_for_dev() function also attaches the > device to its group, so this code doesn't need to be in the > iommu driver. > > Further by using this function the driver can make use of > default

Re: [PATCH] usb: host: ehci: workaround PME bug on AMD EHCI controller

On Sat, 17 Jun 2017, Kai-Heng Feng wrote: > On Fri, Jun 16, 2017 at 11:07 AM, Kai-Heng Feng > wrote: > > On Thu, Jun 15, 2017 at 10:12 PM, Alan Stern > > wrote: > >> Those documents refer to a hardware bug with a workaround in the BIOS. >

Re: [PATCH] usb: host: ehci: workaround PME bug on AMD EHCI controller

On Sat, 17 Jun 2017, Kai-Heng Feng wrote: > On Fri, Jun 16, 2017 at 11:07 AM, Kai-Heng Feng > wrote: > > On Thu, Jun 15, 2017 at 10:12 PM, Alan Stern > > wrote: > >> Those documents refer to a hardware bug with a workaround in the BIOS. > >> Have you checked to see if your BIOS is up to date?

Re: [PATCH v2 03/11] tty: kbd: reduce stack size with KASAN

On Fri, Jun 16, 2017 at 8:58 AM, Samuel Thibault wrote: > Arnd Bergmann, on ven. 16 juin 2017 17:41:47 +0200, wrote: >> The problem are the 'ch' and 'flag' variables that are passed into >> tty_insert_flip_char by value, and from there into >>

Re: [PATCH v2 03/11] tty: kbd: reduce stack size with KASAN

On Fri, Jun 16, 2017 at 8:58 AM, Samuel Thibault wrote: > Arnd Bergmann, on ven. 16 juin 2017 17:41:47 +0200, wrote: >> The problem are the 'ch' and 'flag' variables that are passed into >> tty_insert_flip_char by value, and from there into >> tty_insert_flip_string_flags by reference. In this

[PATCH] net/phy: micrel: configure intterupts after autoneg workaround

The commit ("net/phy: micrel: Add workaround for bad autoneg") fixes an autoneg failure case by resetting the hardware. This turns off intterupts. Things will work themselves out if the phy polls, as it will figure out it's state during a poll. However if the phy uses only intterupts, the phy will

[PATCH] net/phy: micrel: configure intterupts after autoneg workaround

The commit ("net/phy: micrel: Add workaround for bad autoneg") fixes an autoneg failure case by resetting the hardware. This turns off intterupts. Things will work themselves out if the phy polls, as it will figure out it's state during a poll. However if the phy uses only intterupts, the phy will

Re: linux-next: build failure after merge of the akpm-current tree

On Thu, 15 Jun 2017 16:46:33 -0700 Kees Cook wrote: > On Thu, Jun 15, 2017 at 12:12 PM, Andrew Morton > wrote: > > On Wed, 14 Jun 2017 18:56:30 -0700 Kees Cook wrote: > > > >> >> Caused by commit > >> >> > >> >>

Re: linux-next: build failure after merge of the akpm-current tree

On Thu, 15 Jun 2017 16:46:33 -0700 Kees Cook wrote: > On Thu, Jun 15, 2017 at 12:12 PM, Andrew Morton > wrote: > > On Wed, 14 Jun 2017 18:56:30 -0700 Kees Cook wrote: > > > >> >> Caused by commit > >> >> > >> >> 088a5ecf7581 ("include/linux/string.h: add the option of fortified > >> >>

Re: [PATCH v4 0/5] Improve watchdog config for arch watchdogs

Tested on sparc: Tested-by: Babu Moger Reviewed patch #1, #2, #3 Reviewed-by: Babu Moger On 6/16/2017 9:50 AM, Don Zickus wrote: (adding Andrew) On Fri, Jun 16, 2017 at 04:57:10PM +1000, Nicholas Piggin wrote: This is the latest series to

Re: [PATCH v4 0/5] Improve watchdog config for arch watchdogs

Tested on sparc: Tested-by: Babu Moger Reviewed patch #1, #2, #3 Reviewed-by: Babu Moger On 6/16/2017 9:50 AM, Don Zickus wrote: (adding Andrew) On Fri, Jun 16, 2017 at 04:57:10PM +1000, Nicholas Piggin wrote: This is the latest series to make the hardlockup watchdog more easily

[RFH] qemu-2.6 memory corruption with OVMF and linux-4.9

Hello, I tried to get QEMU running with UEFI and SecureBoot. It sometimes works, but sometimes I get memory corruption: - the Debian installer sometimes fails to load the "libata.ko" or "e1000.ko" modules. - it it not always the same module - my guest kernel uses KASLR, which might explain

[RFH] qemu-2.6 memory corruption with OVMF and linux-4.9

Hello, I tried to get QEMU running with UEFI and SecureBoot. It sometimes works, but sometimes I get memory corruption: - the Debian installer sometimes fails to load the "libata.ko" or "e1000.ko" modules. - it it not always the same module - my guest kernel uses KASLR, which might explain

Re: [PATCH v2 03/11] tty: kbd: reduce stack size with KASAN

On 06/16/2017 06:41 PM, Arnd Bergmann wrote: > On Fri, Jun 16, 2017 at 3:02 PM, Greg Kroah-Hartman > wrote: >> On Fri, Jun 16, 2017 at 02:01:57PM +0200, Arnd Bergmann wrote: >>> On Thu, Jun 15, 2017 at 6:53 AM, Greg Kroah-Hartman >>> wrote:

Re: [PATCH v2 03/11] tty: kbd: reduce stack size with KASAN

On 06/16/2017 06:41 PM, Arnd Bergmann wrote: > On Fri, Jun 16, 2017 at 3:02 PM, Greg Kroah-Hartman > wrote: >> On Fri, Jun 16, 2017 at 02:01:57PM +0200, Arnd Bergmann wrote: >>> On Thu, Jun 15, 2017 at 6:53 AM, Greg Kroah-Hartman >>> wrote: On Thu, Jun 15, 2017 at 06:52:21AM +0200, Greg

Re: [PATCH 0/5] perf: add support for capturing skid IP

On Fri, Jun 16, 2017 at 10:08 AM, Stephane Eranian wrote: > On Fri, Jun 16, 2017 at 9:06 AM, Andi Kleen wrote: >> On Thu, Jun 15, 2017 at 11:52:07PM -0700, Stephane Eranian wrote: >>> Andi, >>> >>> On Thu, Jun 15, 2017 at 4:18 PM, Andi Kleen

Re: [PATCH 0/5] perf: add support for capturing skid IP

On Fri, Jun 16, 2017 at 10:08 AM, Stephane Eranian wrote: > On Fri, Jun 16, 2017 at 9:06 AM, Andi Kleen wrote: >> On Thu, Jun 15, 2017 at 11:52:07PM -0700, Stephane Eranian wrote: >>> Andi, >>> >>> On Thu, Jun 15, 2017 at 4:18 PM, Andi Kleen wrote: >>> >> Looking at this approach, the user

Re: [PATCH 2/2] i2c: Add Spreadtrum I2C controller driver

Hi Baolin, [auto build test ERROR on wsa/i2c/for-next] [also build test ERROR on v4.12-rc5 next-20170616] [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/Baolin-Wang/dt-bindings-i2c-Add

Re: [PATCH 2/2] i2c: Add Spreadtrum I2C controller driver

Hi Baolin, [auto build test ERROR on wsa/i2c/for-next] [also build test ERROR on v4.12-rc5 next-20170616] [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/Baolin-Wang/dt-bindings-i2c-Add

Re: autofs multi-map regression

Dick Streefland writes: > After a recent upgrade of a Ubuntu xenial machine, a particular > autofs multi-map mount setup stopped working. A simplified example is: > > :: > auto.master > :: > /net /etc/auto.net > :: > auto.net >

Re: autofs multi-map regression

Dick Streefland writes: > After a recent upgrade of a Ubuntu xenial machine, a particular > autofs multi-map mount setup stopped working. A simplified example is: > > :: > auto.master > :: > /net /etc/auto.net > :: > auto.net > :: >

Re: [RFC PATCH 00/13] Switchtec NTB Support

On 16/06/17 10:33 AM, Serge Semin wrote: > New NTB API is going to be merged to mainline kernel within next features > merge window, so it's really recommended to use that API for new hardware. > Could you please rabase your driver on top of the tree? > https://github.com/jonmason/ntb.git Yes,

Re: [RFC PATCH 00/13] Switchtec NTB Support

On 16/06/17 10:33 AM, Serge Semin wrote: > New NTB API is going to be merged to mainline kernel within next features > merge window, so it's really recommended to use that API for new hardware. > Could you please rabase your driver on top of the tree? > https://github.com/jonmason/ntb.git Yes,

Re: [PATCH 0/5] perf: add support for capturing skid IP

On Fri, Jun 16, 2017 at 9:06 AM, Andi Kleen wrote: > On Thu, Jun 15, 2017 at 11:52:07PM -0700, Stephane Eranian wrote: >> Andi, >> >> On Thu, Jun 15, 2017 at 4:18 PM, Andi Kleen wrote: >> >> Looking at this approach, the user interface is

Re: [PATCH 0/5] perf: add support for capturing skid IP

On Fri, Jun 16, 2017 at 9:06 AM, Andi Kleen wrote: > On Thu, Jun 15, 2017 at 11:52:07PM -0700, Stephane Eranian wrote: >> Andi, >> >> On Thu, Jun 15, 2017 at 4:18 PM, Andi Kleen wrote: >> >> Looking at this approach, the user interface is straightforward, >> >> implementation in the x86 code is

[PATCH v2 2/2] tracing: Document the use of TRACE_DEFINE_SIZEOF

The kernel now corrects the use of sizeof() in the trace format files. Lets document how to make use of that feature. Signed-off-by: Jeremy Linton --- samples/trace_events/trace-events-sample.h | 28 +++- 1 file changed, 19 insertions(+), 9

[PATCH v2 2/2] tracing: Document the use of TRACE_DEFINE_SIZEOF

The kernel now corrects the use of sizeof() in the trace format files. Lets document how to make use of that feature. Signed-off-by: Jeremy Linton --- samples/trace_events/trace-events-sample.h | 28 +++- 1 file changed, 19 insertions(+), 9 deletions(-) diff --git

[PATCH v2 1/2] tracing: trivial: Fix spelling mistakes in trace sample

The trace sample file has a couple mispellings, lets fix them. Signed-off-by: Jeremy Linton --- samples/trace_events/trace-events-sample.h | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/samples/trace_events/trace-events-sample.h

[PATCH v2 1/2] tracing: trivial: Fix spelling mistakes in trace sample

The trace sample file has a couple mispellings, lets fix them. Signed-off-by: Jeremy Linton --- samples/trace_events/trace-events-sample.h | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/samples/trace_events/trace-events-sample.h

[PATCH v5 1/2] arm64: dts: mt7622: add basic nodes to the mt7622.dtsi file

From: Sean Wang add basic nodes into the mt7622.dtsi for the system bring-up which includes ARM CPU, GIC, timer, MediaTek UART, SYSIRQ and one reserved memory region for ATF. Signed-off-by: Sean Wang --- arch/arm64/boot/dts/mediatek/mt7622.dtsi

[PATCH v5 1/2] arm64: dts: mt7622: add basic nodes to the mt7622.dtsi file

From: Sean Wang add basic nodes into the mt7622.dtsi for the system bring-up which includes ARM CPU, GIC, timer, MediaTek UART, SYSIRQ and one reserved memory region for ATF. Signed-off-by: Sean Wang --- arch/arm64/boot/dts/mediatek/mt7622.dtsi | 110 +++ 1 file

[PATCH v5 0/2] Add Basic SoC support for MT7622

From: Sean Wang Changes since v4: - redefine the two dummy clocks with the correct frequency which is 25MHz and 280MHz respectively. Changes since v3: - get rid of those accepted patches - rebased to branch v4.12-next/dts64 in Matthias' tree - fixed uart node in dts

[PATCH v5 0/2] Add Basic SoC support for MT7622

From: Sean Wang Changes since v4: - redefine the two dummy clocks with the correct frequency which is 25MHz and 280MHz respectively. Changes since v3: - get rid of those accepted patches - rebased to branch v4.12-next/dts64 in Matthias' tree - fixed uart node in dts with two clocks as

[PATCH v5 2/2] arm64: dts: mt7622: add dts file for MT7622 reference board variant 1

From: Sean Wang Add the support for the MT7622 reference board variant 1 from MediaTek. Signed-off-by: Sean Wang --- arch/arm64/boot/dts/mediatek/Makefile| 1 + arch/arm64/boot/dts/mediatek/mt7622-rfb1.dts | 27

[PATCH v5 2/2] arm64: dts: mt7622: add dts file for MT7622 reference board variant 1

From: Sean Wang Add the support for the MT7622 reference board variant 1 from MediaTek. Signed-off-by: Sean Wang --- arch/arm64/boot/dts/mediatek/Makefile| 1 + arch/arm64/boot/dts/mediatek/mt7622-rfb1.dts | 27 +++ 2 files changed, 28 insertions(+) create

Re: [RFT v2] pinctrl: samsung: Fix NULL pointer exception on external interrupts on S3C24xx

On Thursday, June 15, 2017 11:46 PM, Krzysztof Kozlowski wrote: After commit 8b1bd11c1f8f ("pinctrl: samsung: Add the support the multiple IORESOURCE_MEM for one pin-bank"), the S3C24xx (and probably S3C64xx as well) fails: Unable to handle kernel NULL pointer dereference at virtual

Re: [RFT v2] pinctrl: samsung: Fix NULL pointer exception on external interrupts on S3C24xx

On Thursday, June 15, 2017 11:46 PM, Krzysztof Kozlowski wrote: After commit 8b1bd11c1f8f ("pinctrl: samsung: Add the support the multiple IORESOURCE_MEM for one pin-bank"), the S3C24xx (and probably S3C64xx as well) fails: Unable to handle kernel NULL pointer dereference at virtual

Re: [PATCH] drm: hdlcd: Update PM code to save/restore console.

Den 16.06.2017 15.53, skrev Liviu Dudau: Update the PM code to suspend/resume the fbdev_cma console. Signed-off-by: Liviu Dudau --- drivers/gpu/drm/arm/hdlcd_drv.c | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git

Re: [PATCH] drm: hdlcd: Update PM code to save/restore console.

Den 16.06.2017 15.53, skrev Liviu Dudau: Update the PM code to suspend/resume the fbdev_cma console. Signed-off-by: Liviu Dudau --- drivers/gpu/drm/arm/hdlcd_drv.c | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/arm/hdlcd_drv.c

Re: [RFC 3/3] rt: Check if the task needs to migrate when re-enabling migration

On 2017-06-16 12:39:48 [+0200], Daniel Bristot de Oliveira wrote: > In the case of an affinity change during a migrate_disable section, > __set_cpus_allowed_ptr will not try to move the task from a CPU > in which it cannot execute anymore. > > So, after enabling migration, if the current task

Re: [RFC 3/3] rt: Check if the task needs to migrate when re-enabling migration

On 2017-06-16 12:39:48 [+0200], Daniel Bristot de Oliveira wrote: > In the case of an affinity change during a migrate_disable section, > __set_cpus_allowed_ptr will not try to move the task from a CPU > in which it cannot execute anymore. > > So, after enabling migration, if the current task

Re: [PATCH] PCI: imx6: add regulator support

On Thu, Jun 08, 2017 at 10:07:42AM +0200, Quentin Schulz wrote: > Some boards might require to control a regulator to power the PCIe port. > > This adds support for an optional regulator defined in Device Tree > linked in the PCIe controller under `vpcie-supply`. If present, the > regulator will

Re: [PATCH] PCI: imx6: add regulator support

On Thu, Jun 08, 2017 at 10:07:42AM +0200, Quentin Schulz wrote: > Some boards might require to control a regulator to power the PCIe port. > > This adds support for an optional regulator defined in Device Tree > linked in the PCIe controller under `vpcie-supply`. If present, the > regulator will

Re: [PATCH] MAINTAINERS: Add an entry for MediaTek PCIe driver

On Fri, Jun 16, 2017 at 12:53:09PM +0800, Ryder Lee wrote: > Add MediaTek PCIe driver maintainer entry. > > Signed-off-by: Ryder Lee Folded into pci/host-mediatek for v4.13, thanks! > --- > MAINTAINERS | 8 > 1 file changed, 8 insertions(+) > > diff --git

Re: [PATCH] MAINTAINERS: Add an entry for MediaTek PCIe driver

On Fri, Jun 16, 2017 at 12:53:09PM +0800, Ryder Lee wrote: > Add MediaTek PCIe driver maintainer entry. > > Signed-off-by: Ryder Lee Folded into pci/host-mediatek for v4.13, thanks! > --- > MAINTAINERS | 8 > 1 file changed, 8 insertions(+) > > diff --git a/MAINTAINERS b/MAINTAINERS

Re: Crypto Fixes for 4.12

From: Theodore Ts'o Date: Fri, 16 Jun 2017 08:50:07 -0400 > On Thu, Jun 15, 2017 at 11:01:18AM -0400, David Miller wrote: >> As a side note, ext4 does something similar with a private >> implementation, but it doesn't use something the evaluates to an >> alloca. Instead it uses a

Re: Crypto Fixes for 4.12

From: Theodore Ts'o Date: Fri, 16 Jun 2017 08:50:07 -0400 > On Thu, Jun 15, 2017 at 11:01:18AM -0400, David Miller wrote: >> As a side note, ext4 does something similar with a private >> implementation, but it doesn't use something the evaluates to an >> alloca. Instead it uses a fixed 4-byte

[GIT PULL] PCI fixes for v4.12

PCI fixes: - fix another PCI_ENDPOINT build error (merged for v4.12) - fix error codes added to config accessors for v4.12 The following changes since commit 4d071c3238987325b9e50e33051a40d1cce311cc: PCI/PM: Add needs_resume flag to avoid suspend complete optimization (2017-05-23

[GIT PULL] PCI fixes for v4.12

PCI fixes: - fix another PCI_ENDPOINT build error (merged for v4.12) - fix error codes added to config accessors for v4.12 The following changes since commit 4d071c3238987325b9e50e33051a40d1cce311cc: PCI/PM: Add needs_resume flag to avoid suspend complete optimization (2017-05-23

Re: [RFC PATCH 00/13] Switchtec NTB Support

On 16/06/17 09:34 AM, Allen Hubbe wrote: > In code review, I really only have found minor nits. Overall, the driver > looks good. Great, thanks for such a quick review! > In switchtec_ntb_part_op, there is a delay of up to 50s (1000 * 50ms). This > looks like a thread context, so it could

Re: [RFC PATCH 00/13] Switchtec NTB Support

On 16/06/17 09:34 AM, Allen Hubbe wrote: > In code review, I really only have found minor nits. Overall, the driver > looks good. Great, thanks for such a quick review! > In switchtec_ntb_part_op, there is a delay of up to 50s (1000 * 50ms). This > looks like a thread context, so it could

Re: LTS testing with latest kselftests - some failures

Kees, please review 47e0bbb7fa98 below. Brian, please review be4a1326d12c below. On Thu, Jun 15, 2017 at 11:26:53PM +0530, Sumit Semwal wrote: > Hello Greg, Shuah, > > While testing 4.4.y and 4.9.y LTS kernels with latest kselftest, To be clear it seems like you are taking the latest upstream

Re: LTS testing with latest kselftests - some failures

Kees, please review 47e0bbb7fa98 below. Brian, please review be4a1326d12c below. On Thu, Jun 15, 2017 at 11:26:53PM +0530, Sumit Semwal wrote: > Hello Greg, Shuah, > > While testing 4.4.y and 4.9.y LTS kernels with latest kselftest, To be clear it seems like you are taking the latest upstream

Re: [PATCH v9 5/7] vfio: Define vfio based dma-buf operations

On Fri, 16 Jun 2017 19:02:30 +0530 Kirti Wankhede wrote: > On 6/16/2017 2:08 AM, Alex Williamson wrote: > > On Thu, 15 Jun 2017 18:00:38 +0200 > > Gerd Hoffmann wrote: > > > >> Hi, > >> > +struct vfio_dmabuf_mgr_plane_info { > +

Re: [PATCH v9 5/7] vfio: Define vfio based dma-buf operations

On Fri, 16 Jun 2017 19:02:30 +0530 Kirti Wankhede wrote: > On 6/16/2017 2:08 AM, Alex Williamson wrote: > > On Thu, 15 Jun 2017 18:00:38 +0200 > > Gerd Hoffmann wrote: > > > >> Hi, > >> > +struct vfio_dmabuf_mgr_plane_info { > +__u64 start; > +__u64

Re: [RFC] KVM: SVM: do not drop VMCB CPL to 0 if SS is not present

On 15/06/2017 23:44, Andy Lutomirski wrote: > On Tue, May 30, 2017 at 9:05 AM, Paolo Bonzini wrote: >> On 30/05/2017 17:58, Roman Penyaev wrote: >>> We will have CPL in var->dpl, and it seems ok. All we need is not >>> to lose it on the way kernel->userspace->kernel. >> >>

Re: [RFC] KVM: SVM: do not drop VMCB CPL to 0 if SS is not present

On 15/06/2017 23:44, Andy Lutomirski wrote: > On Tue, May 30, 2017 at 9:05 AM, Paolo Bonzini wrote: >> On 30/05/2017 17:58, Roman Penyaev wrote: >>> We will have CPL in var->dpl, and it seems ok. All we need is not >>> to lose it on the way kernel->userspace->kernel. >> >> You're right. So

[PATCH v3 2/4] [media] platform: Add Synopsys Designware HDMI RX Controller Driver

This is an initial submission for the Synopsys Designware HDMI RX Controller Driver. This driver interacts with a phy driver so that a communication between them is created and a video pipeline is configured. The controller + phy pipeline can then be integrated into a fully featured system that

[PATCH v3 2/4] [media] platform: Add Synopsys Designware HDMI RX Controller Driver

This is an initial submission for the Synopsys Designware HDMI RX Controller Driver. This driver interacts with a phy driver so that a communication between them is created and a video pipeline is configured. The controller + phy pipeline can then be integrated into a fully featured system that

[PATCH v3 0/4] Synopsys Designware HDMI Video Capture Controller + PHY

The Synopsys Designware HDMI RX controller is an HDMI receiver controller that is responsible to process digital data that comes from a phy. The final result is a stream of raw video data that can then be connected to a video DMA, for example, and transfered into RAM so that it can be displayed.

[PATCH v3 0/4] Synopsys Designware HDMI Video Capture Controller + PHY

The Synopsys Designware HDMI RX controller is an HDMI receiver controller that is responsible to process digital data that comes from a phy. The final result is a stream of raw video data that can then be connected to a video DMA, for example, and transfered into RAM so that it can be displayed.

[PATCH v3 3/4] MAINTAINERS: Add entry for Synopsys Designware HDMI drivers

Add a entry for Synopsys Designware HDMI Receivers drivers and phys. Signed-off-by: Jose Abreu Cc: Carlos Palminha --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 053c3bd..e798040 100644 ---

[PATCH v3 3/4] MAINTAINERS: Add entry for Synopsys Designware HDMI drivers

Add a entry for Synopsys Designware HDMI Receivers drivers and phys. Signed-off-by: Jose Abreu Cc: Carlos Palminha --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 053c3bd..e798040 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -11294,6

[PATCH v3 1/4] [media] platform: Add Synopsys Designware HDMI RX PHY e405 Driver

This adds support for the Synopsys Designware HDMI RX PHY e405. This phy receives and decodes HDMI video that is delivered to a controller. Main features included in this driver are: - Equalizer algorithm that chooses the phy best settings according to the detected HDMI cable

[PATCH v3 4/4] dt-bindings: media: Document Synopsys Designware HDMI RX

Document the bindings for the Synopsys Designware HDMI RX. Signed-off-by: Jose Abreu Cc: Carlos Palminha Cc: Rob Herring Cc: Mark Rutland Cc: Mauro Carvalho Chehab Cc: Hans Verkuil

[PATCH v3 4/4] dt-bindings: media: Document Synopsys Designware HDMI RX

Document the bindings for the Synopsys Designware HDMI RX. Signed-off-by: Jose Abreu Cc: Carlos Palminha Cc: Rob Herring Cc: Mark Rutland Cc: Mauro Carvalho Chehab Cc: Hans Verkuil Changes from v2: - Document edid-phandle property ---

[PATCH v3 1/4] [media] platform: Add Synopsys Designware HDMI RX PHY e405 Driver

This adds support for the Synopsys Designware HDMI RX PHY e405. This phy receives and decodes HDMI video that is delivered to a controller. Main features included in this driver are: - Equalizer algorithm that chooses the phy best settings according to the detected HDMI cable

Re: xgetbv nondeterminism

On Fri, Jun 16, 2017 at 9:17 AM, H.J. Lu wrote: > On Fri, Jun 16, 2017 at 9:01 AM, Andy Lutomirski wrote: >> On Thu, Jun 15, 2017 at 9:34 PM, H.J. Lu wrote: >>> On Thu, Jun 15, 2017 at 8:05 PM, Andy Lutomirski wrote:

Re: xgetbv nondeterminism

On Fri, Jun 16, 2017 at 9:17 AM, H.J. Lu wrote: > On Fri, Jun 16, 2017 at 9:01 AM, Andy Lutomirski wrote: >> On Thu, Jun 15, 2017 at 9:34 PM, H.J. Lu wrote: >>> On Thu, Jun 15, 2017 at 8:05 PM, Andy Lutomirski wrote: On Thu, Jun 15, 2017 at 7:17 PM, H.J. Lu wrote: > On Thu, Jun 15,

To whom it may concern

To whom it may concern, My name is Professor Itse Sagay, Professor Itse Sagay,Chairman Presidential Advisory Committee against Corruption Federal Republic of Nigeria. My reason of contacting you is in line with the desire of President Muhammadu Buhari quest to wipe corruption out of the Nigeria

To whom it may concern

To whom it may concern, My name is Professor Itse Sagay, Professor Itse Sagay,Chairman Presidential Advisory Committee against Corruption Federal Republic of Nigeria. My reason of contacting you is in line with the desire of President Muhammadu Buhari quest to wipe corruption out of the Nigeria

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