RE: [PATCH v3] Add driver to force WMI Thunderbolt controller power status

> -Original Message- > From: Lukas Wunner [mailto:lu...@wunner.de] > Sent: Thursday, September 14, 2017 4:14 AM > To: Limonciello, Mario > Cc: dvh...@infradead.org; linux-kernel@vger.kernel.org; platform-driver- > x...@vger.kernel.org; hughsi...@gmail.com;

RE: [PATCH v3] Add driver to force WMI Thunderbolt controller power status

> -Original Message- > From: Lukas Wunner [mailto:lu...@wunner.de] > Sent: Thursday, September 14, 2017 4:14 AM > To: Limonciello, Mario > Cc: dvh...@infradead.org; linux-kernel@vger.kernel.org; platform-driver- > x...@vger.kernel.org; hughsi...@gmail.com; yehezkel...@gmail.com; >

[PATCH] ocfs2: remove some redundant assignments

From: Colin Ian King The initialization of free_space is redundant as free_space is updated later on and the initialized value is hence never used. The pointer new_list is set but never used so it can be completely removed. Cleans up clang scan-build warnings. "Value

[PATCH] ocfs2: remove some redundant assignments

From: Colin Ian King The initialization of free_space is redundant as free_space is updated later on and the initialized value is hence never used. The pointer new_list is set but never used so it can be completely removed. Cleans up clang scan-build warnings. "Value stored to 'free_space'

[PATCH v4 3/6] iio: adc: sun4i-gpadc-iio: rework code for supporting newer THS variants

The SoCs after H3 has newer thermal sensor ADCs, which have two clock inputs (bus clock and sampling clock) and a reset. The registers are also re-arranged. This commit reworks the code, adds the process of the clocks and resets, and allows the sampling start/end code and the position of value

[PATCH v4 3/6] iio: adc: sun4i-gpadc-iio: rework code for supporting newer THS variants

The SoCs after H3 has newer thermal sensor ADCs, which have two clock inputs (bus clock and sampling clock) and a reset. The registers are also re-arranged. This commit reworks the code, adds the process of the clocks and resets, and allows the sampling start/end code and the position of value

[PATCH v4 4/6] iio: adc: sun4i-gpadc-iio: add support for H3 thermal sensor

This adds support for the Allwinner H3 thermal sensor. Allwinner H3 has a thermal sensor like the one in A33, but have its registers nearly all re-arranged, sample clock moved to CCU and a pair of bus clock and reset added. It's also the base of newer SoCs' thermal sensors. The thermal sensors

[PATCH v4 4/6] iio: adc: sun4i-gpadc-iio: add support for H3 thermal sensor

This adds support for the Allwinner H3 thermal sensor. Allwinner H3 has a thermal sensor like the one in A33, but have its registers nearly all re-arranged, sample clock moved to CCU and a pair of bus clock and reset added. It's also the base of newer SoCs' thermal sensors. The thermal sensors

[PATCH] uwb: ensure that endpoint is interrupt

hwarc_neep_init() assumes that endpoint 0 is interrupt, but there's no check for that, which results in a WARNING in USB core code, when a bad USB descriptor is provided from a device: usb 1-1: BOGUS urb xfer, pipe 1 != type 3 [ cut here ] WARNING: CPU: 0 PID: 3 at

[PATCH] uwb: ensure that endpoint is interrupt

hwarc_neep_init() assumes that endpoint 0 is interrupt, but there's no check for that, which results in a WARNING in USB core code, when a bad USB descriptor is provided from a device: usb 1-1: BOGUS urb xfer, pipe 1 != type 3 [ cut here ] WARNING: CPU: 0 PID: 3 at

[PATCH v4 5/6] ARM: sun8i: h3: add support for the thermal sensor in H3

As we have gained the support for the thermal sensor in H3, we can now add its device nodes to the device tree. Add them to the H3 device tree. The calibration data of the thermal sensor is still not added, as it's currently not used, and the SID node is not added yet. The H5 thermal sensor has

[PATCH v4 6/6] ARM: sun8i: h3: add partial CPU thermal zone

Because of the restriction of the OF thermal framework, the thermal sensor will fail to probe if the thermal zone doesn't exist. Add a partial thermal zone which claims the H3 THS as the thermal sensor. The cooling device (CPU DVFS) is still not added as it's not ready, and the trip points are

[PATCH v4 5/6] ARM: sun8i: h3: add support for the thermal sensor in H3

As we have gained the support for the thermal sensor in H3, we can now add its device nodes to the device tree. Add them to the H3 device tree. The calibration data of the thermal sensor is still not added, as it's currently not used, and the SID node is not added yet. The H5 thermal sensor has

[PATCH v4 6/6] ARM: sun8i: h3: add partial CPU thermal zone

