Re: [PATCH] mm: Add additional consistency check

On Mon, 3 Apr 2017, Michael Ellerman wrote: > At least in slab.c it seems that would allow you to "free" an object > from one kmem_cache onto the array_cache of another kmem_cache, which > seems fishy. But maybe there's a check somewhere I'm missing? kfree can be used to free any object from any

[PATCH v8 0/2] OV5645 camera sensor driver

Resending the OV5645 camera sensor driver patchset to include devicet...@vger.kernel.org too. As there are two one-line changes (agreed on linux-media) I've also increased the patchset version to 8th. Changes since verion 7: - "unsigned int i" changed to "int i" in ov5645_find_nearest_mode(); -

[PATCH v8 1/2] media: i2c/ov5645: add the device tree binding document

Add the document for ov5645 device tree binding. Signed-off-by: Todor Tomov Reviewed-by: Laurent Pinchart --- .../devicetree/bindings/media/i2c/ov5645.txt | 54 ++ 1 file changed, 54 insertions(+) create mode

[PATCH v8 2/2] media: Add a driver for the ov5645 camera sensor.

The ov5645 sensor from Omnivision supports up to 2592x1944 and CSI2 interface. The driver adds support for the following modes: - 1280x960 - 1920x1080 - 2592x1944 Output format is packed 8bit UYVY. Signed-off-by: Todor Tomov Reviewed-by: Laurent Pinchart

[PATCH v8 1/2] media: i2c/ov5645: add the device tree binding document

Add the document for ov5645 device tree binding. Signed-off-by: Todor Tomov Reviewed-by: Laurent Pinchart --- .../devicetree/bindings/media/i2c/ov5645.txt | 54 ++ 1 file changed, 54 insertions(+) create mode 100644

[PATCH v8 2/2] media: Add a driver for the ov5645 camera sensor.

The ov5645 sensor from Omnivision supports up to 2592x1944 and CSI2 interface. The driver adds support for the following modes: - 1280x960 - 1920x1080 - 2592x1944 Output format is packed 8bit UYVY. Signed-off-by: Todor Tomov Reviewed-by: Laurent Pinchart --- drivers/media/i2c/Kconfig | 12

Re: [PATCH v6 02/39] [media] dt-bindings: Add bindings for i.MX media driver

On Tue, Mar 28, 2017 at 05:35:52PM -0700, Steve Longerbeam wrote: > > > On 03/28/2017 05:21 PM, Rob Herring wrote: > > On Mon, Mar 27, 2017 at 7:40 PM, Steve Longerbeam > > wrote: > > > Add bindings documentation for the i.MX media driver. > > > > > > > > > + > > >

Re: [PATCH v6 02/39] [media] dt-bindings: Add bindings for i.MX media driver

On Tue, Mar 28, 2017 at 05:35:52PM -0700, Steve Longerbeam wrote: > > > On 03/28/2017 05:21 PM, Rob Herring wrote: > > On Mon, Mar 27, 2017 at 7:40 PM, Steve Longerbeam > > wrote: > > > Add bindings documentation for the i.MX media driver. > > > > > > > > > + > > > +mipi_csi2 node > > >

Re: [PATCH 2/3] dt-bindings: Add bindings for nvidia,tegra186-ccplex-cluster

On Mon, Apr 03, 2017 at 03:42:24PM +0300, Mikko Perttunen wrote: > The Tegra186 CCPLEX_CLUSTER area contains memory-mapped > registers that initiate CPU frequency/voltage transitions. > > Signed-off-by: Mikko Perttunen > --- >

Re: [PATCH 2/3] dt-bindings: Add bindings for nvidia,tegra186-ccplex-cluster

On Mon, Apr 03, 2017 at 03:42:24PM +0300, Mikko Perttunen wrote: > The Tegra186 CCPLEX_CLUSTER area contains memory-mapped > registers that initiate CPU frequency/voltage transitions. > > Signed-off-by: Mikko Perttunen > --- > .../arm/tegra/nvidia,tegra186-ccplex-cluster.txt | 22 >

Re: [PATCH] watchdog: pcwd_usb: fix NULL-deref at probe

On 04/03/2017 01:36 AM, Johan Hovold wrote: On Mon, Mar 13, 2017 at 10:16:33AM -0700, Guenter Roeck wrote: On Mon, Mar 13, 2017 at 01:49:45PM +0100, Johan Hovold wrote: Make sure to check the number of endpoints to avoid dereferencing a NULL-pointer should a malicious device lack endpoints.

Re: [PATCH] watchdog: pcwd_usb: fix NULL-deref at probe

On 04/03/2017 01:36 AM, Johan Hovold wrote: On Mon, Mar 13, 2017 at 10:16:33AM -0700, Guenter Roeck wrote: On Mon, Mar 13, 2017 at 01:49:45PM +0100, Johan Hovold wrote: Make sure to check the number of endpoints to avoid dereferencing a NULL-pointer should a malicious device lack endpoints.

Re: [RFC PATCH v1 00/30] fs: inode->i_version rework and optimization

