Re: [PATCH] staging: greybus: arche-apb-ctrl: fix unused warnings on resume/suspend

On Sat, Dec 17, 2016 at 6:03 AM, Jérémy Lefaure wrote: > When CONFIG_PM_SLEEP is disabled, SIMPLE_DEV_PM_OPS does not use > arche_apb_ctrl_resume and arche_apb_ctrl_suspend functions: > > drivers/staging/greybus/arche-apb-ctrl.c:478:12: warning: >

Re: [PATCH] staging: gdm724x: add forced casts in endian converters to fix sparse warnings

On Tue, Jan 03, 2017 at 04:30:58PM +0100, Greg KH wrote: > On Wed, Dec 28, 2016 at 10:08:43PM -0800, Eric S. Stone wrote: > > The modified functions do explicit endian checking and conversion. The > > added forced casts fix these sparse warnings: > > > > CHECK

Re: Designated initializers, struct randomization and addressing?

On Tue, Jan 3, 2017 at 10:27 PM, Julia Lawall wrote: > > > On Tue, 3 Jan 2017, Kees Cook wrote: > >> On Tue, Dec 20, 2016 at 9:29 AM, Joe Perches wrote: >> > On Fri, 2016-12-16 at 17:00 -0800, Kees Cook wrote: >> >> Prepare to mark sensitive kernel

Re: Designated initializers, struct randomization and addressing?

On Tue, 3 Jan 2017, Kees Cook wrote: > On Tue, Dec 20, 2016 at 9:29 AM, Joe Perches wrote: > > On Fri, 2016-12-16 at 17:00 -0800, Kees Cook wrote: > >> Prepare to mark sensitive kernel structures for randomization by making > > sure they're using designated initializers. > >

[PATCH] staging:iio:addac Fixes Alignment should match open parenthesis

Fixes style issue where Alignment doesn't match open parenthesis Signed-off-by: Scott Matheina --- drivers/staging/iio/addac/adt7316-i2c.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/iio/addac/adt7316-i2c.c

Re: Designated initializers, struct randomization and addressing?

On Tue, Jan 3, 2017 at 3:55 PM, Bruce Korb wrote: > On Tue, Jan 3, 2017 at 3:47 PM, Kees Cook wrote: >>> how is the code to be verified so that >>> any use of things like offsetof and any >>> address/indexing is not impacted? > > As a tangential

[PATCH net-next] net/hyperv: remove use of VLAN_TAG_PRESENT

Signed-off-by: Michał Mirosław --- drivers/net/hyperv/hyperv_net.h | 2 +- drivers/net/hyperv/netvsc_drv.c | 13 ++--- drivers/net/hyperv/rndis_filter.c | 4 ++-- 3 files changed, 9 insertions(+), 10 deletions(-) diff --git

[PATCH v3 0/4] drivers/staging/greybus: add async operations

V3: Picard: "Let's make sure history never forgets the name ... Enterprise." Drop gb_operation_cancel_async. The sync version works just as well - Johan V2: Scotty : "What are you standing around for - do you not know a jailbreak when you see one" ? Making sure to run format-patch against the

[PATCH v3 1/4] staging: greybus: operation: add generic asynchronous timeout operation support

This patch adds a generic mechanism for handling timeouts of asynchronous operations to operation.c. After doing a gb_operation_request_send() it schedules a delayed worker. When the delayed worker's timer expires the worker runs and does a gb_operation_cancel(). A gb_operation_cancel() operation

[PATCH v3 4/4] staging: greybus: loopback: convert to use msecs internally

The API presented by operation.h expects milliseconds to be passed in. This patch drops the conversion from user-input microseconds-to-jiffies and from jiffies-to-milliseconds and instead converts directly from microseconds-to-milliseconds. The new minimum timeout will be one millisecond as

[PATCH v3 2/4] staging: greybus: operation: add private data with get/set accessors

Asynchronous operation completion handler's lives are made easier if there is a generic pointer that can store private data associated with the operation. This patch adds a pointer field to operation.h and get/set methods to access that pointer. Signed-off-by: Bryan O'Donoghue

[PATCH v3 3/4] staging: greybus: loopback: convert loopback to use generic async operations

Loopback has its own internal method for tracking and timing out asynchronous operations however previous patches make it possible to use functionality provided by operation.c to do this instead. Using the code in operation.c means we can completely subtract the timer, the work-queue, the kref and

Re: Designated initializers, struct randomization and addressing?

As a tangential party, I am a bit curious: does the randomization plugin result in a compact structure? I ask because I know many/most programmers don't bother with it and so doing so ought to make the data more compact. On Tue, Jan 3, 2017 at 3:47 PM, Kees Cook wrote: >>