Because of the restriction of the OF thermal framework, the thermal sensor will fail to probe if the thermal zone doesn't exist. Add a partial thermal zone which claims the H3 THS as the thermal sensor. The cooling device (CPU DVFS) is still not added as it's not ready, and the trip points are

[PATCH v4 1/6] dt-bindings: update the Allwinner GPADC device tree binding for H3

Allwinner H3 features a thermal sensor like the one in A33, but has its register re-arranged, the clock divider moved to CCU (originally the clock divider is in ADC) and added a pair of bus clock and reset. Update the binding document to cover H3. Signed-off-by: Icenowy Zheng

[PATCH v4 1/6] dt-bindings: update the Allwinner GPADC device tree binding for H3

Allwinner H3 features a thermal sensor like the one in A33, but has its register re-arranged, the clock divider moved to CCU (originally the clock divider is in ADC) and added a pair of bus clock and reset. Update the binding document to cover H3. Signed-off-by: Icenowy Zheng Reviewed-by:

[PATCH v4 2/6] iio: adc: sun4i-gpadc-iio: rename A33-specified registers to contain A33

As the H3 SoC, which is also in sun8i line, has totally different register map for the thermal sensor (a cut down version of GPADC), we should rename A23/A33-specified registers to contain A33, in order to prevent obfuscation with H3 registers. Currently these registers are only prefixed "SUN8I",

[PATCH v4 2/6] iio: adc: sun4i-gpadc-iio: rename A33-specified registers to contain A33

As the H3 SoC, which is also in sun8i line, has totally different register map for the thermal sensor (a cut down version of GPADC), we should rename A23/A33-specified registers to contain A33, in order to prevent obfuscation with H3 registers. Currently these registers are only prefixed "SUN8I",

[PATCH v4 0/6] IIO-based thermal sensor driver for Allwinner H3 SoC

Allwiner H3 SoC has a thermal sensor, which is a large refactored version of the old Allwinner "GPADC" (although it have already only thermal part left in A33). This patch tried to add support for the sensor in H3 based on the A33 thermal sensor driver by Quentin Schulz, which is already merged.

[PATCH v4 0/6] IIO-based thermal sensor driver for Allwinner H3 SoC

Allwiner H3 SoC has a thermal sensor, which is a large refactored version of the old Allwinner "GPADC" (although it have already only thermal part left in A33). This patch tried to add support for the sensor in H3 based on the A33 thermal sensor driver by Quentin Schulz, which is already merged.

Re: [PATCH v2 1/2] watchdog: dw_wdt: add stop watchdog operation

On Thu, Sep 14, 2017 at 01:30:12PM +0200, Oleksij Rempel wrote: > From: Steffen Trumtrar > > The only way of stopping the watchdog is by resetting it. > Add the watchdog op for stopping the device and reset if > a reset line is provided. > > Signed-off-by: Steffen

Re: [PATCH v2 1/2] watchdog: dw_wdt: add stop watchdog operation

On Thu, Sep 14, 2017 at 01:30:12PM +0200, Oleksij Rempel wrote: > From: Steffen Trumtrar > > The only way of stopping the watchdog is by resetting it. > Add the watchdog op for stopping the device and reset if > a reset line is provided. > > Signed-off-by: Steffen Trumtrar > Signed-off-by:

Re: [PATCH] fs/proc: report eip/esp in /prod/PID/stat for coredumping

On Thu, Sep 14, 2017 at 2:42 AM, John Ogness wrote: > Commit 0a1eb2d474ed ("fs/proc: Stop reporting eip and esp in > /proc/PID/stat") stopped reporting eip/esp because it is > racey and dangerous for executing tasks. The comment adds: > > As far as I know, there are

Re: [PATCH] fs/proc: report eip/esp in /prod/PID/stat for coredumping

On Thu, Sep 14, 2017 at 2:42 AM, John Ogness wrote: > Commit 0a1eb2d474ed ("fs/proc: Stop reporting eip and esp in > /proc/PID/stat") stopped reporting eip/esp because it is > racey and dangerous for executing tasks. The comment adds: > > As far as I know, there are no use programs that make

[PATCH] ACPI / PCI: Bail early in acpi_pci_add_bus() if there is no ACPI handle

Hyper-V instances support PCI pass-through which is implemented through PV pci-hyperv driver. When a device is passed through a new root PCI bus is created in the guest. The bus sits on top of VMBus and has no associated information in ACPI. acpi_pci_add_bus() in this case proceeds all the way to

[PATCH] ACPI / PCI: Bail early in acpi_pci_add_bus() if there is no ACPI handle