On Sun 02-04-17 09:05:26, Dave Chinner wrote: > On Thu, Mar 30, 2017 at 12:12:31PM -0400, J. Bruce Fields wrote: > > On Thu, Mar 30, 2017 at 07:11:48AM -0400, Jeff Layton wrote: > > > On Thu, 2017-03-30 at 08:47 +0200, Jan Kara wrote: > > > > Because if above is acceptable we could make reported

Re: [RFC PATCH v1 00/30] fs: inode->i_version rework and optimization

On Sun 02-04-17 09:05:26, Dave Chinner wrote: > On Thu, Mar 30, 2017 at 12:12:31PM -0400, J. Bruce Fields wrote: > > On Thu, Mar 30, 2017 at 07:11:48AM -0400, Jeff Layton wrote: > > > On Thu, 2017-03-30 at 08:47 +0200, Jan Kara wrote: > > > > Because if above is acceptable we could make reported

Re: [alsa-devel][PATCH v2 2/2] ASoC: wm8960: Let wm8960 driver configure its bit clock and frame clock

On Mon, Apr 03, 2017 at 04:39:40PM +0300, Daniel Baluta wrote: > On Mon, Apr 3, 2017 at 4:34 PM, Charles Keepax > wrote: > > On Mon, Apr 03, 2017 at 04:16:23PM +0300, Daniel Baluta wrote: > > Does this problem still remain after the relaxed clock > >

Re: [alsa-devel][PATCH v2 2/2] ASoC: wm8960: Let wm8960 driver configure its bit clock and frame clock

On Mon, Apr 03, 2017 at 04:39:40PM +0300, Daniel Baluta wrote: > On Mon, Apr 3, 2017 at 4:34 PM, Charles Keepax > wrote: > > On Mon, Apr 03, 2017 at 04:16:23PM +0300, Daniel Baluta wrote: > > Does this problem still remain after the relaxed clock > > computation? The maths you quote depends on

[PATCH] Documentation: stable-kernel-rules: fix stable-tag format

A patch documenting how to specify which kernels a particular fix should be backported to (seemingly) inadvertently added a minus sign after the kernel version. This particular stable-tag format had never been used prior to this patch, and was neither present when the patch in question was first

[PATCH] Documentation: stable-kernel-rules: fix stable-tag format

A patch documenting how to specify which kernels a particular fix should be backported to (seemingly) inadvertently added a minus sign after the kernel version. This particular stable-tag format had never been used prior to this patch, and was neither present when the patch in question was first

Re: [RFC PATCH] binder: Don't require the binder lock when killed in binder_thread_read()

On 03/31/2017 07:53 PM, Douglas Anderson wrote: > Sometimes when we're out of memory the OOM killer decides to kill a > process that's in binder_thread_read(). If we happen to be waiting > for work we'll get the kill signal and wake up. That's good. ...but > then we try to grab the binder lock

Re: [RFC PATCH] binder: Don't require the binder lock when killed in binder_thread_read()

On 03/31/2017 07:53 PM, Douglas Anderson wrote: > Sometimes when we're out of memory the OOM killer decides to kill a > process that's in binder_thread_read(). If we happen to be waiting > for work we'll get the kill signal and wake up. That's good. ...but > then we try to grab the binder lock

[PATCH 3/3] hwmon: pwm-fan: remove no longer needed suspend/resume code

The suspend/resume is now properly handled by pwm-samsung driver (pwm-fan is currently only used by ARM Exynos boards) and the old code only handles ctx->pwm_value != 0 case. Just remove it. Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/hwmon/pwm-fan.c | 32

[PATCH 3/3] hwmon: pwm-fan: remove no longer needed suspend/resume code

The suspend/resume is now properly handled by pwm-samsung driver (pwm-fan is currently only used by ARM Exynos boards) and the old code only handles ctx->pwm_value != 0 case. Just remove it. Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/hwmon/pwm-fan.c | 32

[PATCH 0/3] pwm: pwm-samsung: fix suspend/resume support

