Re: [PATCH v1 04/10] staging: iio: cdc: ad7152: Remove exceptional & on function name

On 11/03/17 14:26, simran singhal wrote: > Remove & from function pointers to conform to the style found elsewhere > in the file. Done using the following semantic patch > > // > @r@ > identifier f; > @@ > > f(...) { ... } > @@ > identifier r.f; > @@ > > - > + f > // > > Signed-off-by:

Re: [PATCH v1 04/10] staging: iio: cdc: ad7152: Remove exceptional & on function name

On 11/03/17 14:26, simran singhal wrote: > Remove & from function pointers to conform to the style found elsewhere > in the file. Done using the following semantic patch > > // > @r@ > identifier f; > @@ > > f(...) { ... } > @@ > identifier r.f; > @@ > > - > + f > // > > Signed-off-by:

Re: [PATCH v1 03/10] staging: iio: cdc: ad7746: Remove exceptional & on function name

On 11/03/17 14:26, simran singhal wrote: > Remove & from function pointers to conform to the style found elsewhere > in the file. Done using the following semantic patch > > // > @r@ > identifier f; > @@ > > f(...) { ... } > @@ > identifier r.f; > @@ > > - > + f > // > > Signed-off-by:

Re: [PATCH v1 03/10] staging: iio: cdc: ad7746: Remove exceptional & on function name

On 11/03/17 14:26, simran singhal wrote: > Remove & from function pointers to conform to the style found elsewhere > in the file. Done using the following semantic patch > > // > @r@ > identifier f; > @@ > > f(...) { ... } > @@ > identifier r.f; > @@ > > - > + f > // > > Signed-off-by:

Re: [PATCH v1 02/10] staging: iio: ad7780: Remove exceptional & on function name

On 11/03/17 14:26, simran singhal wrote: > Remove & from function pointers to conform to the style found elsewhere > in the file. Done using the following semantic patch > > // > @r@ > identifier f; > @@ > > f(...) { ... } > @@ > identifier r.f; > @@ > > - > + f > // > > Signed-off-by:

Re: [PATCH v1 02/10] staging: iio: ad7780: Remove exceptional & on function name

On 11/03/17 14:26, simran singhal wrote: > Remove & from function pointers to conform to the style found elsewhere > in the file. Done using the following semantic patch > > // > @r@ > identifier f; > @@ > > f(...) { ... } > @@ > identifier r.f; > @@ > > - > + f > // > > Signed-off-by:

Re: [PATCH v1 01/10] staging: iio: ad7192: Remove exceptional & on function name

On 11/03/17 14:26, simran singhal wrote: > Remove & from function pointers to conform to the style found elsewhere > in the file. Done using the following semantic patch > > // > @r@ > identifier f; > @@ > > f(...) { ... } > @@ > identifier r.f; > @@ > > - > + f > // > > Signed-off-by:

Re: [PATCH v1 01/10] staging: iio: ad7192: Remove exceptional & on function name

On 11/03/17 14:26, simran singhal wrote: > Remove & from function pointers to conform to the style found elsewhere > in the file. Done using the following semantic patch > > // > @r@ > identifier f; > @@ > > f(...) { ... } > @@ > identifier r.f; > @@ > > - > + f > // > > Signed-off-by:

Re: [PATCH v1 00/10] staging: iio: Remove exceptional & on functions name

On 11/03/17 14:26, simran singhal wrote: > This patch-series removes exceptional & on functions name. > > v1: > -Change the commit message of all the patches of the patch-series Usual convention is to call the first (unlabelled) revision v1 implicitly which would have made this V2. Doesn't

Re: [PATCH v1 00/10] staging: iio: Remove exceptional & on functions name

On 11/03/17 14:26, simran singhal wrote: > This patch-series removes exceptional & on functions name. > > v1: > -Change the commit message of all the patches of the patch-series Usual convention is to call the first (unlabelled) revision v1 implicitly which would have made this V2. Doesn't

Re: [PATCH v2] iio: multiplexer: fix unsigned check with less than zero

On 08/03/17 13:28, Peter Rosin wrote: > Comparing a size_t with less than zero is always false as size_t > is unsigned. So, change the type of the variable to ssize_t and > replicate the size check from mux_configure_channel() into > mux_write_ext_info() thus ensuring that the size will fit in the

Re: [PATCH v2] iio: multiplexer: fix unsigned check with less than zero

On 08/03/17 13:28, Peter Rosin wrote: > Comparing a size_t with less than zero is always false as size_t > is unsigned. So, change the type of the variable to ssize_t and > replicate the size check from mux_configure_channel() into > mux_write_ext_info() thus ensuring that the size will fit in the

[PATCH v2 4/4] phy: exynos: Use one define for enable bit

There is no need for separate defines for Exynos4 and Exynos5 phy enable bit and MIPI phy reset bits. In both cases there are the same so simplify it. This reduces number of defines and allows removal of one header file. Signed-off-by: Krzysztof Kozlowski Acked-by: Lee Jones