Hyper-V instances support PCI pass-through which is implemented through PV pci-hyperv driver. When a device is passed through a new root PCI bus is created in the guest. The bus sits on top of VMBus and has no associated information in ACPI. acpi_pci_add_bus() in this case proceeds all the way to

Re: [RFC PATCH 3/4] x86/asm: Make alternative macro interfaces more clear and consistent

On Sat, Sep 02, 2017 at 12:32:21PM +0200, Ingo Molnar wrote: > > * Josh Poimboeuf wrote: > > > On Thu, Aug 31, 2017 at 12:25:42PM -0500, Josh Poimboeuf wrote: > > > 2) Put "sp" in the clobbers list instead of as an i/o constraint. This > > >mostly works for GCC, and

Re: [RFC PATCH 3/4] x86/asm: Make alternative macro interfaces more clear and consistent

On Sat, Sep 02, 2017 at 12:32:21PM +0200, Ingo Molnar wrote: > > * Josh Poimboeuf wrote: > > > On Thu, Aug 31, 2017 at 12:25:42PM -0500, Josh Poimboeuf wrote: > > > 2) Put "sp" in the clobbers list instead of as an i/o constraint. This > > >mostly works for GCC, and doesn't break clang.

Re: [PATCH] scsi: lpfc: remove redundant null check on eqe

On 9/8/2017 1:02 AM, Colin King wrote: From: Colin Ian King The pointer eqe is always non-null inside the while loop, so the check to see if eqe is NULL is redudant and hence can be removed. Detected by CoverityScan CID#1248693 ("Logically Dead Code") Signed-off-by:

Re: [PATCH] scsi: lpfc: remove redundant null check on eqe

On 9/8/2017 1:02 AM, Colin King wrote: From: Colin Ian King The pointer eqe is always non-null inside the while loop, so the check to see if eqe is NULL is redudant and hence can be removed. Detected by CoverityScan CID#1248693 ("Logically Dead Code") Signed-off-by: Colin Ian King Yep.

Re: [Intel-wired-lan] [PATCH] igb: check memory allocation failure

On 9/13/17 7:24 PM, Brown, Aaron F wrote: >> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On Behalf >> Of Christophe JAILLET >> Sent: Monday, August 28, 2017 10:13 AM >> To: Waskiewicz Jr, Peter ; Kirsher, Jeffrey T >>

Re: [Intel-wired-lan] [PATCH] igb: check memory allocation failure

On 9/13/17 7:24 PM, Brown, Aaron F wrote: >> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On Behalf >> Of Christophe JAILLET >> Sent: Monday, August 28, 2017 10:13 AM >> To: Waskiewicz Jr, Peter ; Kirsher, Jeffrey T >> >> Cc: net...@vger.kernel.org;

Re: [PATCH] selftests: intel_pstate: compile programs if executable not found

On 09/14/2017 08:42 AM, Shuah Khan wrote: > Hi Naresh, > > On 09/14/2017 04:51 AM, naresh.kamb...@linaro.org wrote: >> From: Naresh Kamboju >> >> Test exit due to aperf.c: No such file or directory >> ./run.sh >> gcc: error: aperf.c: No such file or directory >>

Re: [PATCH] selftests: intel_pstate: compile programs if executable not found

On 09/14/2017 08:42 AM, Shuah Khan wrote: > Hi Naresh, > > On 09/14/2017 04:51 AM, naresh.kamb...@linaro.org wrote: >> From: Naresh Kamboju >> >> Test exit due to aperf.c: No such file or directory >> ./run.sh >> gcc: error: aperf.c: No such file or directory >> Problem compiling aperf.c. >> >

Re: [PATCH v1 1/2] watchdog: dw_wdt: add stop watchdog operation

On Thu, Sep 14, 2017 at 10:14:01AM +0200, Oleksij Rempel wrote: > From: Steffen Trumtrar > > The only way of stopping the watchdog is by resetting it. > Add the watchdog op for stopping the device and reset if > a reset line is provided. > > Signed-off-by: Steffen

Re: [PATCH v1 1/2] watchdog: dw_wdt: add stop watchdog operation

On Thu, Sep 14, 2017 at 10:14:01AM +0200, Oleksij Rempel wrote: > From: Steffen Trumtrar > > The only way of stopping the watchdog is by resetting it. > Add the watchdog op for stopping the device and reset if > a reset line is provided. > > Signed-off-by: Steffen Trumtrar > Signed-off-by:

Re: [PATCH] selftests: intel_pstate: compile programs if executable not found

Hi Naresh, On 09/14/2017 04:51 AM, naresh.kamb...@linaro.org wrote: > From: Naresh Kamboju > > Test exit due to aperf.c: No such file or directory > ./run.sh > gcc: error: aperf.c: No such file or directory > Problem compiling aperf.c. > Please give me more details