Hi, This patchset fixes suspend/resume support in pwm-samsung driver (which has an effect of fixing suspend/resume support for PWM client drivers such as pwm-fan one). Then it removes no longer needed suspend/resume code from pwm-fan driver. It was tested on Odroid-XU3 board (with few extra

[PATCH 0/3] pwm: pwm-samsung: fix suspend/resume support

Hi, This patchset fixes suspend/resume support in pwm-samsung driver (which has an effect of fixing suspend/resume support for PWM client drivers such as pwm-fan one). Then it removes no longer needed suspend/resume code from pwm-fan driver. It was tested on Odroid-XU3 board (with few extra

[PATCH 2/3] pwm: pwm-samsung: fix suspend/resume support

Fix suspend/resume support: - add disabled_mask to struct samsung_pwm_chip to track PWM disabled state information in pwm_samsung_{disable,enable}() - rename pwm_samsung_config() to __pwm_samsung_config() and add extra force_period parameter to be used during resume (to force tin_ns and

[PATCH 1/3] pwm: pwm-samsung: remove redundant checks from pwm_samsung_config()

If the requested period_ns and duty_ns values are identical to the last programmed ones pwm_samsung_config() returns early and skips the hardware configuration. The same checks are now done by the PWM core so the driver specific ones can be removed. Signed-off-by: Bartlomiej Zolnierkiewicz

[PATCH 1/3] pwm: pwm-samsung: remove redundant checks from pwm_samsung_config()

If the requested period_ns and duty_ns values are identical to the last programmed ones pwm_samsung_config() returns early and skips the hardware configuration. The same checks are now done by the PWM core so the driver specific ones can be removed. Signed-off-by: Bartlomiej Zolnierkiewicz ---

[PATCH 2/3] pwm: pwm-samsung: fix suspend/resume support

Fix suspend/resume support: - add disabled_mask to struct samsung_pwm_chip to track PWM disabled state information in pwm_samsung_{disable,enable}() - rename pwm_samsung_config() to __pwm_samsung_config() and add extra force_period parameter to be used during resume (to force tin_ns and

Re: [PATCH] mm/zswap: fix potential deadlock in zswap_frontswap_store()

On 04/03/2017 04:28 PM, Vlastimil Babka wrote: >> >> >> Seems it was broken by >> >> a8161d1ed6098506303c65b3701dedba876df42a >> Author: Vlastimil Babka >> Date: Thu Jul 28 15:49:19 2016 -0700 >> >> mm, page_alloc: restructure direct compaction handling in slowpath > >

Re: [PATCH] mm/zswap: fix potential deadlock in zswap_frontswap_store()

On 04/03/2017 04:28 PM, Vlastimil Babka wrote: >> >> >> Seems it was broken by >> >> a8161d1ed6098506303c65b3701dedba876df42a >> Author: Vlastimil Babka >> Date: Thu Jul 28 15:49:19 2016 -0700 >> >> mm, page_alloc: restructure direct compaction handling in slowpath > > Yeah, looks like

[PATCH v2 3/4] usb: dwc3: of-simple: Add support to get resets for the device

Add support to get a list of resets available for the device. These resets must be kept de-asserted until the device is in use. Cc: Felipe Balbi Cc: Philipp Zabel Signed-off-by: Vivek Gautam --- Changes since v1: - Using

[PATCH v2 1/4] reset: Add API to count number of reset available with device

Count number of reset phandles available with the device node to know the resets a given device has. Cc: Philipp Zabel Signed-off-by: Vivek Gautam --- Changes since v1: - Handling the error path by returning error code for failures and

[PATCH v2 3/4] usb: dwc3: of-simple: Add support to get resets for the device

Add support to get a list of resets available for the device. These resets must be kept de-asserted until the device is in use. Cc: Felipe Balbi Cc: Philipp Zabel Signed-off-by: Vivek Gautam --- Changes since v1: - Using new APIs for reset control array. - Using the *_get_exclusive() API.

[PATCH v2 1/4] reset: Add API to count number of reset available with device

Count number of reset phandles available with the device node to know the resets a given device has. Cc: Philipp Zabel Signed-off-by: Vivek Gautam --- Changes since v1: - Handling the error path by returning error code for failures and ENODEV for count equal to 0. - Moved the function to

[PATCH v2 4/4] soc/tegra: pmc: Use the new reset APIs to manage reset controllers

Make use of reset_control_array_*() set of APIs to manage an array of reset controllers available with the device. Cc: Thierry Reding Cc: Philipp Zabel Signed-off-by: Vivek Gautam --- Changes since v1: - New patch added

[PATCH v2 0/4] reset: APIs to manage a list of resets

Set of patches to support getting and de/asserting a list (array) of reset controllers available with the device. These patches address the comments received for the earlier posted series [1,2]. The users can pass a list of reset controllers and the number of resets available in the driver or the

[PATCH v2 0/4] reset: APIs to manage a list of resets

Set of patches to support getting and de/asserting a list (array) of reset controllers available with the device. These patches address the comments received for the earlier posted series [1,2]. The users can pass a list of reset controllers and the number of resets available in the driver or the

[PATCH v2 4/4] soc/tegra: pmc: Use the new reset APIs to manage reset controllers

Make use of reset_control_array_*() set of APIs to manage an array of reset controllers available with the device. Cc: Thierry Reding Cc: Philipp Zabel Signed-off-by: Vivek Gautam --- Changes since v1: - New patch added to the series to enable this driver use the newer set of APIs that

[PATCH v2 2/4] reset: Add APIs to manage array of resets

Many devices may want to request a bunch of resets and control them. So it's better to manage them as an array. Add APIs to _get(), _assert(), and _deassert() an array of reset_control. Cc: Philipp Zabel Signed-off-by: Vivek Gautam ---

[PATCH v2 2/4] reset: Add APIs to manage array of resets

Many devices may want to request a bunch of resets and control them. So it's better to manage them as an array. Add APIs to _get(), _assert(), and _deassert() an array of reset_control. Cc: Philipp Zabel Signed-off-by: Vivek Gautam --- Changes since v1: - New patch added to the series.

[PATCH net-next] macb: Add hardware PTP support.

This patch is based on original Harini's patch and Andrei's patch, implemented in aseparate file to ease the review/maintanance and integration with other platforms. In case that macb is compiled as a module, it has been renamed to cadence-macb.ko to avoid naming confusion in Makefile. This

[PATCH net-next] macb: Add hardware PTP support.

This patch is based on original Harini's patch and Andrei's patch, implemented in aseparate file to ease the review/maintanance and integration with other platforms. In case that macb is compiled as a module, it has been renamed to cadence-macb.ko to avoid naming confusion in Makefile. This

Re: [alsa-devel][PATCH v2 2/2] ASoC: wm8960: Let wm8960 driver configure its bit clock and frame clock

On Mon, Apr 3, 2017 at 4:34 PM, Charles Keepax wrote: > On Mon, Apr 03, 2017 at 04:16:23PM +0300, Daniel Baluta wrote: >> On Thu, Jan 15, 2015 at 3:34 PM, Zidan Wang wrote: >> > On Wed, Jan 14, 2015 at 07:27:03PM +, Mark Brown wrote:

Re: [alsa-devel][PATCH v2 2/2] ASoC: wm8960: Let wm8960 driver configure its bit clock and frame clock

On Mon, Apr 3, 2017 at 4:34 PM, Charles Keepax wrote: > On Mon, Apr 03, 2017 at 04:16:23PM +0300, Daniel Baluta wrote: >> On Thu, Jan 15, 2015 at 3:34 PM, Zidan Wang wrote: >> > On Wed, Jan 14, 2015 at 07:27:03PM +, Mark Brown wrote: >> >> On Wed, Jan 07, 2015 at 03:31:45PM +0800, Zidan Wang

Re: [PATCH V7 3/7] Documentation: devicetree: mfd: da9062/61 MFD binding

On Tue, 28 Mar 2017, Steve Twiss wrote: > From: Steve Twiss > > Extend existing DA9062 binding information to include the DA9061 PMIC for > MFD core and regulators. > > Add a da9062-onkey link to the existing onkey binding file. > > Add a da9062-thermal link to

Re: [PATCH V7 3/7] Documentation: devicetree: mfd: da9062/61 MFD binding

On Tue, 28 Mar 2017, Steve Twiss wrote: > From: Steve Twiss > > Extend existing DA9062 binding information to include the DA9061 PMIC for > MFD core and regulators. > > Add a da9062-onkey link to the existing onkey binding file. > > Add a da9062-thermal link to the new temperature monitoring

[PATCH v3 1/2] dt-bindings: display: panel: Add bindings for the Sitronix ST7789V panel

The Sitronix ST7789V is an LCD panel controller, controlled over SPI, that can drive 18-bits 240x320 LCD displays. Signed-off-by: Maxime Ripard Acked-by: Rob Herring --- Documentation/devicetree/bindings/display/panel/sitronix,st7789v.txt | 37

[PATCH v3 1/2] dt-bindings: display: panel: Add bindings for the Sitronix ST7789V panel

The Sitronix ST7789V is an LCD panel controller, controlled over SPI, that can drive 18-bits 240x320 LCD displays. Signed-off-by: Maxime Ripard Acked-by: Rob Herring --- Documentation/devicetree/bindings/display/panel/sitronix,st7789v.txt | 37 + 1 file

[PATCH v3 2/2] drm/panel: Add driver for sitronix ST7789V LCD controller

The Sitronix ST7789v controller is used to drive 240x320 LCD panels through various interfaces, including SPI and RGB/Parallel. The current driver is configuring it for the latter. Support for tinyDRM can always be added later. Signed-off-by: Maxime Ripard ---

[PATCH v3 0/2] drm/panel: Add support for the Sitronix ST7789V

Hi, Here is an attempt at supporting the ST7789V LCD controller from Sitronix. It is controlled through an SPI bus, with a twist, since each byte sent must be prefixed by a bit, which needs an 9-bits-per-word SPI controller, which is quite rare. Else, you would need to bitbang it. Let me know

[PATCH v3 2/2] drm/panel: Add driver for sitronix ST7789V LCD controller

The Sitronix ST7789v controller is used to drive 240x320 LCD panels through various interfaces, including SPI and RGB/Parallel. The current driver is configuring it for the latter. Support for tinyDRM can always be added later. Signed-off-by: Maxime Ripard --- drivers/gpu/drm/panel/Kconfig

[PATCH v3 0/2] drm/panel: Add support for the Sitronix ST7789V

Hi, Here is an attempt at supporting the ST7789V LCD controller from Sitronix. It is controlled through an SPI bus, with a twist, since each byte sent must be prefixed by a bit, which needs an 9-bits-per-word SPI controller, which is quite rare. Else, you would need to bitbang it. Let me know

Re: [PATCH v2] i2c/muxes/i2c-mux-ltc4306: LTC4306 and LTC4305 I2C multiplexer/switch

On 03.04.2017 14:03, Peter Rosin wrote: On 2017-03-31 17:29, Peter Rosin wrote: Hi! Sorry for my incremental reviewing... Another incremental... On 2017-03-29 12:15, michael.henner...@analog.com wrote: + + /* Now create an adapter for each channel */ + for (num = 0; num <

Re: [PATCH v2] i2c/muxes/i2c-mux-ltc4306: LTC4306 and LTC4305 I2C multiplexer/switch

On 03.04.2017 14:03, Peter Rosin wrote: On 2017-03-31 17:29, Peter Rosin wrote: Hi! Sorry for my incremental reviewing... Another incremental... On 2017-03-29 12:15, michael.henner...@analog.com wrote: + + /* Now create an adapter for each channel */ + for (num = 0; num <

Re: [alsa-devel][PATCH v2 2/2] ASoC: wm8960: Let wm8960 driver configure its bit clock and frame clock

On Mon, Apr 03, 2017 at 04:16:23PM +0300, Daniel Baluta wrote: > On Thu, Jan 15, 2015 at 3:34 PM, Zidan Wang wrote: > > On Wed, Jan 14, 2015 at 07:27:03PM +, Mark Brown wrote: > >> On Wed, Jan 07, 2015 at 03:31:45PM +0800, Zidan Wang wrote: > > I found it can't generate

Re: [alsa-devel][PATCH v2 2/2] ASoC: wm8960: Let wm8960 driver configure its bit clock and frame clock

On Mon, Apr 03, 2017 at 04:16:23PM +0300, Daniel Baluta wrote: > On Thu, Jan 15, 2015 at 3:34 PM, Zidan Wang wrote: > > On Wed, Jan 14, 2015 at 07:27:03PM +, Mark Brown wrote: > >> On Wed, Jan 07, 2015 at 03:31:45PM +0800, Zidan Wang wrote: > > I found it can't generate bclk for S20_3LE data

[PATCH v3 1/2] i2c:mux:ltc4306: LTC4306 and LTC4305 I2C multiplexer/switch

From: Michael Hennerich This patch adds support for the Analog Devices / Linear Technology LTC4306 and LTC4305 4/2 Channel I2C Bus Multiplexer/Switches. The LTC4306 optionally provides two general purpose input/output pins (GPIOs) that can be configured as logic

[PATCH v3 1/2] i2c:mux:ltc4306: LTC4306 and LTC4305 I2C multiplexer/switch

From: Michael Hennerich This patch adds support for the Analog Devices / Linear Technology LTC4306 and LTC4305 4/2 Channel I2C Bus Multiplexer/Switches. The LTC4306 optionally provides two general purpose input/output pins (GPIOs) that can be configured as logic inputs, opendrain outputs or

[PATCH v3 2/2] dt-bindings:i2c:mux:ltc4306: Add dt-bindings for I2C multiplexer/switch

From: Michael Hennerich Signed-off-by: Michael Hennerich Acked-by: Rob Herring --- .../devicetree/bindings/i2c/i2c-mux-ltc4306.txt| 61 ++ 1 file changed, 61 insertions(+) create mode 100644

[PATCH v3 2/2] dt-bindings:i2c:mux:ltc4306: Add dt-bindings for I2C multiplexer/switch

From: Michael Hennerich Signed-off-by: Michael Hennerich Acked-by: Rob Herring --- .../devicetree/bindings/i2c/i2c-mux-ltc4306.txt| 61 ++ 1 file changed, 61 insertions(+) create mode 100644 Documentation/devicetree/bindings/i2c/i2c-mux-ltc4306.txt diff --git

Re: Build regressions/improvements in v4.11-rc5

On Mon, Apr 3, 2017 at 3:29 PM, Geert Uytterhoeven wrote: > JFYI, when comparing v4.11-rc5[1] to v4.11-rc4[3], the summaries are: > - build errors: +2/- Nothing to report. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux

Re: Build regressions/improvements in v4.11-rc5

On Mon, Apr 3, 2017 at 3:29 PM, Geert Uytterhoeven wrote: > JFYI, when comparing v4.11-rc5[1] to v4.11-rc4[3], the summaries are: > - build errors: +2/- Nothing to report. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 --

Build regressions/improvements in v4.11-rc5

Below is the list of build error/warning regressions/improvements in v4.11-rc5[1] compared to v4.10[2]. Summarized: - build errors: +4/-1 - build warnings: +1138/-891 JFYI, when comparing v4.11-rc5[1] to v4.11-rc4[3], the summaries are: - build errors: +2/- - build warnings: +367/-594

Build regressions/improvements in v4.11-rc5

Below is the list of build error/warning regressions/improvements in v4.11-rc5[1] compared to v4.10[2]. Summarized: - build errors: +4/-1 - build warnings: +1138/-891 JFYI, when comparing v4.11-rc5[1] to v4.11-rc4[3], the summaries are: - build errors: +2/- - build warnings: +367/-594

Re: [PATCH] mm/zswap: fix potential deadlock in zswap_frontswap_store()

On 04/03/2017 02:38 PM, Andrey Ryabinin wrote: > > > On 04/03/2017 03:37 PM, Andrey Ryabinin wrote: >> >> >> On 04/03/2017 11:47 AM, Michal Hocko wrote: >>> On Fri 31-03-17 10:00:30, Shakeel Butt wrote: On Fri, Mar 31, 2017 at 8:30 AM, Andrey Ryabinin wrote:

Re: [PATCH] mm/zswap: fix potential deadlock in zswap_frontswap_store()

On 04/03/2017 02:38 PM, Andrey Ryabinin wrote: > > > On 04/03/2017 03:37 PM, Andrey Ryabinin wrote: >> >> >> On 04/03/2017 11:47 AM, Michal Hocko wrote: >>> On Fri 31-03-17 10:00:30, Shakeel Butt wrote: On Fri, Mar 31, 2017 at 8:30 AM, Andrey Ryabinin wrote: >

Re: [PATCH] selftests: add a generic testsuite for ethernet device

> By ifnum, you mean by the order that "ip link" gives ? I've not checked if it remains in order as interfaces are hot plugged/unplugged. But i guess you are running tests direct after boot, and unplugs/replugs are unlikely? Andrew

Re: [PATCH] selftests: add a generic testsuite for ethernet device

> By ifnum, you mean by the order that "ip link" gives ? I've not checked if it remains in order as interfaces are hot plugged/unplugged. But i guess you are running tests direct after boot, and unplugs/replugs are unlikely? Andrew

Re: [PATCH 1/2] wireless: ath9k_htc: fix NULL-deref at probe

On Mon, Apr 03, 2017 at 01:21:08PM +, Kalle Valo wrote: > Johan Hovold writes: > > > On Mon, Apr 03, 2017 at 01:02:28PM +, Kalle Valo wrote: > >> Kalle Valo writes: > >> > >> > Johan Hovold writes: > >> > > >> >> On Mon, Mar

Re: [PATCH 1/2] wireless: ath9k_htc: fix NULL-deref at probe

On Mon, Apr 03, 2017 at 01:21:08PM +, Kalle Valo wrote: > Johan Hovold writes: > > > On Mon, Apr 03, 2017 at 01:02:28PM +, Kalle Valo wrote: > >> Kalle Valo writes: > >> > >> > Johan Hovold writes: > >> > > >> >> On Mon, Mar 13, 2017 at 01:44:20PM +0100, Johan Hovold wrote: > >> >>>

Re: [RFC PATCH] binder: Don't require the binder lock when killed in binder_thread_read()

On Sat, Apr 01, 2017 at 07:34:53PM -0700, Doug Anderson wrote: > Hi, > > On Fri, Mar 31, 2017 at 11:48 PM, Greg KH wrote: > > On Fri, Mar 31, 2017 at 02:00:13PM -0700, Doug Anderson wrote: > >> On Fri, Mar 31, 2017 at 12:29 PM, Greg KH >

Re: [RFC PATCH] binder: Don't require the binder lock when killed in binder_thread_read()

On Sat, Apr 01, 2017 at 07:34:53PM -0700, Doug Anderson wrote: > Hi, > > On Fri, Mar 31, 2017 at 11:48 PM, Greg KH wrote: > > On Fri, Mar 31, 2017 at 02:00:13PM -0700, Doug Anderson wrote: > >> On Fri, Mar 31, 2017 at 12:29 PM, Greg KH > >> wrote: > >> BTW: I presume that nobody has decided

Re: [PATCH 1/2] drm/sun4i: Add display backend interrupt to device tree binding

On Mon, Mar 27, 2017 at 10:38:46PM +0800, Chen-Yu Tsai wrote: > The display backend has an interrupt line. Add it to the device tree > binding. > > Signed-off-by: Chen-Yu Tsai > --- > Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 2 ++ > 1 file changed, 2

Re: [PATCH 1/2] drm/sun4i: Add display backend interrupt to device tree binding

On Mon, Mar 27, 2017 at 10:38:46PM +0800, Chen-Yu Tsai wrote: > The display backend has an interrupt line. Add it to the device tree > binding. > > Signed-off-by: Chen-Yu Tsai > --- > Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 2 ++ > 1 file changed, 2 insertions(+)

Re: [PATCH] mm/zswap: fix potential deadlock in zswap_frontswap_store()

On Mon 03-04-17 16:14:51, Andrey Ryabinin wrote: > > > On 04/03/2017 03:45 PM, Michal Hocko wrote: > > On Mon 03-04-17 15:37:07, Andrey Ryabinin wrote: > >> > >> > >> On 04/03/2017 11:47 AM, Michal Hocko wrote: > >>> On Fri 31-03-17 10:00:30, Shakeel Butt wrote: > On Fri, Mar 31, 2017 at

Re: [PATCH] mm/zswap: fix potential deadlock in zswap_frontswap_store()

On Mon 03-04-17 16:14:51, Andrey Ryabinin wrote: > > > On 04/03/2017 03:45 PM, Michal Hocko wrote: > > On Mon 03-04-17 15:37:07, Andrey Ryabinin wrote: > >> > >> > >> On 04/03/2017 11:47 AM, Michal Hocko wrote: > >>> On Fri 31-03-17 10:00:30, Shakeel Butt wrote: > On Fri, Mar 31, 2017 at

Re: [PATCH RFC v4 07/10] dt-bindings: net: add binding for QCA7000 UART

On Tue, Mar 28, 2017 at 06:18:03PM +0200, Stefan Wahren wrote: > Am 27.03.2017 um 22:30 schrieb Rob Herring: > > On Mon, Mar 27, 2017 at 8:37 AM, Stefan Wahren > > wrote: > >> This is the serdev binding for the QCA7000 UART driver (Ethernet over > >> UART). > >> > >>

Re: [PATCH RFC v4 07/10] dt-bindings: net: add binding for QCA7000 UART

On Tue, Mar 28, 2017 at 06:18:03PM +0200, Stefan Wahren wrote: > Am 27.03.2017 um 22:30 schrieb Rob Herring: > > On Mon, Mar 27, 2017 at 8:37 AM, Stefan Wahren > > wrote: > >> This is the serdev binding for the QCA7000 UART driver (Ethernet over > >> UART). > >> > >> Signed-off-by: Stefan

RE: [PATCH V7 6/7] thermal: da9062/61: Thermal junction temperature monitoring driver

On 01 April 2017 @20:59, Eduardo Valentin wrote: > Subject: Re: [PATCH V7 6/7] thermal: da9062/61: Thermal junction temperature > monitoring driver > > On Tue, Mar 28, 2017 at 03:43:33PM +0100, Steve Twiss wrote: > > From: Steve Twiss > > > > Add junction

RE: [PATCH V7 6/7] thermal: da9062/61: Thermal junction temperature monitoring driver

On 01 April 2017 @20:59, Eduardo Valentin wrote: > Subject: Re: [PATCH V7 6/7] thermal: da9062/61: Thermal junction temperature > monitoring driver > > On Tue, Mar 28, 2017 at 03:43:33PM +0100, Steve Twiss wrote: > > From: Steve Twiss > > > > Add junction temperature monitoring supervisor

Re: [PATCH 1/2] wireless: ath9k_htc: fix NULL-deref at probe

Johan Hovold writes: > On Mon, Apr 03, 2017 at 01:02:28PM +, Kalle Valo wrote: >> Kalle Valo writes: >> >> > Johan Hovold writes: >> > >> >> On Mon, Mar 13, 2017 at 01:44:20PM +0100, Johan Hovold wrote: >> >>> Make sure to check

Re: [PATCH 1/2] wireless: ath9k_htc: fix NULL-deref at probe

Johan Hovold writes: > On Mon, Apr 03, 2017 at 01:02:28PM +, Kalle Valo wrote: >> Kalle Valo writes: >> >> > Johan Hovold writes: >> > >> >> On Mon, Mar 13, 2017 at 01:44:20PM +0100, Johan Hovold wrote: >> >>> Make sure to check the number of endpoints to avoid dereferencing a >> >>>

Re: [PATCH 2/2] nvmem: imx-ocotp: add write support

On Mon, Mar 27, 2017 at 03:31:31PM +0200, Richard Leitner wrote: > Implement write routine for OCOTP controller found in i.MX6 SoC's. > Furthermore add locking to the read function to prevent race conditions. > The write routine code is based on the fsl_otp driver from Freescale. > >

Re: [PATCH 2/2] nvmem: imx-ocotp: add write support

On Mon, Mar 27, 2017 at 03:31:31PM +0200, Richard Leitner wrote: > Implement write routine for OCOTP controller found in i.MX6 SoC's. > Furthermore add locking to the read function to prevent race conditions. > The write routine code is based on the fsl_otp driver from Freescale. > >

Re: [alsa-devel][PATCH v2 2/2] ASoC: wm8960: Let wm8960 driver configure its bit clock and frame clock

On Thu, Jan 15, 2015 at 3:34 PM, Zidan Wang wrote: > On Wed, Jan 14, 2015 at 07:27:03PM +, Mark Brown wrote: >> On Wed, Jan 07, 2015 at 03:31:45PM +0800, Zidan Wang wrote: >> >> > + for (i = 0; i < ARRAY_SIZE(dac_divs); ++i) { >> > + if (wm8960->sysclk ==

Re: [PATCH 1/2] wireless: ath9k_htc: fix NULL-deref at probe

On Mon, Apr 03, 2017 at 01:02:28PM +, Kalle Valo wrote: > Kalle Valo writes: > > > Johan Hovold writes: > > > >> On Mon, Mar 13, 2017 at 01:44:20PM +0100, Johan Hovold wrote: > >>> Make sure to check the number of endpoints to avoid dereferencing a >

Re: [alsa-devel][PATCH v2 2/2] ASoC: wm8960: Let wm8960 driver configure its bit clock and frame clock

On Thu, Jan 15, 2015 at 3:34 PM, Zidan Wang wrote: > On Wed, Jan 14, 2015 at 07:27:03PM +, Mark Brown wrote: >> On Wed, Jan 07, 2015 at 03:31:45PM +0800, Zidan Wang wrote: >> >> > + for (i = 0; i < ARRAY_SIZE(dac_divs); ++i) { >> > + if (wm8960->sysclk == lrclk * dac_divs[i]) { >>

Re: [PATCH 1/2] wireless: ath9k_htc: fix NULL-deref at probe

On Mon, Apr 03, 2017 at 01:02:28PM +, Kalle Valo wrote: > Kalle Valo writes: > > > Johan Hovold writes: > > > >> On Mon, Mar 13, 2017 at 01:44:20PM +0100, Johan Hovold wrote: > >>> Make sure to check the number of endpoints to avoid dereferencing a > >>> NULL-pointer or accessing memory

Re: [PATCH] selftests: add a generic testsuite for ethernet device

On Fri, Mar 31, 2017 at 04:12:41PM +0200, Andrew Lunn wrote: > On Fri, Mar 31, 2017 at 02:57:52PM +0200, Corentin Labbe wrote: > > This patch add a generic testsuite for testing ethernet network device > > driver. > > > > Signed-off-by: Corentin Labbe > > --- > >

Re: [PATCH] selftests: add a generic testsuite for ethernet device

On Fri, Mar 31, 2017 at 04:12:41PM +0200, Andrew Lunn wrote: > On Fri, Mar 31, 2017 at 02:57:52PM +0200, Corentin Labbe wrote: > > This patch add a generic testsuite for testing ethernet network device > > driver. > > > > Signed-off-by: Corentin Labbe > > --- > >

Re: linux-next: manual merge of the net-next tree with the net tree

On 04/03/2017 04:07 AM, Stephen Rothwell wrote: Hi all, Today's linux-next merge of the net-next tree got conflicts in: tools/testing/selftests/bpf/Makefile tools/testing/selftests/bpf/test_verifier.c between commit: 02ea80b1850e ("bpf: add various verifier test cases for

Re: linux-next: manual merge of the net-next tree with the net tree

On 04/03/2017 04:07 AM, Stephen Rothwell wrote: Hi all, Today's linux-next merge of the net-next tree got conflicts in: tools/testing/selftests/bpf/Makefile tools/testing/selftests/bpf/test_verifier.c between commit: 02ea80b1850e ("bpf: add various verifier test cases for

Re: [PATCH v2] scsi: storvsc: Add support for FC rport.

On 04/03/2017 08:17 AM, Christoph Hellwig wrote: if (host->transportt == fc_transport_template) { + struct fc_rport_identifiers ids = { + .roles = FC_PORT_ROLE_FCP_TARGET, + }; I don't think storvsc ever acts as FCP target. In order to

Re: [PATCH v2] scsi: storvsc: Add support for FC rport.

On 04/03/2017 08:17 AM, Christoph Hellwig wrote: if (host->transportt == fc_transport_template) { + struct fc_rport_identifiers ids = { + .roles = FC_PORT_ROLE_FCP_TARGET, + }; I don't think storvsc ever acts as FCP target. In order to

Re: [PATCH] mm/zswap: fix potential deadlock in zswap_frontswap_store()

On 04/03/2017 03:45 PM, Michal Hocko wrote: > On Mon 03-04-17 15:37:07, Andrey Ryabinin wrote: >> >> >> On 04/03/2017 11:47 AM, Michal Hocko wrote: >>> On Fri 31-03-17 10:00:30, Shakeel Butt wrote: On Fri, Mar 31, 2017 at 8:30 AM, Andrey Ryabinin wrote: >

Re: [PATCH] mm/zswap: fix potential deadlock in zswap_frontswap_store()

On 04/03/2017 03:45 PM, Michal Hocko wrote: > On Mon 03-04-17 15:37:07, Andrey Ryabinin wrote: >> >> >> On 04/03/2017 11:47 AM, Michal Hocko wrote: >>> On Fri 31-03-17 10:00:30, Shakeel Butt wrote: On Fri, Mar 31, 2017 at 8:30 AM, Andrey Ryabinin wrote: > zswap_frontswap_store()

Re: [PATCH 3/4] sparc: convert mdesc_handle.refcnt from atomic_t to refcount_t

From: "Reshetova, Elena" Date: Mon, 3 Apr 2017 07:28:01 + > >> From: Elena Reshetova >> Date: Mon, 20 Feb 2017 13:06:20 +0200 >> >> > refcount_t type and corresponding API should be >> > used instead of atomic_t when the variable is

Re: [PATCH 3/4] sparc: convert mdesc_handle.refcnt from atomic_t to refcount_t

From: "Reshetova, Elena" Date: Mon, 3 Apr 2017 07:28:01 + > >> From: Elena Reshetova >> Date: Mon, 20 Feb 2017 13:06:20 +0200 >> >> > refcount_t type and corresponding API should be >> > used instead of atomic_t when the variable is used as >> > a reference counter. This allows to avoid

Re: [PATCH] [net-next] stmmac: use netif_set_real_num_{rx,tx}_queues

Hello Peppe, Às 2:07 PM de 4/3/2017, Giuseppe CAVALLARO escreveu: > Hello Joao > > On 3/30/2017 6:42 PM, Joao Pinto wrote: >> Às 5:35 PM de 3/30/2017, Niklas Cassel escreveu: >>> On 03/30/2017 04:34 PM, Thierry Reding wrote: On Thu, Mar 30, 2017 at 09:45:36AM +0200, Corentin Labbe wrote:

Re: [PATCH] [net-next] stmmac: use netif_set_real_num_{rx,tx}_queues

Hello Peppe, Às 2:07 PM de 4/3/2017, Giuseppe CAVALLARO escreveu: > Hello Joao > > On 3/30/2017 6:42 PM, Joao Pinto wrote: >> Às 5:35 PM de 3/30/2017, Niklas Cassel escreveu: >>> On 03/30/2017 04:34 PM, Thierry Reding wrote: On Thu, Mar 30, 2017 at 09:45:36AM +0200, Corentin Labbe wrote:

<    6   7   8   9   10   11   12   13   14   15   >