[PATCH v2 4/4] phy: exynos: Use one define for enable bit

There is no need for separate defines for Exynos4 and Exynos5 phy enable bit and MIPI phy reset bits. In both cases there are the same so simplify it. This reduces number of defines and allows removal of one header file. Signed-off-by: Krzysztof Kozlowski Acked-by: Lee Jones ---

[PATCH v2 2/4] phy: exynos5: Remove duplicated defines of PHY register defines

Phy drivers access PMU region through regmap provided by exynos-pmu driver. However there is no need to duplicate defines for PMU registers. Instead just use whatever is defined in exynos-regs-pmu.h. This reduces number of defines and allows removal of one header. Suggested-by: Marek

[PATCH v2 2/4] phy: exynos5: Remove duplicated defines of PHY register defines

Phy drivers access PMU region through regmap provided by exynos-pmu driver. However there is no need to duplicate defines for PMU registers. Instead just use whatever is defined in exynos-regs-pmu.h. This reduces number of defines and allows removal of one header. Suggested-by: Marek

[PATCH v2 1/4] phy: exynos4: Remove duplicated defines of PHY register defines

Phy drivers access PMU region through regmap provided by exynos-pmu driver. However there is no need to duplicate defines for PMU registers. Instead just use whatever is defined in exynos-regs-pmu.h. Additionally MIPI PHY registers for Exynos5433 start from the same address as Exynos4 and

[PATCH v2 3/4] phy: exynos-mipi-video: Use consistent method to address phy registers

Exynos4 MIPI phy registers are defined with macro calculating the offset for given phyN. Use the same method for Exynos5420 to be consistent. Signed-off-by: Krzysztof Kozlowski --- drivers/phy/phy-exynos-mipi-video.c | 20 ++--

[PATCH v2 3/4] phy: exynos-mipi-video: Use consistent method to address phy registers

Exynos4 MIPI phy registers are defined with macro calculating the offset for given phyN. Use the same method for Exynos5420 to be consistent. Signed-off-by: Krzysztof Kozlowski --- drivers/phy/phy-exynos-mipi-video.c | 20 ++--

[PATCH v2 1/4] phy: exynos4: Remove duplicated defines of PHY register defines

Phy drivers access PMU region through regmap provided by exynos-pmu driver. However there is no need to duplicate defines for PMU registers. Instead just use whatever is defined in exynos-regs-pmu.h. Additionally MIPI PHY registers for Exynos5433 start from the same address as Exynos4 and

[PATCH v2 0/4] phy/mfd/soc: exynos: Header cleanup

Suggested by Marek, continuation of cleanup of PMU register defines in headers. Let's keep all of them in include/linux/soc/samsung/exynos-regs-pmu.h. Merging strategy: probably through phy tree (in that case they have samsung-soc's ack). I can also take it through samsung-soc - please let me

[PATCH v2 0/4] phy/mfd/soc: exynos: Header cleanup

Suggested by Marek, continuation of cleanup of PMU register defines in headers. Let's keep all of them in include/linux/soc/samsung/exynos-regs-pmu.h. Merging strategy: probably through phy tree (in that case they have samsung-soc's ack). I can also take it through samsung-soc - please let me

Re: [PATCH] Staging: iio: return expression instead of return ret

On 10/03/17 03:57, Bo Yu wrote: > The following Coccinelle script was used to detect this: > > @@ > local idexpression ret; > expression e; > @@ > > -ret = > +return > e; > -return ret; A bit of fuzz on this one. Presumably things moving around in other recent changes. Anyhow, applied to

Re: [PATCH] Staging: iio: return expression instead of return ret

On 10/03/17 03:57, Bo Yu wrote: > The following Coccinelle script was used to detect this: > > @@ > local idexpression ret; > expression e; > @@ > > -ret = > +return > e; > -return ret; A bit of fuzz on this one. Presumably things moving around in other recent changes. Anyhow, applied to

Re: [PATCH v5 21/39] UAPI: Add media UAPI Kbuild file

On 03/11/2017 05:49 AM, Sakari Ailus wrote: Hi Steve, On Thu, Mar 09, 2017 at 08:53:01PM -0800, Steve Longerbeam wrote: Add an empty UAPI Kbuild file for media UAPI headers. Signed-off-by: Steve Longerbeam The existing V4L2 UAPI headers are under

Re: [PATCH v5 21/39] UAPI: Add media UAPI Kbuild file

On 03/11/2017 05:49 AM, Sakari Ailus wrote: Hi Steve, On Thu, Mar 09, 2017 at 08:53:01PM -0800, Steve Longerbeam wrote: Add an empty UAPI Kbuild file for media UAPI headers. Signed-off-by: Steve Longerbeam The existing V4L2 UAPI headers are under include/uapi/linux. Could you use that

Re: [PATCH v5 15/39] [media] v4l2: add a frame interval error event