Re: [PATCH] selftests: intel_pstate: compile programs if executable not found

Hi Naresh, On 09/14/2017 04:51 AM, naresh.kamb...@linaro.org wrote: > From: Naresh Kamboju > > Test exit due to aperf.c: No such file or directory > ./run.sh > gcc: error: aperf.c: No such file or directory > Problem compiling aperf.c. > Please give me more details on where do you see this

Re: [PATCH] net/packet: fix race condition between fanout_add and __unregister_prot_hook

On Thu, Sep 14, 2017 at 10:07 AM, nixiaoming wrote: > From: l00219569 > > If fanout_add is preempted after running po-> fanout = match > and before running __fanout_link, > it will cause BUG_ON when __unregister_prot_hook call __fanout_unlink > > so, we

Re: [PATCH] net/packet: fix race condition between fanout_add and __unregister_prot_hook

On Thu, Sep 14, 2017 at 10:07 AM, nixiaoming wrote: > From: l00219569 > > If fanout_add is preempted after running po-> fanout = match > and before running __fanout_link, > it will cause BUG_ON when __unregister_prot_hook call __fanout_unlink > > so, we need add mutex_lock(_mutex) to

Re: [RFC Part2 PATCH v3 24/26] KVM: SVM: Clear C-bit from the page fault address

On Mon, Jul 24, 2017 at 03:03:01PM -0500, Brijesh Singh wrote: > When SEV is active, on #NPF the page fault address will contain C-bit. "... contain the C-bit." > We must clear the C-bit before handling the fault. > > Signed-off-by: Brijesh Singh > --- >

Re: [RFC Part2 PATCH v3 24/26] KVM: SVM: Clear C-bit from the page fault address

On Mon, Jul 24, 2017 at 03:03:01PM -0500, Brijesh Singh wrote: > When SEV is active, on #NPF the page fault address will contain C-bit. "... contain the C-bit." > We must clear the C-bit before handling the fault. > > Signed-off-by: Brijesh Singh > --- > arch/x86/kvm/svm.c | 2 +- > 1 file

Re: keyboard backlight max_brightness bug on Dell Latitude E6410

2017-09-14 15:54 GMT+02:00 Pali Rohár : > Adding Gabriele to thread, IIRC you have machine which uses > "supported keyboard light brightness levels" > Can you look at this bug, if your machine is affected by it too? My keyboard has two brightness levels + off. The value of

Re: keyboard backlight max_brightness bug on Dell Latitude E6410

2017-09-14 15:54 GMT+02:00 Pali Rohár : > Adding Gabriele to thread, IIRC you have machine which uses > "supported keyboard light brightness levels" > Can you look at this bug, if your machine is affected by it too? My keyboard has two brightness levels + off. The value of max_brightness is 2, as

RE: keyboard backlight max_brightness bug on Dell Latitude E6410

I've also been updating https://bugzilla.kernel.org/show_bug.cgi?id=196913 btw. What source file is responsible for setting this; led-class.c? I would like to know, so I can tell it to use the correct value: max_brightness = supported_brightness_levels-1; // !actual_max_brightness+1 :) #

Re: [PATCH v2] kbuild: (bin)rpm-pkg: fix version number handling

Hi Riku. 2017-09-14 22:10 GMT+09:00 Riku Voipio : > On 14 September 2017 at 14:26, Masahiro Yamada > wrote: >> The "Release:" field of the spec file is determined based on the >> .version file. >> >> However, the .version file is not copied

RE: keyboard backlight max_brightness bug on Dell Latitude E6410

I've also been updating https://bugzilla.kernel.org/show_bug.cgi?id=196913 btw. What source file is responsible for setting this; led-class.c? I would like to know, so I can tell it to use the correct value: max_brightness = supported_brightness_levels-1; // !actual_max_brightness+1 :) #

Re: [PATCH v2] kbuild: (bin)rpm-pkg: fix version number handling

Hi Riku. 2017-09-14 22:10 GMT+09:00 Riku Voipio : > On 14 September 2017 at 14:26, Masahiro Yamada > wrote: >> The "Release:" field of the spec file is determined based on the >> .version file. >> >> However, the .version file is not copied to the source tar file. >> So, when we build the kernel

Re: [PATCH v1 1/4] perf annotate: create a new hists to manage multiple events samples

On 9/14/2017 10:05 PM, Arnaldo Carvalho de Melo wrote: > Em Thu, Sep 14, 2017 at 09:03:55AM +0800, Jin, Yao escreveu: >> On 9/11/2017 9:33 AM, Jin, Yao wrote: >>> On 9/8/2017 9:43 PM, Arnaldo Carvalho de Melo wrote: Em Wed, Aug 16, 2017 at 06:18:33PM +0800, Jin Yao escreveu: > An issue