Re: Designated initializers, struct randomization and addressing?

On Tue, Dec 20, 2016 at 9:29 AM, Joe Perches wrote: > On Fri, 2016-12-16 at 17:00 -0800, Kees Cook wrote: >> Prepare to mark sensitive kernel structures for randomization by making > sure they're using designated initializers. > > About the designated initializer patches, >

Re: [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging

On Tuesday, January 3, 2017 11:57:36 PM CET Paul Bolle wrote: > On Tue, 2017-01-03 at 23:25 +0100, Arnd Bergmann wrote: > > As far as I'm concerned, we are totally fine as long as there exists a > > longterm supported kernel that has i4l in drivers/staging. > > Or in drivers/isdn, right? Right,

Re: [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging

On Tue, 2017-01-03 at 23:25 +0100, Arnd Bergmann wrote: > As far as I'm concerned, we are totally fine as long as there exists a > longterm supported kernel that has i4l in drivers/staging. Or in drivers/isdn, right? Paul Bolle ___ devel mailing list

Re: [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging

On Tuesday, January 3, 2017 10:54:19 PM CET Paul Bolle wrote: > On Tue, 2017-01-03 at 22:19 +0100, Arnd Bergmann wrote: > > isdn: move isdnhdlc out of i4l > > isdn: i4l: move hisax driver to staging > > isdn: move i4l to staging > > > > I can post those as well, at least I think the first two are

Re: [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging

On Tue, 2017-01-03 at 22:19 +0100, Arnd Bergmann wrote: > Sounds good to me. My original series contained four more patches that > I did not post again after there was some concern[1] that we did not > come to a conclusion on: > > isdn: gigaset: remove i4l code Let me repeat that I'm fine with a

RE: [PATCH 7/8] staging: fsl-dpaa2/eth: Add TODO file

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Tuesday, January 03, 2017 10:48 AM > To: Stuart Yoder > Cc: de...@driverdev.osuosl.org; a...@arndb.de; Roy Pledge > ; Alexandru Marginean >

Re: [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging

On Tuesday, January 3, 2017 4:24:36 PM CET Greg Kroah-Hartman wrote: > On Wed, Mar 02, 2016 at 08:06:46PM +0100, Arnd Bergmann wrote: > > The icn, act2000 and pcbit drivers are all for very old hardware, > > and it is highly unlikely that anyone is actually still using them > > on modern kernels,

Re: [PATCH 11/20] media: Add i.MX media core driver

On Thu, Dec 29, 2016 at 02:27:26PM -0800, Steve Longerbeam wrote: > Add the core media driver for i.MX SOC. > > Signed-off-by: Steve Longerbeam > --- > Documentation/devicetree/bindings/media/imx.txt | 205 + > Documentation/media/v4l-drivers/imx.rst

Re: [PATCH 00/20] i.MX Media Driver

Hi Fabio, On 01/02/2017 01:09 PM, Fabio Estevam wrote: Hi Steve, On Thu, Dec 29, 2016 at 8:27 PM, Steve Longerbeam wrote: This is a media driver for video capture on i.MX. Refer to Documentation/media/v4l-drivers/imx.rst for example capture pipelines on SabreSD,

Re: [PATCH v2 00/19] i.MX Media Driver

On Tue, Jan 3, 2017 at 6:57 PM, Steve Longerbeam wrote: > In version 2 (no functional changes): > > - removed patch "gpio: pca953x: Add optional reset gpio control", it > has been submitted separately. > - fixed some whitespace errors. > - added a few missing

[PATCH v2 2/2] staging: unisys: visorbus: Don't check for more than PAGE_SIZE length in visorbus

From: David Binder Since a sysfs entry is allocated 1 page of memory (4096 bytes) by default, there is no need to enforce this limit in the driver. This patch corrects visorbus/visorbus_main.c. Reported-by: Greg Kroah-Hartman Signed-off-by:

[PATCH v2 0/2] staging: unisys: visorbus: Don't check for more than PAGE_SIZE

This series is just a resubmission of the last 2 patches from our previous series. It just removes extraneous PAGE_SIZE checks. Changes since v1: -- Remove references to procfs since we are only dealing with sysfs David Binder (2): staging: unisys: visorbus: visorchipset.c: Don't

[PATCH v2 1/2] staging: unisys: visorbus: visorchipset.c: Don't check for more than PAGE_SIZE length

From: David Binder Since a sysfs entry is allocated 1 page of memory (4096 bytes) by default, there is no need to enforce this limit in the driver. This patch corrects visorbus/visorchipset.c. Signed-off-by: David Binder Signed-off-by: David

[PATCH v2 17/19] media: imx: Add MIPI CSI-2 OV5640 sensor subdev driver

This driver is based on ov5640_mipi.c from Freescale imx_3.10.17_1.0.0_beta branch, modified heavily to bring forward to latest interfaces and code cleanup. Signed-off-by: Steve Longerbeam --- drivers/staging/media/imx/Kconfig |8 +

[PATCH v2 16/19] media: imx: Add video switch subdev driver

From: Philipp Zabel This driver can handle SoC internal and extern video bus multiplexers, controlled either by register bit fields or by GPIO. Signed-off-by: Sascha Hauer Signed-off-by: Philipp Zabel Signed-off-by: Steve

[PATCH v2 19/19] ARM: imx_v6_v7_defconfig: Enable staging video4linux drivers

Enable imx v4l2 staging drivers. For video capture on the SabreAuto, the ADV7180 video decoder also requires the i2c-mux-gpio and the max7310 port expander. The Sabrelite requires PWM clocks for the OV5640. Signed-off-by: Steve Longerbeam ---

[PATCH v2 13/19] media: imx: Add IC subdev drivers

This is a set of three media entity subdevice drivers for the i.MX Image Converter. The i.MX IC module contains three independent "tasks": - Pre-processing Encode task: video frames are routed directly from the CSI and can be scaled, color-space converted, and rotated. Scaled output is

[PATCH v2 15/19] media: imx: Add MIPI CSI-2 Receiver subdev driver

Adds MIPI CSI-2 Receiver subdev driver. This subdev is required for sensors with a MIPI CSI2 interface. Signed-off-by: Steve Longerbeam --- drivers/staging/media/imx/Makefile| 1 + drivers/staging/media/imx/imx-mipi-csi2.c | 509

[PATCH v2 14/19] media: imx: Add Camera Interface subdev driver

This is the camera interface driver that provides the v4l2 user interface. Frames can be received from various sources: - directly from SMFC for capturing unconverted images directly from camera sensors. - from the IC pre-process encode task. - from the IC pre-process viewfinder task. - from

[PATCH v2 10/19] media: Add i.MX media core driver

Add the core media driver for i.MX SOC. Signed-off-by: Steve Longerbeam --- Documentation/devicetree/bindings/media/imx.txt | 205 + Documentation/media/v4l-drivers/imx.rst | 430 ++ drivers/staging/media/Kconfig | 2 +

[PATCH v2 11/19] media: imx: Add CSI subdev driver

This is a media entity subdevice for the i.MX Camera Serial Interface module. Signed-off-by: Steve Longerbeam --- drivers/staging/media/imx/Kconfig | 13 + drivers/staging/media/imx/Makefile | 2 + drivers/staging/media/imx/imx-csi.c | 638

[PATCH v2 12/19] media: imx: Add SMFC subdev driver

This is a media entity subdevice driver for the i.MX Sensor Multi-FIFO Controller module. Video frames are received from the CSI and can be routed to various sinks including the i.MX Image Converter for scaling, color-space conversion, motion compensated deinterlacing, and image rotation.

[PATCH v2 06/19] ARM: dts: imx6-sabreauto: create i2cmux for i2c3

The sabreauto uses a steering pin to select between the SDA signal on i2c3 bus, and a data-in pin for an SPI NOR chip. Use i2cmux to control this steering pin. Idle state of the i2cmux selects SPI NOR. This is not a classic way to use i2cmux, since one side of the mux selects something other than

[PATCH v2 07/19] ARM: dts: imx6-sabreauto: add reset-gpios property for max7310_b

The reset pin to the port expander chip (MAX7310) is controlled by a gpio, so define a reset-gpios property to control it. There are three MAX7310's on the SabreAuto CPU card (max7310_[abc]), but all use the same pin for their reset. Since all can't acquire the same pin, assign it to max7310_b,

[PATCH v2 08/19] ARM: dts: imx6-sabreauto: add pinctrl for gpt input capture

Add pinctrl groups for both GPT input capture channels. Signed-off-by: Steve Longerbeam --- arch/arm/boot/dts/imx6qdl-sabreauto.dtsi | 12 1 file changed, 12 insertions(+) diff --git a/arch/arm/boot/dts/imx6qdl-sabreauto.dtsi

[PATCH v2 09/19] ARM: dts: imx6-sabreauto: add the ADV7180 video decoder

Enables the ADV7180 decoder sensor. The ADV7180 connects to the parallel-bus mux input on ipu1_csi0_mux. On the sabreauto, two analog video inputs are routed to the ADV7180, composite on Ain1, and composite on Ain3. Those inputs are defined via inputs and input-names under the ADV7180 node. The

[PATCH v2 04/19] ARM: dts: imx6-sabrelite: add OV5642 and OV5640 camera sensors

Enables the OV5642 parallel-bus sensor, and the OV5640 MIPI CSI-2 sensor. Both hang off the same i2c2 bus, so they require different (and non- default) i2c slave addresses. The OV5642 connects to the parallel-bus mux input port on ipu1_csi0_mux. The OV5640 connects to the input port on the MIPI

[PATCH v2 05/19] ARM: dts: imx6-sabresd: add OV5642 and OV5640 camera sensors

Enables the OV5642 parallel-bus sensor, and the OV5640 MIPI CSI-2 sensor. The OV5642 connects to the parallel-bus mux input port on ipu1_csi0_mux. The OV5640 connects to the input port on the MIPI CSI-2 receiver on mipi_csi. It is set to transmit over MIPI virtual channel 1. Until the OV5652

[PATCH v2 03/19] ARM: dts: imx6qdl: add media device

Signed-off-by: Steve Longerbeam --- arch/arm/boot/dts/imx6q.dtsi | 4 arch/arm/boot/dts/imx6qdl.dtsi | 8 2 files changed, 12 insertions(+) diff --git a/arch/arm/boot/dts/imx6q.dtsi b/arch/arm/boot/dts/imx6q.dtsi index 56a314f..2fbe0b3 100644 ---

[PATCH v2 01/19] ARM: dts: imx6qdl: Add compatible, clocks, irqs to MIPI CSI-2 node

Add to the MIPI CSI2 receiver node: compatible string, interrupt sources, clocks. Signed-off-by: Steve Longerbeam --- arch/arm/boot/dts/imx6qdl.dtsi | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm/boot/dts/imx6qdl.dtsi

[PATCH v2 02/19] ARM: dts: imx6qdl: Add mipi_ipu1/2 multiplexers, mipi_csi, and their connections

From: Philipp Zabel This patch adds the device tree graph connecting the input multiplexers to the IPU CSIs and the MIPI-CSI2 gasket on i.MX6. The MIPI_IPU multiplexers are added as children of the iomuxc-gpr syscon device node. On i.MX6Q/D two two-input multiplexers in

[PATCH v2 00/19] i.MX Media Driver

In version 2 (no functional changes): - removed patch "gpio: pca953x: Add optional reset gpio control", it has been submitted separately. - fixed some whitespace errors. - added a few missing Signed-off-by's. Philipp Zabel (2): ARM: dts: imx6qdl: Add mipi_ipu1/2 multiplexers, mipi_csi, and

[PATCH net-next v2 26/27] net/hyperv: enable passing of VLAN.CFI bit

Signed-off-by: Michał Mirosław --- drivers/net/hyperv/netvsc_drv.c | 1 + drivers/net/hyperv/rndis_filter.c | 1 + 2 files changed, 2 insertions(+) diff --git a/drivers/net/hyperv/netvsc_drv.c b/drivers/net/hyperv/netvsc_drv.c index 6597d7901929..4e20f4c247fa 100644

[PATCH net-next v2 08/27] net/hyperv: remove use of VLAN_TAG_PRESENT

Signed-off-by: Michał Mirosław --- drivers/net/hyperv/hyperv_net.h | 2 +- drivers/net/hyperv/netvsc_drv.c | 13 ++--- drivers/net/hyperv/rndis_filter.c | 4 ++-- 3 files changed, 9 insertions(+), 10 deletions(-) diff --git

RE: [PATCH 3/4] hv_util: use do_adjtimex() to update system time

> -Original Message- > From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] > Sent: Tuesday, January 3, 2017 4:32 AM > To: Alex Ng (LIS) > Cc: de...@linuxdriverproject.org; linux-ker...@vger.kernel.org; KY > Srinivasan ; Haiyang Zhang

Re: [PATCH] staging: greybus: add host device function pointer checks

On Mon, Jan 02, 2017 at 02:54:37PM +0100, Johan Hovold wrote: > On Tue, Dec 20, 2016 at 02:49:27PM -0600, Jason Hrycay wrote: > > Add sanity checks for cport_quiesce and cport_clear before invoking the > > callbacks as these function pointers are not required during the host > > device

[PATCH v3 3/5] staging: fbtft: propagate error code from kstrto*()

kstrto*() functions return proper error code. Do propogate it to the user. Signed-off-by: Andy Shevchenko --- drivers/staging/fbtft/fbtft-sysfs.c | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/drivers/staging/fbtft/fbtft-sysfs.c

[PATCH v3 1/5] staging: fbtft: convert fbtft_reset() to be non-atomic

First of all, fbtft in current state doesn't allow to override GPIOs to be optional, like "reset" one. It might be a bug somewhere, but rather out of scope of this fix. Second, not all GPIOs available on the board would be SoC based, some of them might sit on I2C GPIO expanders, for example, on

[PATCH v3 5/5] staging: fbtft: fb_ssd1306: Refactor write_vmem()

Refactor write_vmem() for sake of readability. While here, fix indentation in one comment. Acked-by: Noralf Trønnes Signed-off-by: Andy Shevchenko --- drivers/staging/fbtft/fb_ssd1306.c | 16 +++- 1 file changed, 7

Re: [PATCH 0/6] staging: vchiq_arm: Fine-tuning for some function implementations

On Tue, Jan 03, 2017 at 09:46:51AM -0800, Eric Anholt wrote: > SF Markus Elfring writes: > > > From: Markus Elfring > > Date: Sat, 31 Dec 2016 22:42:34 +0100 > > > > Some update suggestions were taken into account > > from static

[PATCH v3 2/5] staging: fbtft: remove custom DMA mapped buffer

There is no need to duplicate what SPI core already does, i.e. mapping buffers for DMA capable transfers. Remove all related pices of code. Note, that code, besides its redundancy, was buggy: DMA address potentially can be 0, SPI slave device has nothing to do with DMA capable device properties

[PATCH v3 0/5] fbtft: make it work with DMA enabled SPI

This series enables 64x48 OLED display and fixes the driver to work with DMA enabled SPI properly. Has been tested on Intel Edison board with Adafruit 2'8" and SSD1306 64x48 (Sparkfun for Intel Edison) OLED displays at their maximum speed (25MHz and 10MHz). Since v2: - fix kbuild bot warning -

[PATCH v3 4/5] staging: fbtft: fb_ssd1306: Support smaller screen sizes

There is 64x48 display exists. In order to support that set multiplexer to 48 pixels and window address to proper position in the graphic display data RAM. Acked-by: Noralf Trønnes Signed-off-by: Andy Shevchenko ---

Re: [PATCH 0/6] staging: vchiq_arm: Fine-tuning for some function implementations

SF Markus Elfring writes: > From: Markus Elfring > Date: Sat, 31 Dec 2016 22:42:34 +0100 > > Some update suggestions were taken into account > from static source code analysis. This series is: Reviewed-by: Eric Anholt

Re: [PATCH v2 5/6] staging: fbtft: fb_ssd1306: Support smaller screen sizes

Den 02.01.2017 12:35, skrev Andy Shevchenko: There is 64x48 display exists. In order to support that set multiplexer to 48 pixels and window address to proper position in the graphic display data RAM. Signed-off-by: Andy Shevchenko --- Patches 5 and 6:

Re: [PATCH] staging: fwserial: fix checkpatch alignment check

On Tue, Jan 03, 2017 at 10:16:00PM +, Abdul Rauf Mujahid wrote: > > > On 01/03/2017 03:28 PM, Greg KH wrote: > > On Sun, Jan 01, 2017 at 01:00:59AM +, Abdul Rauf wrote: > >> Fix the following checks: > >> Alignment should match open parenthesis. > >> > >> Signed-off-by: Abdul Rauf

Re: [PATCH v2 3/6] staging: fbtft: fallback to usual allocation when DMA fails

Den 03.01.2017 17:12, skrev Andy Shevchenko: On Mon, 2017-01-02 at 13:35 +0200, Andy Shevchenko wrote: Fall back to usual allocation method if DMA coherent allocation fails. SPI framework will map and use DMA mapped memory when possible. Locally I have re-done DMA approach and thus this

Re: [PATCH v2 1/6] staging: fbtft: convert fbtft_reset() to be non-atomic

Den 02.01.2017 12:35, skrev Andy Shevchenko: First of all, fbtft in current state doesn't allow to override GPIOs to be optional, like "reset" one. It might be a bug somewhere, but rather out of scope of this fix. Second, not all GPIOs available on the board would be SoC based, some of them

Re: [PATCH v2 2/6] staging: fbtft: do not override DMA coherent mask

Den 03.01.2017 14:58, skrev Andy Shevchenko: On Tue, 2017-01-03 at 12:51 +0200, Andy Shevchenko wrote: On Mon, 2017-01-02 at 19:14 +0100, Noralf Trønnes wrote: Den 02.01.2017 12:35, skrev Andy Shevchenko: Usually it's not consumer's business to override resources passed from provider, in

Re: [PATCH] staging: fwserial: fix checkpatch alignment check

On 01/03/2017 03:28 PM, Greg KH wrote: > On Sun, Jan 01, 2017 at 01:00:59AM +, Abdul Rauf wrote: >> Fix the following checks: >> Alignment should match open parenthesis. >> >> Signed-off-by: Abdul Rauf >> --- >> drivers/staging/fwserial/fwserial.c | 5 +++-- >>

Re: [PATCH 7/8] staging: fsl-dpaa2/eth: Add TODO file

On Tue, Dec 06, 2016 at 06:10:38PM +, Stuart Yoder wrote: > > > > -Original Message- > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Tuesday, December 06, 2016 11:56 AM > > To: Stuart Yoder > > Cc: Ruxandra Ioana Radulescu

Re: [PATCH] staging: octeon: Call SET_NETDEV_DEV()

On Tue, Dec 27, 2016 at 02:15:57PM -0800, Florian Fainelli wrote: > On 12/20/2016 07:20 PM, David Miller wrote: > > From: Florian Fainelli > > Date: Tue, 20 Dec 2016 17:02:37 -0800 > > > >> On 12/14/2016 05:13 PM, Florian Fainelli wrote: > >>> The Octeon driver calls into

Re: [PATCH 2/3] staging: rtl8188eu: remove unused function _linked_rx_signal_strehgth_display

On Fri, Dec 30, 2016 at 12:01:05AM +0100, Luca Ceresoli wrote: > Not referenced anymore since the removal of field bRxRSSIDisplay in > struct adapter. > > Cc: Greg Kroah-Hartman > Cc: Larry Finger > Cc: Ivan Safonov >

Re: [PATCH v2 3/6] staging: fbtft: fallback to usual allocation when DMA fails

On Mon, 2017-01-02 at 13:35 +0200, Andy Shevchenko wrote: > Fall back to usual allocation method if DMA coherent allocation fails. > > SPI framework will map and use DMA mapped memory when possible. Locally I have re-done DMA approach and thus this patch became optional. Should I leave or

Re: [PATCH v2 0/2] staging: greybus: loopback fixes and updates

On Thu, Dec 22, 2016 at 12:37:27AM +, Bryan O'Donoghue wrote: > Two simple patches here resulting from using greybus on gbsim and > developing support for async. I found a bug in the user-space tool and > while doing that decided to update the kernel thread to be better behaved > when waiting

Re: [PATCH v2 0/6] fbtft: make it work with DMA enabled SPI

On Tue, 2017-01-03 at 16:27 +0100, Greg Kroah-Hartman wrote: > On Mon, Jan 02, 2017 at 01:37:43PM +0200, Andy Shevchenko wrote: > > On Mon, 2017-01-02 at 13:35 +0200, Andy Shevchenko wrote: > > > This series enables 64x48 OLED display and fixes the driver to > > > work > > > with DMA > > > enabled

Re: [PATCH] Staging: ks7010: ks7010_sdio.h: Fixed coding style error

On Fri, Dec 09, 2016 at 07:38:36PM +, Manoj Sawai wrote: > Error - Complex macro not in parentheses and trailing whitespace That's two different things, please make two different patches. thanks, greg k-h ___ devel mailing list

Re: [PATCH] staging: gdm724x: add forced casts in endian converters to fix sparse warnings

On Wed, Dec 28, 2016 at 10:08:43PM -0800, Eric S. Stone wrote: > The modified functions do explicit endian checking and conversion. The > added forced casts fix these sparse warnings: > > CHECK drivers/staging/gdm724x/gdm_endian.c > drivers/staging/gdm724x/gdm_endian.c:28:24: warning: incorrect

Re: [PATCH] staging: fwserial: fix checkpatch alignment check

On Sun, Jan 01, 2017 at 01:00:59AM +, Abdul Rauf wrote: > Fix the following checks: > Alignment should match open parenthesis. > > Signed-off-by: Abdul Rauf > --- > drivers/staging/fwserial/fwserial.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) >

Re: [PATCH v2 0/6] fbtft: make it work with DMA enabled SPI

On Mon, Jan 02, 2017 at 01:37:43PM +0200, Andy Shevchenko wrote: > On Mon, 2017-01-02 at 13:35 +0200, Andy Shevchenko wrote: > > This series enables 64x48 OLED display and fixes the driver to work > > with DMA > > enabled SPI properly. > > > > Has been tested on Intel Edison board with Adafruit

Re: [PATCH] drivers: staging: fbtft: fix checkpatch error and udelay

On Mon, Dec 19, 2016 at 07:44:42PM +0200, Ozgur Karatas wrote: > 19.12.2016, 08:35, "Greg KH" : > > On Sun, Dec 18, 2016 at 11:47:30AM -0600, Scott Matheina wrote: > >>  These changes where identified by checkpatch.pl as needed changes to > >>  align the code with the

Re: [PATCH] staging: i4l :fixed coding style

On Fri, Dec 09, 2016 at 11:06:26AM +0530, Tabrez khan wrote: > Remove braces {} for single if statement block. > > Signed-off-by: Tabrez khan > --- > drivers/staging/i4l/act2000/module.c | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) This patch doesn't apply

Re: [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging

On Wed, Mar 02, 2016 at 08:06:46PM +0100, Arnd Bergmann wrote: > The icn, act2000 and pcbit drivers are all for very old hardware, > and it is highly unlikely that anyone is actually still using them > on modern kernels, if at all. > > All three drivers apparently are for hardware that predates

Re: [PATCH] Staging: i4l: Correct coding style errors

On Thu, Dec 22, 2016 at 11:32:16PM +0100, Javier Rodriguez wrote: > Some lines with more than 80 characters has been corrected. > > Also, some printk() functions has been changed with their proper > print functions suggested by checkpatch.pl script as well as some > open braces has been aligned

[PATCH] staging: comedi: ni_at_ao: using the BIT(x) macro

Fix the checkpatch.pl issue: CHECK: Prefer using the BIT macro replacing bit shifting on 1 with the BIT(x) macro. Signed-off-by: Saber Rezvani Reviewed-by: Ian Abbott --- drivers/staging/comedi/drivers/ni_at_ao.c | 62 +++ 1

[PATCH] staging: comedi: ni_670x: using the BIT(x) macro

Fix the checkpatch.pl issue: CHECK: Prefer using the BIT macro replacing bit shifting on 1 with the BIT(x) macro. Signed-off-by: Saber Rezvani Reviewed-by: Ian Abbott --- drivers/staging/comedi/drivers/ni_670x.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 2/3] staging: comedi: cb_pcidas64: use preferred kernel type u16

Fix the checkpatch.pl issue: CHECK: Prefer kernel type 'u16' over 'uint16_t' Signed-off-by: Saber Rezvani Reviewed-by: Ian Abbott --- drivers/staging/comedi/drivers/cb_pcidas64.c | 58 ++-- 1 file changed, 29 insertions(+), 29

[PATCH 3/3] staging: comedi: cb_pcidas64: use preferred kernel type u32

Fix the checkpatch.pl issue: CHECK: Prefer kernel type 'u32' over 'uint32_t' Signed-off-by: Saber Rezvani Reviewed-by: Ian Abbott --- drivers/staging/comedi/drivers/cb_pcidas64.c | 38 ++-- 1 file changed, 19 insertions(+), 19

[PATCH 1/3] staging: comedi: cb_pcidas64: use preferred kernel type u8

Fix the checkpatch.pl issue: CHECK: Prefer kernel type 'u8' over 'uint8_t' Signed-off-by: Saber Rezvani Reviewed-by: Ian Abbott --- drivers/staging/comedi/drivers/cb_pcidas64.c | 46 ++-- 1 file changed, 23 insertions(+), 23

[PATCH] staging: most: change dma_buf variable to __le16

dma_buf is being cast to __le16 *, but it was defined as u16 *. sparse reported this error as: drivers/staging/most/hdm-usb/hdm_usb.c:158:16: warning: cast to restricted __le16 This patch changes dma_buf from u16 to __le16. Signed-off-by: Ramiro Oliveira ---

Re: [PATCH 14/14] staging: greybus: core: Fix NULL comparison to preferred style.

On Tue, Jan 03, 2017 at 03:33:16PM +0100, chatzi.eman...@gmail.com wrote: > From: Emmanuil Chatzipetru > > Fix coding style issue caught by checkpatch.pl related to the following > warning: > - CHECK: Comparison to NULL could be written "!id" Current code is

Re: [PATCH 10/14] staging: greybus: connection: Remove multiple blank lines

On Tue, Jan 03, 2017 at 03:33:12PM +0100, chatzi.eman...@gmail.com wrote: > From: Emmanuil Chatzipetru > > Fix coding style issue caught by checkpatch.pl related to the following > warning: > - CHECK: Please don't use multiple blank lines Again not a warning, and

Re: [PATCH 08/14] staging: greybus: camera: Fix NULL comparison to preferred style.

On Tue, Jan 03, 2017 at 03:33:10PM +0100, chatzi.eman...@gmail.com wrote: > From: Emmanuil Chatzipetru > > Fix coding style issue caught by checkpatch.pl related to the following > warning: > - CHECK: Comparison to NULL could be written "!token" Again, not a

Re: [PATCH 06/14] staging: greybus: bootrom: Fix line over 80 characters warning.

On Tue, Jan 03, 2017 at 03:33:08PM +0100, chatzi.eman...@gmail.com wrote: > From: Emmanuil Chatzipetru > > Fix coding style issue caught by checkpatch.pl related to the following > warning: > - CHECK: WARNING: line over 80 characters > > Signed-off-by: Emmanuil

Re: [PATCH 03/14] staging: greybus: arche-platform: Fix typo in the comments.

On Tue, Jan 03, 2017 at 03:33:05PM +0100, chatzi.eman...@gmail.com wrote: > From: Emmanuil Chatzipetru > > This warning is caught by checkpatch.pl: > - CHECK: 'begining' may be misspelled - perhaps 'beginning'? > > Signed-off-by: Emmanuil Chatzipetru

Re: [PATCH 02/14] staging: greybus: arche-apb-ctrl: Fix open parenthesis alignment.

On Tue, Jan 03, 2017 at 03:33:04PM +0100, chatzi.eman...@gmail.com wrote: > From: Emmanuil Chatzipetru > > Fix coding style issue caught by checkpatch.pl related to the following > warning: > - CHECK: Alignment should match open parenthesis This is not even a

Re: [PATCH 01/14] staging: greybus: arche-apb-ctrl: Remove multiple blank lines.

On Tue, Jan 03, 2017 at 03:33:03PM +0100, chatzi.eman...@gmail.com wrote: > From: Emmanuil Chatzipetru > > Fix coding style issue caught by checkpatch.pl related to the following > warning: > - CHECK: Please don't use multiple blank lines > > Signed-off-by:

[PATCH 14/14] staging: greybus: core: Fix NULL comparison to preferred style.

From: Emmanuil Chatzipetru Fix coding style issue caught by checkpatch.pl related to the following warning: - CHECK: Comparison to NULL could be written "!id" Signed-off-by: Emmanuil Chatzipetru --- drivers/staging/greybus/core.c | 2

[PATCH 12/14] staging: greybus: control: fix open parenthesis alingment

From: Emmanuil Chatzipetru Fix coding style issue caught by checkpatch.pl related to the following warning: - CHECK: Alignment should match open parenthesis Signed-off-by: Emmanuil Chatzipetru --- drivers/staging/greybus/control.c |

[PATCH 13/14] staging: greybus: core: Fix open parenthesis alingment

From: Emmanuil Chatzipetru Fix coding style issue caught by checkpatch.pl related to the following warning: - CHECK: Alignment should match open parenthesis Signed-off-by: Emmanuil Chatzipetru --- drivers/staging/greybus/core.c | 4

[PATCH 04/14] staging: greybus: arche-platform: Fix open parenthesis alignment.

From: Emmanuil Chatzipetru Fix coding style issue caught by checkpatch.pl related to the following warning: - CHECK: Alignment should match open parenthesis Signed-off-by: Emmanuil Chatzipetru ---

[PATCH 09/14] staging: greybus: connection: fix open parenthesis alignment

From: Emmanuil Chatzipetru Fix coding style issue caught by checkpatch.pl related to the following warning: - CHECK: Alignment should match open parenthesis Signed-off-by: Emmanuil Chatzipetru --- drivers/staging/greybus/connection.c

[PATCH 07/14] staging: greybus: camera: Fix open parenthesis alingment.

From: Emmanuil Chatzipetru Fix coding style issue caught by checkpatch.pl related to the following warning: - CHECK: Alignment should match open parenthesis Signed-off-by: Emmanuil Chatzipetru --- drivers/staging/greybus/camera.c |

[PATCH 11/14] staging: greybus: control: Remove multiple blank lines

From: Emmanuil Chatzipetru Fix coding style issue caught by checkpatch.pl related to the following warning: - CHECK: Please don't use multiple blank lines Signed-off-by: Emmanuil Chatzipetru --- drivers/staging/greybus/control.c | 1

[PATCH 10/14] staging: greybus: connection: Remove multiple blank lines

From: Emmanuil Chatzipetru Fix coding style issue caught by checkpatch.pl related to the following warning: - CHECK: Please don't use multiple blank lines Signed-off-by: Emmanuil Chatzipetru --- drivers/staging/greybus/connection.c |

[PATCH 05/14] staging: greybus: bootrom: Fix open parenthesis alignment.

From: Emmanuil Chatzipetru Fix coding style issue caught by checkpatch.pl related to the following warning: - CHECK: Alignment should match open parenthesis Signed-off-by: Emmanuil Chatzipetru --- drivers/staging/greybus/bootrom.c |

[PATCH 08/14] staging: greybus: camera: Fix NULL comparison to preferred style.

From: Emmanuil Chatzipetru Fix coding style issue caught by checkpatch.pl related to the following warning: - CHECK: Comparison to NULL could be written "!token" Signed-off-by: Emmanuil Chatzipetru ---

  1   2   >