On 03/11/2017 03:39 AM, Hans Verkuil wrote: On 10/03/17 19:37, Steve Longerbeam wrote: Hi Hans, On 03/10/2017 04:03 AM, Hans Verkuil wrote: On 10/03/17 05:52, Steve Longerbeam wrote: Add a new FRAME_INTERVAL_ERROR event to signal that a video capture or output device has measured an

Re: [PATCH v5 15/39] [media] v4l2: add a frame interval error event

On 03/11/2017 03:39 AM, Hans Verkuil wrote: On 10/03/17 19:37, Steve Longerbeam wrote: Hi Hans, On 03/10/2017 04:03 AM, Hans Verkuil wrote: On 10/03/17 05:52, Steve Longerbeam wrote: Add a new FRAME_INTERVAL_ERROR event to signal that a video capture or output device has measured an

Re: [PATCH v4 14/36] [media] v4l2-mc: add a function to inherit controls from a pipeline

On 03/11/2017 07:32 AM, Sakari Ailus wrote: Hi Mauro and Hans, On Sat, Mar 11, 2017 at 10:14:08AM -0300, Mauro Carvalho Chehab wrote: Em Sat, 11 Mar 2017 12:32:43 +0100 Hans Verkuil escreveu: On 10/03/17 16:09, Mauro Carvalho Chehab wrote: Em Fri, 10 Mar 2017 13:54:28

Re: [PATCH v4 14/36] [media] v4l2-mc: add a function to inherit controls from a pipeline

On 03/11/2017 07:32 AM, Sakari Ailus wrote: Hi Mauro and Hans, On Sat, Mar 11, 2017 at 10:14:08AM -0300, Mauro Carvalho Chehab wrote: Em Sat, 11 Mar 2017 12:32:43 +0100 Hans Verkuil escreveu: On 10/03/17 16:09, Mauro Carvalho Chehab wrote: Em Fri, 10 Mar 2017 13:54:28 +0100 Hans Verkuil

[RESEND] drm/exynos: Remove support for Exynos4415 (SoC not supported anymore)

Support for Exynos4415 is going away because there are no internal nor external users. Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), the platform cannot be instantiated so remove also the drivers. Signed-off-by: Krzysztof Kozlowski Acked-by: Kukjin Kim

[RESEND] drm/exynos: Remove support for Exynos4415 (SoC not supported anymore)

Support for Exynos4415 is going away because there are no internal nor external users. Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), the platform cannot be instantiated so remove also the drivers. Signed-off-by: Krzysztof Kozlowski Acked-by: Kukjin Kim Acked-by: Rob

Re: [PATCH] morse code panics for 2.5.65

Andrew, Tomas, can you please give GPL permission for this code. https://old.lwn.net/Articles/25868/ -- Regards, Oleksij signature.asc Description: OpenPGP digital signature

Re: [PATCH] morse code panics for 2.5.65

Andrew, Tomas, can you please give GPL permission for this code. https://old.lwn.net/Articles/25868/ -- Regards, Oleksij signature.asc Description: OpenPGP digital signature

Re: [PATCH v2 RFC] mm/vmscan: more restrictive condition for retry in do_try_to_free_pages

On Sat, Mar 11, 2017 at 5:51 AM, Yisheng Xie wrote: > From: Yisheng Xie > > When we enter do_try_to_free_pages, the may_thrash is always clear, and > it will retry shrink zones to tap cgroup's reserves memory by setting > may_thrash when the former

Re: [PATCH v2 RFC] mm/vmscan: more restrictive condition for retry in do_try_to_free_pages

On Sat, Mar 11, 2017 at 5:51 AM, Yisheng Xie wrote: > From: Yisheng Xie > > When we enter do_try_to_free_pages, the may_thrash is always clear, and > it will retry shrink zones to tap cgroup's reserves memory by setting > may_thrash when the former shrink_zones reclaim nothing. > > However, when

[PATCH v2 2/3] watchdog: s3c2410: Simplify getting driver data

Simplify the flow in helper function for getting the driver data by using of_device_get_match_data() and only one if() branch. The code should be equivalent. Signed-off-by: Krzysztof Kozlowski --- drivers/watchdog/s3c2410_wdt.c | 17 ++--- 1 file changed, 10

[PATCH v2 2/3] watchdog: s3c2410: Simplify getting driver data

Simplify the flow in helper function for getting the driver data by using of_device_get_match_data() and only one if() branch. The code should be equivalent. Signed-off-by: Krzysztof Kozlowski --- drivers/watchdog/s3c2410_wdt.c | 17 ++--- 1 file changed, 10 insertions(+), 7

[PATCH v2 3/3] watchdog: s3c2410: Minor code cleanup

Cleanup the code from minor readability issues (no functional changes): 1. Fix checkpatch: ERROR: Do not include the paragraph about writing to the Free Software Foundation's mailing address. 2. Fix checkpatch: WARNING: quoted string split across lines 3. Fix chechpatch: WARNING: Prefer

[PATCH v2 3/3] watchdog: s3c2410: Minor code cleanup