[PATCH v4 1/5] dt-bindings: i2c-stm32: Document the STM32F7 I2C bindings

This patch adds the documentation of device tree bindings for STM32F7 I2C Signed-off-by: M'boumba Cedric Madianga Signed-off-by: Pierre-Yves MORDRET Acked-by: Rob Herring --- Version history: v4: v3: *

Re: [PATCH v1 1/4] perf annotate: create a new hists to manage multiple events samples

On 9/14/2017 10:05 PM, Arnaldo Carvalho de Melo wrote: > Em Thu, Sep 14, 2017 at 09:03:55AM +0800, Jin, Yao escreveu: >> On 9/11/2017 9:33 AM, Jin, Yao wrote: >>> On 9/8/2017 9:43 PM, Arnaldo Carvalho de Melo wrote: Em Wed, Aug 16, 2017 at 06:18:33PM +0800, Jin Yao escreveu: > An issue

[PATCH v4 1/5] dt-bindings: i2c-stm32: Document the STM32F7 I2C bindings

This patch adds the documentation of device tree bindings for STM32F7 I2C Signed-off-by: M'boumba Cedric Madianga Signed-off-by: Pierre-Yves MORDRET Acked-by: Rob Herring --- Version history: v4: v3: * None v2: * Remove i2c-timing binding in order to use generic

[PATCH v4 0/5] Add support for the STM32F7 I2C

This patchset adds support for the I2C controller embedded in STM32F7xx SoC. It enables I2C transfer in interrupt mode with Standard-mode, Fast-mode and Fast-mode+ bus speed. --- Version history: v4: * Fix max I2C Bus clock to 100% * Solve typo issue * Add retries

[PATCH v4 0/5] Add support for the STM32F7 I2C

This patchset adds support for the I2C controller embedded in STM32F7xx SoC. It enables I2C transfer in interrupt mode with Standard-mode, Fast-mode and Fast-mode+ bus speed. --- Version history: v4: * Fix max I2C Bus clock to 100% * Solve typo issue * Add retries

[PATCH v4 4/5] ARM: dts: stm32: Add I2C1 support for STM32F746 SoC

This patch adds I2C1 support for STM32F746 SoC. Signed-off-by: M'boumba Cedric Madianga Signed-off-by: Pierre-Yves MORDRET --- Version history: v4: v3: * None v2: * Update I2C SoC device tree with latest Linux

[PATCH v4 4/5] ARM: dts: stm32: Add I2C1 support for STM32F746 SoC

This patch adds I2C1 support for STM32F746 SoC. Signed-off-by: M'boumba Cedric Madianga Signed-off-by: Pierre-Yves MORDRET --- Version history: v4: v3: * None v2: * Update I2C SoC device tree with latest Linux version --- --- arch/arm/boot/dts/stm32f746.dtsi | 22

[PATCH v4 2/5] i2c: i2c-stm32f4: use generic definition of speed enum

This patch uses a more generic definition of speed enum for i2c-stm32f4 driver. Signed-off-by: M'boumba Cedric Madianga Signed-off-by: Pierre-Yves MORDRET Reviewed-by: Ludovic BARRE --- Version history: v4:

[PATCH v4 2/5] i2c: i2c-stm32f4: use generic definition of speed enum

This patch uses a more generic definition of speed enum for i2c-stm32f4 driver. Signed-off-by: M'boumba Cedric Madianga Signed-off-by: Pierre-Yves MORDRET Reviewed-by: Ludovic BARRE --- Version history: v4: v3: v2: * None --- --- drivers/i2c/busses/i2c-stm32.h | 20

[PATCH 2/3] ARM: dts: at91: sama5d27_som1_ek: fix typos

From: Ludovic Desroches Fix typos that prevent proper using of uart2 and uart4 devices. Signed-off-by: Ludovic Desroches Signed-off-by: Claudiu Beznea ---

[PATCH 2/3] ARM: dts: at91: sama5d27_som1_ek: fix typos

From: Ludovic Desroches Fix typos that prevent proper using of uart2 and uart4 devices. Signed-off-by: Ludovic Desroches Signed-off-by: Claudiu Beznea --- arch/arm/boot/dts/at91-sama5d27_som1_ek.dts | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH 1/3] ARM: dts: at91: sama5d27_som1_ek: update pinmux/pinconf for LEDs and USB

From: Ludovic Desroches There are some changes from the prototype board concerning LEDs and USB pins: - USBB power enable and red LED pins are inverted. - The polarity of LEDs is inverted too. Signed-off-by: Ludovic Desroches

[PATCH 1/3] ARM: dts: at91: sama5d27_som1_ek: update pinmux/pinconf for LEDs and USB