Cleanup the code from minor readability issues (no functional changes): 1. Fix checkpatch: ERROR: Do not include the paragraph about writing to the Free Software Foundation's mailing address. 2. Fix checkpatch: WARNING: quoted string split across lines 3. Fix chechpatch: WARNING: Prefer

[PATCH v2 1/3] watchdog: s3c2410: Constify local structures

Structures watchdog_device, watchdog_ops and s3c2410_wdt_variant are not modified so they can be made const to increase code safeness. Signed-off-by: Krzysztof Kozlowski --- drivers/watchdog/s3c2410_wdt.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff

[PATCH v2 1/3] watchdog: s3c2410: Constify local structures

Structures watchdog_device, watchdog_ops and s3c2410_wdt_variant are not modified so they can be made const to increase code safeness. Signed-off-by: Krzysztof Kozlowski --- drivers/watchdog/s3c2410_wdt.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git

[PATCH v2 0/3] watchdog: s3c2410: Minor cleanups

Hi, Continuation of previous [1] with patches just rebased on current linux-next. [1] http://lkml.iu.edu/hypermail/linux/kernel/1702.3/00673.html Best regards, Krzysztof Krzysztof Kozlowski (3): watchdog: s3c2410: Constify local structures watchdog: s3c2410: Simplify getting driver data

[PATCH v2 0/3] watchdog: s3c2410: Minor cleanups

Hi, Continuation of previous [1] with patches just rebased on current linux-next. [1] http://lkml.iu.edu/hypermail/linux/kernel/1702.3/00673.html Best regards, Krzysztof Krzysztof Kozlowski (3): watchdog: s3c2410: Constify local structures watchdog: s3c2410: Simplify getting driver data

Re: [PATCH v2 2/8] watchdog: s3c2410: Fix infinite interrupt in soft mode

On Sat, Mar 11, 2017 at 07:25:21PM +0200, Krzysztof Kozlowski wrote: > In soft (no-reboot) mode, the driver self-pings watchdog upon expiration > of an interrupt. However the interrupt itself was not cleared thus on > first hit, the system enters infinite interrupt handling loop. > > On Odroid

Re: [PATCH v2 2/8] watchdog: s3c2410: Fix infinite interrupt in soft mode

On Sat, Mar 11, 2017 at 07:25:21PM +0200, Krzysztof Kozlowski wrote: > In soft (no-reboot) mode, the driver self-pings watchdog upon expiration > of an interrupt. However the interrupt itself was not cleared thus on > first hit, the system enters infinite interrupt handling loop. > > On Odroid

Re: [PATCH v4 14/36] [media] v4l2-mc: add a function to inherit controls from a pipeline

On Sat, Mar 11, 2017 at 05:32:29PM +0200, Sakari Ailus wrote: > My understanding of the i.MX6 case is the hardware is configurable enough > to warrant the use of the Media controller API. Some patches indicate > there are choices to be made in data routing. The iMX6 does have configurable data

Re: [PATCH v4 14/36] [media] v4l2-mc: add a function to inherit controls from a pipeline

On Sat, Mar 11, 2017 at 05:32:29PM +0200, Sakari Ailus wrote: > My understanding of the i.MX6 case is the hardware is configurable enough > to warrant the use of the Media controller API. Some patches indicate > there are choices to be made in data routing. The iMX6 does have configurable data

Re: [Outreachy kernel] [PATCH v2] staging: rtl8192u: Remove typedef phy_ofdm_rx_status_rxsc_sgien_exintfflag

On Sat, 11 Mar 2017, simran singhal wrote: > Remove typdef phy_ofdm_rx_status_rxsc_sgien_exintfflag and replace its uses > in the code. > > Signed-off-by: simran singhal Acked-by: Julia Lawall > --- > > v2: >-Drop the "_" at the beginning

Re: [Outreachy kernel] [PATCH v2] staging: rtl8192u: Remove typedef phy_ofdm_rx_status_rxsc_sgien_exintfflag

On Sat, 11 Mar 2017, simran singhal wrote: > Remove typdef phy_ofdm_rx_status_rxsc_sgien_exintfflag and replace its uses > in the code. > > Signed-off-by: simran singhal Acked-by: Julia Lawall > --- > > v2: >-Drop the "_" at the beginning of the name of the structure > >

[PATCH 2/2] x86/fpu: Support disabling AVX and AVX512

From: Andi Kleen For performance testing it is useful to be able to disable AVX and AVX512. User programs check in XGETBV if AVX is supported by the OS. If we don't initialize the XSAVE state for AVX it will appear as if the OS is not supporting AVX. Implement disable

[PATCH 2/2] x86/fpu: Support disabling AVX and AVX512

From: Andi Kleen For performance testing it is useful to be able to disable AVX and AVX512. User programs check in XGETBV if AVX is supported by the OS. If we don't initialize the XSAVE state for AVX it will appear as if the OS is not supporting AVX. Implement disable options for AVX and AVX512

[PATCH 1/2] x86/xsave: Move xsave initialization to after parsing early parameters

From: Andi Kleen Move the XSAVE initialization code to be after parsing early parameters. I don't see any reason why the FPU code needs to be initialized that early, nothing else in the initialization phase uses XSAVE. This is useful to be able to handle command line

[PATCH 1/2] x86/xsave: Move xsave initialization to after parsing early parameters

From: Andi Kleen Move the XSAVE initialization code to be after parsing early parameters. I don't see any reason why the FPU code needs to be initialized that early, nothing else in the initialization phase uses XSAVE. This is useful to be able to handle command line parameters in the XSAVE

Re: [PATCH v2 1/8] watchdog: s3c2410: Remove confusing CONFIG prefix from local defines

On Sat, Mar 11, 2017 at 07:25:20PM +0200, Krzysztof Kozlowski wrote: > The CONFIG prefix from defines in the s3c2410_wdt.c might suggest that > these constants come from Kconfig. > > Signed-off-by: Krzysztof Kozlowski > Reviewed-by: Guenter Roeck > --- >

Re: [PATCH v2 1/8] watchdog: s3c2410: Remove confusing CONFIG prefix from local defines

On Sat, Mar 11, 2017 at 07:25:20PM +0200, Krzysztof Kozlowski wrote: > The CONFIG prefix from defines in the s3c2410_wdt.c might suggest that > these constants come from Kconfig. > > Signed-off-by: Krzysztof Kozlowski > Reviewed-by: Guenter Roeck > --- > drivers/watchdog/s3c2410_wdt.c | 16

[PATCH v2 6/8] ARM: dts: exynos: Fix infinite interrupt in soft mode on Exynos4210 and Exynos5440

In soft (no-reboot) mode, the driver self-pings watchdog upon expiration of an interrupt. The interrupt has to be cleared, because otherwise system enters infinite interrupt handling loop. Use a samsung,s3c6410-wdt compatible to select appropriate quirk for clearing the watchdog interrupt.

[PATCH v2 6/8] ARM: dts: exynos: Fix infinite interrupt in soft mode on Exynos4210 and Exynos5440

In soft (no-reboot) mode, the driver self-pings watchdog upon expiration of an interrupt. The interrupt has to be cleared, because otherwise system enters infinite interrupt handling loop. Use a samsung,s3c6410-wdt compatible to select appropriate quirk for clearing the watchdog interrupt.

[PATCH v2 8/8] ARM: dts: s5pv210: Fix infinite interrupt in soft mode

In soft (no-reboot) mode, the driver self-pings watchdog upon expiration of an interrupt. The interrupt has to be cleared, because otherwise system enters infinite interrupt handling loop. Use a samsung,s3c6410-wdt compatible to select appropriate quirk for clearing the watchdog interrupt.

[PATCH v2 8/8] ARM: dts: s5pv210: Fix infinite interrupt in soft mode

In soft (no-reboot) mode, the driver self-pings watchdog upon expiration of an interrupt. The interrupt has to be cleared, because otherwise system enters infinite interrupt handling loop. Use a samsung,s3c6410-wdt compatible to select appropriate quirk for clearing the watchdog interrupt.

[PATCH v2 7/8] ARM: dts: s3c64xx: Fix infinite interrupt in soft mode

In soft (no-reboot) mode, the driver self-pings watchdog upon expiration of an interrupt. The interrupt has to be cleared, because otherwise system enters infinite interrupt handling loop. Use a samsung,s3c6410-wdt compatible to select appropriate quirk for clearing the watchdog interrupt.

[PATCH v2 7/8] ARM: dts: s3c64xx: Fix infinite interrupt in soft mode

In soft (no-reboot) mode, the driver self-pings watchdog upon expiration of an interrupt. The interrupt has to be cleared, because otherwise system enters infinite interrupt handling loop. Use a samsung,s3c6410-wdt compatible to select appropriate quirk for clearing the watchdog interrupt.

[PATCH v2 4/8] ARM: dts: s3c64xx: Enable watchdog on all S3C64xx boards

Watchdog module does not have external dependencies so it can be safely enabled in s3c64xx.dtsi thus making it available for all S3C64xx-based boards. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/s3c64xx.dtsi | 1 - 1 file changed, 1 deletion(-) diff --git

[PATCH v2 3/8] ARM: dts: exynos: Fix watchdog reset on Exynos4412

The Exynos4412 has the same watchdog as newer SoCs (e.g. Exynos5250). Just like the others, for working it requires additional steps in Power Management Unit: unmasking the reset request and enabling the system reset. Without these additional steps in PMU, the watchdog will not be able to reset

[PATCH v2 5/8] ARM: dts: exynos: Enable watchdog on all Exynos4 boards

Watchdog module does not have external dependencies so it can be safely enabled in exynos4.dtsi thus making it available for all Exynos4-based boards. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/exynos4210-origen.dts | 4