From: Ludovic Desroches There are some changes from the prototype board concerning LEDs and USB pins: - USBB power enable and red LED pins are inverted. - The polarity of LEDs is inverted too. Signed-off-by: Ludovic Desroches Signed-off-by: Claudiu Beznea ---

[PATCH 0/3] SoM1 EK board fixes

Hi, This series contains fixes for SAMA5D27 SoM1 EK board. It would be good if we will have this in 4.14 version. Thank you, Claudiu Ludovic Desroches (2): ARM: dts: at91: sama5d27_som1_ek: update pinmux/pinconf for LEDs and USB ARM: dts: at91: sama5d27_som1_ek: fix typos Nicolas Ferre

[PATCH 0/3] SoM1 EK board fixes

Hi, This series contains fixes for SAMA5D27 SoM1 EK board. It would be good if we will have this in 4.14 version. Thank you, Claudiu Ludovic Desroches (2): ARM: dts: at91: sama5d27_som1_ek: update pinmux/pinconf for LEDs and USB ARM: dts: at91: sama5d27_som1_ek: fix typos Nicolas Ferre

[PATCH 3/3] ARM: dts: at91: sama5d27_som1_ek: fix USB host vbus

From: Nicolas Ferre The USB host has 3 ports so we must specify the entries for each in the atmel,vbus-gpio property. The specified pin (PA27) is the vbus for USBB and not USBA. Signed-off-by: Nicolas Ferre

[PATCH 3/3] ARM: dts: at91: sama5d27_som1_ek: fix USB host vbus

From: Nicolas Ferre The USB host has 3 ports so we must specify the entries for each in the atmel,vbus-gpio property. The specified pin (PA27) is the vbus for USBB and not USBA. Signed-off-by: Nicolas Ferre [claudiu.bez...@microchip.com: change subject to match the desired prefix]

[PATCH v4 3/5] i2c: i2c-stm32f7: add driver

This patch adds initial support for the STM32F7 I2C controller. Signed-off-by: M'boumba Cedric Madianga Signed-off-by: Pierre-Yves MORDRET --- Version history: v4: * Fix max I2C Bus clock to 100% * Solve typo issue

[PATCH v4 3/5] i2c: i2c-stm32f7: add driver

This patch adds initial support for the STM32F7 I2C controller. Signed-off-by: M'boumba Cedric Madianga Signed-off-by: Pierre-Yves MORDRET --- Version history: v4: * Fix max I2C Bus clock to 100% * Solve typo issue * Add retries value v3: * Move

[PATCH v4 5/5] ARM: dts: stm32: Add I2C1 support for STM32F746 eval board

This patch adds I2C1 support for STM32F746 eval board Signed-off-by: M'boumba Cedric Madianga Signed-off-by: Pierre-Yves MORDRET --- Version history: v4: v3: * None v2: * Add SCL Rising/Falling time for eval

[PATCH v4 5/5] ARM: dts: stm32: Add I2C1 support for STM32F746 eval board

This patch adds I2C1 support for STM32F746 eval board Signed-off-by: M'boumba Cedric Madianga Signed-off-by: Pierre-Yves MORDRET --- Version history: v4: v3: * None v2: * Add SCL Rising/Falling time for eval board --- --- arch/arm/boot/dts/stm32746g-eval.dts | 8

[PATCH v2] ARC: reset: introduce AXS10x reset driver

ARC AXS10x boards support custom IP-block which allows to control reset signals of selected peripherals. For example DW GMAC, etc... This block is controlled via memory-mapped register (AKA CREG) which represents up-to 32 reset lines. This regiter is self-clearing so we don't need to deassert line

Re: [PATCH] staging: iio: ad7192: Use the dedicated reset function

On 14.09.2017 15:50, Stefan Popa wrote: SPI host drivers can use DMA to transfer data, so the buffer should be properly allocated. Keeping it on the stack could cause an undefined behavior. The dedicated reset function solves this issue. Signed-off-by: Stefan Popa

[PATCH v2] ARC: reset: introduce AXS10x reset driver

ARC AXS10x boards support custom IP-block which allows to control reset signals of selected peripherals. For example DW GMAC, etc... This block is controlled via memory-mapped register (AKA CREG) which represents up-to 32 reset lines. This regiter is self-clearing so we don't need to deassert line

Re: [PATCH] staging: iio: ad7192: Use the dedicated reset function

On 14.09.2017 15:50, Stefan Popa wrote: SPI host drivers can use DMA to transfer data, so the buffer should be properly allocated. Keeping it on the stack could cause an undefined behavior. The dedicated reset function solves this issue. Signed-off-by: Stefan Popa Acked-by: Michael

[PATCH] net/packet: fix race condition between fanout_add and __unregister_prot_hook