[PATCH v2 1/8] watchdog: s3c2410: Remove confusing CONFIG prefix from local defines

The CONFIG prefix from defines in the s3c2410_wdt.c might suggest that these constants come from Kconfig. Signed-off-by: Krzysztof Kozlowski Reviewed-by: Guenter Roeck --- drivers/watchdog/s3c2410_wdt.c | 16 1 file changed, 8

[PATCH v2 2/8] watchdog: s3c2410: Fix infinite interrupt in soft mode

In soft (no-reboot) mode, the driver self-pings watchdog upon expiration of an interrupt. However the interrupt itself was not cleared thus on first hit, the system enters infinite interrupt handling loop. On Odroid U3 (Exynos4412), when booted with s3c2410_wdt.soft_noboot=1 argument the console

[PATCH v2 4/8] ARM: dts: s3c64xx: Enable watchdog on all S3C64xx boards

Watchdog module does not have external dependencies so it can be safely enabled in s3c64xx.dtsi thus making it available for all S3C64xx-based boards. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/s3c64xx.dtsi | 1 - 1 file changed, 1 deletion(-) diff --git

[PATCH v2 3/8] ARM: dts: exynos: Fix watchdog reset on Exynos4412

The Exynos4412 has the same watchdog as newer SoCs (e.g. Exynos5250). Just like the others, for working it requires additional steps in Power Management Unit: unmasking the reset request and enabling the system reset. Without these additional steps in PMU, the watchdog will not be able to reset

[PATCH v2 5/8] ARM: dts: exynos: Enable watchdog on all Exynos4 boards

Watchdog module does not have external dependencies so it can be safely enabled in exynos4.dtsi thus making it available for all Exynos4-based boards. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/exynos4210-origen.dts | 4 arch/arm/boot/dts/exynos4210.dtsi

[PATCH v2 1/8] watchdog: s3c2410: Remove confusing CONFIG prefix from local defines

The CONFIG prefix from defines in the s3c2410_wdt.c might suggest that these constants come from Kconfig. Signed-off-by: Krzysztof Kozlowski Reviewed-by: Guenter Roeck --- drivers/watchdog/s3c2410_wdt.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git

[PATCH v2 2/8] watchdog: s3c2410: Fix infinite interrupt in soft mode

In soft (no-reboot) mode, the driver self-pings watchdog upon expiration of an interrupt. However the interrupt itself was not cleared thus on first hit, the system enters infinite interrupt handling loop. On Odroid U3 (Exynos4412), when booted with s3c2410_wdt.soft_noboot=1 argument the console

[PATCH v2 0/8] watchdog: s3c2410: Fixes and improvements

Hi, Minor cleanup and some fixes for the watchdog used on all Samsung SoCs. The DTS patches should through samsung-soc tree but they depend on introducing new compatible. The patches waiting for new compatible will be deferred to next release. Changes since v1: = 1. Add

[PATCH v2 0/8] watchdog: s3c2410: Fixes and improvements

Hi, Minor cleanup and some fixes for the watchdog used on all Samsung SoCs. The DTS patches should through samsung-soc tree but they depend on introducing new compatible. The patches waiting for new compatible will be deferred to next release. Changes since v1: = 1. Add

[PATCH v2] staging: rtl8192u: Remove typedef phy_ofdm_rx_status_rxsc_sgien_exintfflag

Remove typdef phy_ofdm_rx_status_rxsc_sgien_exintfflag and replace its uses in the code. Signed-off-by: simran singhal --- v2: -Drop the "_" at the beginning of the name of the structure drivers/staging/rtl8192u/r8192U.h | 4 ++--

[PATCH v2] staging: rtl8192u: Remove typedef phy_ofdm_rx_status_rxsc_sgien_exintfflag

Remove typdef phy_ofdm_rx_status_rxsc_sgien_exintfflag and replace its uses in the code. Signed-off-by: simran singhal --- v2: -Drop the "_" at the beginning of the name of the structure drivers/staging/rtl8192u/r8192U.h | 4 ++-- drivers/staging/rtl8192u/r8192U_core.c | 4 ++-- 2

Re: [PATCH 2/2] x86/fpu: Support disabling AVX and AVX512