From: l00219569 If fanout_add is preempted after running po-> fanout = match and before running __fanout_link, it will cause BUG_ON when __unregister_prot_hook call __fanout_unlink so, we need add mutex_lock(_mutex) to __unregister_prot_hook or add spin_lock(>bind_lock)

[PATCH] net/packet: fix race condition between fanout_add and __unregister_prot_hook

From: l00219569 If fanout_add is preempted after running po-> fanout = match and before running __fanout_link, it will cause BUG_ON when __unregister_prot_hook call __fanout_unlink so, we need add mutex_lock(_mutex) to __unregister_prot_hook or add spin_lock(>bind_lock) before po-> fanout =

[PATCH] mtd: cfi_cmdset_0002: fix Cypress S29GL flash erase suspend

On UBIFS, Cypress S29GL01GT flash is failed to access occasionally , and throw below error information and call trace: MTD get_chip(): chip not ready after erase suspend UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 932:36992, written 0 bytes Call Trace: [jiffies: 0x1ad9b]

[PATCH] mtd: cfi_cmdset_0002: fix Cypress S29GL flash erase suspend

On UBIFS, Cypress S29GL01GT flash is failed to access occasionally , and throw below error information and call trace: MTD get_chip(): chip not ready after erase suspend UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 932:36992, written 0 bytes Call Trace: [jiffies: 0x1ad9b]

Helloo

Helloo

[tip:core/urgent] tools/objtool: Fix memory leak in elf_create_rela_section()

Commit-ID: 5d0be52d44e32ae98b1345e9ecfa6a97783ca2c9 Gitweb: http://git.kernel.org/tip/5d0be52d44e32ae98b1345e9ecfa6a97783ca2c9 Author: Martin Kepplinger AuthorDate: Thu, 14 Sep 2017 08:01:38 +0200 Committer: Ingo Molnar CommitDate: Thu, 14 Sep 2017

[tip:core/urgent] tools/objtool: Fix memory leak in elf_create_rela_section()

Commit-ID: 5d0be52d44e32ae98b1345e9ecfa6a97783ca2c9 Gitweb: http://git.kernel.org/tip/5d0be52d44e32ae98b1345e9ecfa6a97783ca2c9 Author: Martin Kepplinger AuthorDate: Thu, 14 Sep 2017 08:01:38 +0200 Committer: Ingo Molnar CommitDate: Thu, 14 Sep 2017 16:02:30 +0200 tools/objtool: Fix

WINNING NOTIFICATION

Congratulation you have won 85,000,000.00GBP For Claim email:i...@winningsclaimsoffice.com

WINNING NOTIFICATION

Congratulation you have won 85,000,000.00GBP For Claim email:i...@winningsclaimsoffice.com

Re: [RFC Part2 PATCH v3 23/26] KVM: X86: Add memory encryption enabled ops

On Mon, Jul 24, 2017 at 03:03:00PM -0500, Brijesh Singh wrote: > Extend kvm_x86_ops to add memory_encyption_enabled() ops. > It returns a > boolean indicating whether memory encryption is enabled on the VCPU. You don't need that sentence. > > Signed-off-by: Brijesh Singh

Re: [RFC Part2 PATCH v3 23/26] KVM: X86: Add memory encryption enabled ops

On Mon, Jul 24, 2017 at 03:03:00PM -0500, Brijesh Singh wrote: > Extend kvm_x86_ops to add memory_encyption_enabled() ops. > It returns a > boolean indicating whether memory encryption is enabled on the VCPU. You don't need that sentence. > > Signed-off-by: Brijesh Singh > --- >

Re: [PATCH] xen: don't compile pv-specific parts if XEN_PV isn't configured

>> Did you make any changes in xenbus_map_ring_valloc_pv()? I don't see any >> but the diff looks pretty big --- I'd expect only the preprocessor >> directives to show up. > I moved the functions to require only one #ifdef (plus 1 for setting > the pv variants). Oh, OK, I didn't notice that.

Re: [PATCH] xen: don't compile pv-specific parts if XEN_PV isn't configured

>> Did you make any changes in xenbus_map_ring_valloc_pv()? I don't see any >> but the diff looks pretty big --- I'd expect only the preprocessor >> directives to show up. > I moved the functions to require only one #ifdef (plus 1 for setting > the pv variants). Oh, OK, I didn't notice that.

Re: [PATCH V6 3/5] PCI: thunder-pem: Allow to probe PEM-specific register range for ACPI case