On Sat, Mar 11, 2017 at 11:46:37AM +0100, Thomas Gleixner wrote: > > +enum xsave_features { > > + XSAVE_X87, > > + XSAVE_SSE, > > + XSAVE_AVX, > > + XSAVE_MPX_BOUNDS, > > + XSAVE_MPX_CSR, > > + XSAVE_AVX512_OPMASK, > > + XSAVE_AVX512_HI256, > > + XSAVE_AVX512_ZMM_HI256, > > +

Re: [PATCH 2/2] x86/fpu: Support disabling AVX and AVX512

On Sat, Mar 11, 2017 at 11:46:37AM +0100, Thomas Gleixner wrote: > > +enum xsave_features { > > + XSAVE_X87, > > + XSAVE_SSE, > > + XSAVE_AVX, > > + XSAVE_MPX_BOUNDS, > > + XSAVE_MPX_CSR, > > + XSAVE_AVX512_OPMASK, > > + XSAVE_AVX512_HI256, > > + XSAVE_AVX512_ZMM_HI256, > > +

[PATCH] staging: rtl8188eu: Fix redundant space coding style issue

Signed-off-by: Alex Yashchenko --- drivers/staging/rtl8188eu/hal/Hal8188ERateAdaptive.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/rtl8188eu/hal/Hal8188ERateAdaptive.c b/drivers/staging/rtl8188eu/hal/Hal8188ERateAdaptive.c index

[PATCH] staging: rtl8188eu: Fix redundant space coding style issue

Signed-off-by: Alex Yashchenko --- drivers/staging/rtl8188eu/hal/Hal8188ERateAdaptive.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/rtl8188eu/hal/Hal8188ERateAdaptive.c b/drivers/staging/rtl8188eu/hal/Hal8188ERateAdaptive.c index 201c15b..81bf494 100644

Re: [PATCH] powerpc: Fix crash introduced with commit 5657933dbb6e

On Thu, Mar 9, 2017 at 6:33 PM, Larry Finger wrote: > > The problem was bisected to commit 5657933dbb6e ("treewide: Move dma_ops > from struct dev_archdata into struct device"). The problem was a missing > copy of critical information from struct dev_archdata into

Re: [PATCH] powerpc: Fix crash introduced with commit 5657933dbb6e

On Thu, Mar 9, 2017 at 6:33 PM, Larry Finger wrote: > > The problem was bisected to commit 5657933dbb6e ("treewide: Move dma_ops > from struct dev_archdata into struct device"). The problem was a missing > copy of critical information from struct dev_archdata into struct device, > leading to the

Re: [Outreachy kernel] [PATCH] staging: rtl8192u: Remove typedef phy_ofdm_rx_status_rxsc_sgien_exintfflag

On Sat, 11 Mar 2017, SIMRAN SINGHAL wrote: > On Sat, Mar 11, 2017 at 9:56 PM, Julia Lawall wrote: > > > > > > On Sat, 11 Mar 2017, simran singhal wrote: > > > >> Remove typdef phy_ofdm_rx_status_rxsc_sgien_exintfflag and replace its uses > >> in the code. > >> > >>

Re: [Outreachy kernel] [PATCH] staging: rtl8192u: Remove typedef phy_ofdm_rx_status_rxsc_sgien_exintfflag

On Sat, 11 Mar 2017, SIMRAN SINGHAL wrote: > On Sat, Mar 11, 2017 at 9:56 PM, Julia Lawall wrote: > > > > > > On Sat, 11 Mar 2017, simran singhal wrote: > > > >> Remove typdef phy_ofdm_rx_status_rxsc_sgien_exintfflag and replace its uses > >> in the code. > >> > >> Signed-off-by: simran

Re: [Outreachy kernel] [PATCH] staging: rtl8192u: Remove typedef phy_ofdm_rx_status_rxsc_sgien_exintfflag

On Sat, Mar 11, 2017 at 9:56 PM, Julia Lawall wrote: > > > On Sat, 11 Mar 2017, simran singhal wrote: > >> Remove typdef phy_ofdm_rx_status_rxsc_sgien_exintfflag and replace its uses >> in the code. >> >> Signed-off-by: simran singhal >> --- >>

Re: [Outreachy kernel] [PATCH] staging: rtl8192u: Remove typedef phy_ofdm_rx_status_rxsc_sgien_exintfflag

On Sat, Mar 11, 2017 at 9:56 PM, Julia Lawall wrote: > > > On Sat, 11 Mar 2017, simran singhal wrote: > >> Remove typdef phy_ofdm_rx_status_rxsc_sgien_exintfflag and replace its uses >> in the code. >> >> Signed-off-by: simran singhal >> --- >> drivers/staging/rtl8192u/r8192U.h | 4 ++-- >>

Re: nvme, allocation failures, and aborted commands

On Thursday, March 9, 2017 6:03:34 PM MST Keith Busch wrote: > On Thu, Mar 09, 2017 at 03:01:27PM -0700, Thomas Fjellstrom wrote: > > On Monday, March 6, 2017 5:46:33 PM MST Keith Busch wrote: > > > > > > echo 128 > /sys/block/nvme0n1/queue/max_hw_sectors_kb > > > echo 128 >

Re: nvme, allocation failures, and aborted commands

On Thursday, March 9, 2017 6:03:34 PM MST Keith Busch wrote: > On Thu, Mar 09, 2017 at 03:01:27PM -0700, Thomas Fjellstrom wrote: > > On Monday, March 6, 2017 5:46:33 PM MST Keith Busch wrote: > > > > > > echo 128 > /sys/block/nvme0n1/queue/max_hw_sectors_kb > > > echo 128 >

Re: [Outreachy kernel] [PATCH] staging: rtl8192u: Remove typedef phy_ofdm_rx_status_rxsc_sgien_exintfflag

On Sat, 11 Mar 2017, simran singhal wrote: > Remove typdef phy_ofdm_rx_status_rxsc_sgien_exintfflag and replace its uses > in the code. > > Signed-off-by: simran singhal > --- > drivers/staging/rtl8192u/r8192U.h | 4 ++-- > drivers/staging/rtl8192u/r8192U_core.c

Re: [Outreachy kernel] [PATCH] staging: rtl8192u: Remove typedef phy_ofdm_rx_status_rxsc_sgien_exintfflag

On Sat, 11 Mar 2017, simran singhal wrote: > Remove typdef phy_ofdm_rx_status_rxsc_sgien_exintfflag and replace its uses > in the code. > > Signed-off-by: simran singhal > --- > drivers/staging/rtl8192u/r8192U.h | 4 ++-- > drivers/staging/rtl8192u/r8192U_core.c | 4 ++-- > 2 files

[PATCH] drm/radeon: Fix GPU lockups for the R7 M270

Commit 3a69adfe5617 ("drm/radeon: drop oland quirks") removed quirks for Oland but also caused a regression where M270 GPUs would go into a lock-up when OpenGL intensive applications were used. This reverts the change only for the M270 and fixes the lock-ups. Signed-off-by: Umang Raghuvanshi

[PATCH] drm/radeon: Fix GPU lockups for the R7 M270

Commit 3a69adfe5617 ("drm/radeon: drop oland quirks") removed quirks for Oland but also caused a regression where M270 GPUs would go into a lock-up when OpenGL intensive applications were used. This reverts the change only for the M270 and fixes the lock-ups. Signed-off-by: Umang Raghuvanshi ---

[PATCH] staging: rtl8192u: Remove typedef phy_ofdm_rx_status_rxsc_sgien_exintfflag

Remove typdef phy_ofdm_rx_status_rxsc_sgien_exintfflag and replace its uses in the code. Signed-off-by: simran singhal --- drivers/staging/rtl8192u/r8192U.h | 4 ++-- drivers/staging/rtl8192u/r8192U_core.c | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-)

[PATCH] staging: rtl8192u: Remove typedef phy_ofdm_rx_status_rxsc_sgien_exintfflag

Remove typdef phy_ofdm_rx_status_rxsc_sgien_exintfflag and replace its uses in the code. Signed-off-by: simran singhal --- drivers/staging/rtl8192u/r8192U.h | 4 ++-- drivers/staging/rtl8192u/r8192U_core.c | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git

Re: UBSAN: Undefined behaviour in kernel/time/tick-sched.c:600:9

> > Cc'ing KASAN folks > > > >> (Retry with fixed address ox 86 list) > >> > >> This HP Netserver LT6000R, quad P3 Xeon. Trying > >> 4.11.0-rc1-00088-gec3b93a, I got the following UBSAN warning that was > >> not there in 4.10: > >> > >> [ 14.820437] > >>

Re: UBSAN: Undefined behaviour in kernel/time/tick-sched.c:600:9

> > Cc'ing KASAN folks > > > >> (Retry with fixed address ox 86 list) > >> > >> This HP Netserver LT6000R, quad P3 Xeon. Trying > >> 4.11.0-rc1-00088-gec3b93a, I got the following UBSAN warning that was > >> not there in 4.10: > >> > >> [ 14.820437] > >>

Re: [PULL REQUEST] i2c for 4.11

Linus, > You added an extra revert, only to pull in the *exact* same patch. WTF? The patch I reverted had a broken, typoed Signed-off. My rationale was to have only a proper one, and not two different ones coming from different trees. Looks like I misjudged, sorry. > Please stop this kind of

Re: [PULL REQUEST] i2c for 4.11

Linus, > You added an extra revert, only to pull in the *exact* same patch. WTF? The patch I reverted had a broken, typoed Signed-off. My rationale was to have only a proper one, and not two different ones coming from different trees. Looks like I misjudged, sorry. > Please stop this kind of

[PATCH] arm64: dts: uniphier: add pinctrl property to eMMC node for LD11/LD20

Now everything is ready to enable this pinctrl. Signed-off-by: Masahiro Yamada --- arch/arm64/boot/dts/socionext/uniphier-ld11.dtsi | 2 ++ arch/arm64/boot/dts/socionext/uniphier-ld20.dtsi | 2 ++ 2 files changed, 4 insertions(+) diff --git

[PATCH] arm64: dts: uniphier: add pinctrl property to eMMC node for LD11/LD20

Now everything is ready to enable this pinctrl. Signed-off-by: Masahiro Yamada --- arch/arm64/boot/dts/socionext/uniphier-ld11.dtsi | 2 ++ arch/arm64/boot/dts/socionext/uniphier-ld20.dtsi | 2 ++ 2 files changed, 4 insertions(+) diff --git a/arch/arm64/boot/dts/socionext/uniphier-ld11.dtsi

<    1   2   3   4   5   6   >