(remove most cc's) Hi all, Apologies for digging up this old thread. I am currently looking into whether it is feasible to refactor some of the ACPI PCI quirk code we have so it can apply to more instances of the Synopsys Designware PCIe (i.e., for Marvell and Socionext SOCs), which all suffer

Re: [PATCH V6 3/5] PCI: thunder-pem: Allow to probe PEM-specific register range for ACPI case

(remove most cc's) Hi all, Apologies for digging up this old thread. I am currently looking into whether it is feasible to refactor some of the ACPI PCI quirk code we have so it can apply to more instances of the Synopsys Designware PCIe (i.e., for Marvell and Socionext SOCs), which all suffer

Re: [PATCH v1 1/4] perf annotate: create a new hists to manage multiple events samples

Em Thu, Sep 14, 2017 at 09:03:55AM +0800, Jin, Yao escreveu: > On 9/11/2017 9:33 AM, Jin, Yao wrote: > > On 9/8/2017 9:43 PM, Arnaldo Carvalho de Melo wrote: > >> Em Wed, Aug 16, 2017 at 06:18:33PM +0800, Jin Yao escreveu: > >>> An issue is found during using perf annotate. > >>> > >>> perf record

Re: [PATCH v1 1/4] perf annotate: create a new hists to manage multiple events samples

Em Thu, Sep 14, 2017 at 09:03:55AM +0800, Jin, Yao escreveu: > On 9/11/2017 9:33 AM, Jin, Yao wrote: > > On 9/8/2017 9:43 PM, Arnaldo Carvalho de Melo wrote: > >> Em Wed, Aug 16, 2017 at 06:18:33PM +0800, Jin Yao escreveu: > >>> An issue is found during using perf annotate. > >>> > >>> perf record

[PATCH] ALSA: oxygen: Xonar DG(X): make model_xonar_dg const

Make this const as it not modified anywhere. It is only used during a copy operation. Also, add const to the declaration in header. Signed-off-by: Bhumika Goyal --- sound/pci/oxygen/xonar_dg.h | 2 +- sound/pci/oxygen/xonar_dg_mixer.c | 2 +- 2 files changed, 2

[PATCH] ALSA: oxygen: Xonar DG(X): make model_xonar_dg const

Make this const as it not modified anywhere. It is only used during a copy operation. Also, add const to the declaration in header. Signed-off-by: Bhumika Goyal --- sound/pci/oxygen/xonar_dg.h | 2 +- sound/pci/oxygen/xonar_dg_mixer.c | 2 +- 2 files changed, 2 insertions(+), 2

Re: [PATCH] xen: don't compile pv-specific parts if XEN_PV isn't configured

On 14/09/17 16:00, Boris Ostrovsky wrote: > On 09/14/2017 08:38 AM, Juergen Gross wrote: >> xenbus_client.c contains some functions specific for pv guests. >> Enclose them with #ifdef CONFIG_XEN_PV to avoid compiling them when >> they are not needed (e.g. on ARM). >> >> Signed-off-by: Juergen

Re: [PATCH] xen: don't compile pv-specific parts if XEN_PV isn't configured

On 14/09/17 16:00, Boris Ostrovsky wrote: > On 09/14/2017 08:38 AM, Juergen Gross wrote: >> xenbus_client.c contains some functions specific for pv guests. >> Enclose them with #ifdef CONFIG_XEN_PV to avoid compiling them when >> they are not needed (e.g. on ARM). >> >> Signed-off-by: Juergen

[PATCH] lib: add module support to string tests

Extract the string test code into its own source file, to allow to compile it either to a loadable module, or builtin into the kernel. Fixes: 03270c13c5ffaa6a ("lib/string.c: add testcases for memset16/32/64") Signed-off-by: Geert Uytterhoeven --- lib/Kconfig | 2

[PATCH] lib: add module support to string tests

Extract the string test code into its own source file, to allow to compile it either to a loadable module, or builtin into the kernel. Fixes: 03270c13c5ffaa6a ("lib/string.c: add testcases for memset16/32/64") Signed-off-by: Geert Uytterhoeven --- lib/Kconfig | 2 +- lib/Makefile |

Re: [PATCH] xen: don't compile pv-specific parts if XEN_PV isn't configured

On 09/14/2017 08:38 AM, Juergen Gross wrote: > xenbus_client.c contains some functions specific for pv guests. > Enclose them with #ifdef CONFIG_XEN_PV to avoid compiling them when > they are not needed (e.g. on ARM). > > Signed-off-by: Juergen Gross > --- >

Re: [PATCH] xen: don't compile pv-specific parts if XEN_PV isn't configured

On 09/14/2017 08:38 AM, Juergen Gross wrote: > xenbus_client.c contains some functions specific for pv guests. > Enclose them with #ifdef CONFIG_XEN_PV to avoid compiling them when > they are not needed (e.g. on ARM). > > Signed-off-by: Juergen Gross > --- > drivers/xen/xenbus/xenbus_client.c |

<    4   5   6   7   8   9   10   11   12   13   >