Re: [PATCH v2 01/16] hyper-v: trace vmbus_on_msg_dpc()

On Mon, 2 Oct 2017 08:18:50 +0800 kbuild test robot wrote: > Hi Vitaly, > > [auto build test WARNING on linus/master] > [also build test WARNING on v4.14-rc3 next-20170929] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] >

Re: [PATCH v5 2/2] staging: ion: create one device entry per heap

On 10/03/2017 04:08 PM, Sandeep Patil wrote: > On Tue, Oct 03, 2017 at 02:42:32PM -0700, Laura Abbott wrote: >> On 10/03/2017 09:48 AM, Mark Brown wrote: >>> On Mon, Oct 02, 2017 at 11:07:48AM -0700, Laura Abbott wrote: >>> Thinking about this a bit more, I'm not 100% sure if this will

[PATCH v4] staging: atomisp: add a driver for ov5648 camera sensor

The ov5648 5-megapixel camera sensor from OmniVision supports up to 2592x1944 resolution and MIPI CSI-2 interface. Output format is raw sRGB/Bayer with 10 bits per colour (SGRBG10_1X10). This patch is a port of ov5648 driver after applying following 01org/ProductionKernelQuilts patches: -

[PATCH v2 1/2] staging: Introduce NVIDIA Tegra20 video decoder driver

Video decoder, found on NVIDIA Tegra20 SoC, supports a standard set of video formats like H.264 / MPEG-4 / WMV / VC1. Currently driver supports decoding of CAVLC H.264 only. Signed-off-by: Dmitry Osipenko --- .../bindings/arm/tegra/nvidia,tegra20-vde.txt | 43 +

[PATCH v2 2/2] ARM: dts: tegra20: Add video decoder node

Add a device node for the video decoder engine found on Tegra20. Signed-off-by: Dmitry Osipenko --- arch/arm/boot/dts/tegra20.dtsi | 17 + 1 file changed, 17 insertions(+) diff --git a/arch/arm/boot/dts/tegra20.dtsi b/arch/arm/boot/dts/tegra20.dtsi index

[PATCH v2 0/2] NVIDIA Tegra20 video decoder driver

This driver provides accelerated video decoding to NVIDIA Tegra20 SoC's, it is a result of reverse-engineering efforts. Driver has been tested on Toshiba AC100 and Acer A500, it should work on any Tegra20 device. In userspace this driver is utilized by libvdpau-tegra [0] that implements VDPAU

Re: [PATCH v5 2/2] staging: ion: create one device entry per heap

On 10/03/2017 09:48 AM, Mark Brown wrote: > On Mon, Oct 02, 2017 at 11:07:48AM -0700, Laura Abbott wrote: > >> Thinking about this a bit more, I'm not 100% sure if this >> will allow the security rules we want. Heap ids are assigned >> dynamically and therefore so will the /dev/ionX designation.

[PATCH] Staging: rtl8188eu: core: Use list_for_each_entry_safe

Use list_for_each_entry_safe when the list elements may get deleted during traversal. Done using the following semantic patch by coccinelle. @r@ struct list_head* l; expression e; identifier m, list_del_init, f; type T1; T1* pos; iterator name list_for_each_entry_safe; @@ f(...){ +T1* tmp; ...

[PATCH] media: staging/imx: do not return error in link_notify for unknown sources

imx_media_link_notify() should not return error if the source subdevice is not recognized by imx-media, that isn't an error. If the subdev has controls they will be inherited starting from a known subdev. Signed-off-by: Steve Longerbeam ---

Re: [PATCH RFC] media: staging/imx: fix complete handler

On 10/03/2017 02:06 AM, Russell King - ARM Linux wrote: On Mon, Oct 02, 2017 at 05:59:30PM -0700, Steve Longerbeam wrote: On 10/01/2017 04:36 PM, Russell King - ARM Linux wrote: On Sun, Oct 01, 2017 at 01:16:53PM -0700, Steve Longerbeam wrote: Right, imx_media_add_vdev_to_pa() has followed

Re: [PATCH v2 16/16] hyper-v: trace vmbus_send_tl_connect_request()

I added an additional set of trace points for when channel gets notified or signals host. diff -urNp linux-msft/drivers/hv/channel.c msft-4.14-rc3/drivers/hv/channel.c --- linux-msft/drivers/hv/channel.c 2017-10-03 10:06:54.893209237 -0700 +++ msft-4.14-rc3/drivers/hv/channel.c 2017-10-03

Re: [PATCH 02/16] hyper-v: trace vmbus_on_message()

On Thu, 21 Sep 2017 10:17:18 +0200 Vitaly Kuznetsov wrote: > Steven Rostedt writes: > > > On Wed, 20 Sep 2017 19:21:53 +0200 > > Vitaly Kuznetsov wrote: > > > >> diff --git a/drivers/hv/hv_trace.h b/drivers/hv/hv_trace.h > >>

Re: [PATCH v5 2/2] staging: ion: create one device entry per heap

On Mon, Oct 02, 2017 at 11:07:48AM -0700, Laura Abbott wrote: > Thinking about this a bit more, I'm not 100% sure if this > will allow the security rules we want. Heap ids are assigned > dynamically and therefore so will the /dev/ionX designation. > From my understanding, security rules like

Re: [PATCH] staging: fbtft: diferenciate between buffer and data types to fix sparse warning

On Wed, Sep 27, 2017 at 06:16:18PM +0100, Alfonso Lima Astor wrote: > sparse was complaning about an incorrect type cast: > drivers/staging/fbtft/fbtft-bus.c:60:1: warning: incorrect type in assignment > (different base types) > drivers/staging/fbtft/fbtft-bus.c:60:1:expected unsigned short

Re: [PATCH 0/6] Replace container_of with list_entry

On Tue, Oct 3, 2017 at 9:44 PM, Greg KH wrote: > On Sat, Sep 30, 2017 at 12:49:00PM +0530, Srishti Sharma wrote: >> Replaces instances of container_of with list_entry to >> access current list element. >> >> Srishti Sharma (6): >> Staging: rtl8188eu: core: Use

Re: [PATCH v2] staging: ccree: Convert to platform_{get,set}_drvdata()

On Thu, Sep 21, 2017 at 05:47:42PM +0530, suni...@techveda.org wrote: > From: Suniel Mahesh > > Platform devices are expected to use wrapper functions, > platform_{get,set}_drvdata() with platform_device as argument, > for getting and setting the driver data.

Re: [PATCH 0/6] Replace container_of with list_entry

On Sat, Sep 30, 2017 at 12:49:00PM +0530, Srishti Sharma wrote: > Replaces instances of container_of with list_entry to > access current list element. > > Srishti Sharma (6): > Staging: rtl8188eu: core: Use list_entry instead of container_of > Staging: rtl8188eu: core: Use list_entry instead

Re: [PATCH 5/6] staging: fsl-dpaa2/ethsw: Add README

On Tue, Oct 03, 2017 at 10:07:41AM +, Razvan Stefanescu wrote: > > -Original Message- > > From: linux-arm-kernel [mailto:linux-arm-kernel-boun...@lists.infradead.org] > > On Behalf Of Andrew Lunn > > Sent: Tuesday, September 19, 2017 3:18 PM > > To: Razvan Stefanescu

[GIT PULL] Staging/IIO driver fixes for 4.14-rc4

The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e: Linux 4.14-rc1 (2017-09-16 15:47:51 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/ tags/staging-4.14-rc4 for you to fetch changes up to

[PATCH 4/4] staging: rtlwifi: pr_err() strings should end with newlines

pr_err() messages should end with a new-line to avoid other messages being concatenated. Signed-off-by: Arvind Yadav --- drivers/staging/rtlwifi/halmac/halmac_88xx/halmac_func_88xx.c | 6 +++--- drivers/staging/rtlwifi/rtl8822be/phy.c | 4 ++-- 2

[PATCH 3/4] staging: bcm2835-camera: pr_err() strings should end with newlines

pr_err() messages should end with a new-line to avoid other messages being concatenated. Signed-off-by: Arvind Yadav --- drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 0/4] staging: rtlwifi: pr_err() strings should end with newlines

pr_err() messages should end with a new-line to avoid other messages being concatenated. Arvind Yadav (4): [PATCH 1/4] staging: gs_fpgaboot: pr_err() strings should end with newlines [PATCH 2/4] staging: media: davinci_vpfe: pr_err() strings should end with newlines [PATCH 3/4] staging:

[PATCH 2/4] staging: media: davinci_vpfe: pr_err() strings should end with newlines

pr_err() messages should end with a new-line to avoid other messages being concatenated. Signed-off-by: Arvind Yadav --- drivers/staging/media/davinci_vpfe/dm365_ipipe_hw.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 1/4] staging: gs_fpgaboot: pr_err() strings should end with newlines

pr_err() messages should end with a new-line to avoid other messages being concatenated. Signed-off-by: Arvind Yadav --- drivers/staging/gs_fpgaboot/gs_fpgaboot.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH v3] staging: atomisp: add a driver for ov5648 camera sensor

On Mon, 2017-10-02 at 21:30 +0200, Devid Antonio Filoni wrote: > The ov5648 5-megapixel camera sensor from OmniVision supports up to > 2592x1944 > resolution and MIPI CSI-2 interface. Output format is raw sRGB/Bayer > with > 10 bits per colour (SGRBG10_1X10). > > This patch is a port of ov5648

[PATCH v2 3/4] staging: ccree: move to generic device log infra

Move over from using macro wrappers around to printk to dev_err, dev_dbg and friends and clean up resulting fallout. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_aead.c| 226 ++ drivers/staging/ccree/ssi_buffer_mgr.c | 394

[PATCH v2 4/4] staging: ccree: simplify OOM handling

Simplify handling of memory allocation failures and remove redundant log messages Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_cipher.c | 11 -- drivers/staging/ccree/ssi_driver.c | 1 - drivers/staging/ccree/ssi_hash.c | 42

[PATCH v2 2/4] staging: ccree: simplify access to struct device

Introduce a function to retrieve struct device from private data structure in preparation to replacing custom logging macros with proper dev_dbg and friends which require struct device. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_aead.c| 11 ---

Re: [PATCH 2/4] staging: ccree: simplify access to struct device

On Mon, Oct 2, 2017 at 1:00 PM, Joe Perches wrote: > On Mon, 2017-10-02 at 10:03 +0100, Gilad Ben-Yossef wrote: >> Introduce a DEV macro to retrieve struct device from private >> data structure in preparation to replacing custom logging >> macros with proper dev_dbg and friends

[PATCH v2 1/4] staging: ccree: remove sysfs if of deleted code

The ccree cycle count mechanism was removed in commit 7f821f0c6ffa ("staging: ccree: remove cycle count debug support") but the sysfs interface lingered on. Remove it now. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_sysfs.c | 266

[PATCH v2 0/4] staging: ccree: logging related coding style fixes

The following patch set cleans up some code and builds upon this to replace ccree custom logging macros with the generic device dev_* facilities, handles the resulting fallout and further simplifies handling of memory and allocation OOM error handling code path exposed by checkpatch following the

RE: [PATCH 5/6] staging: fsl-dpaa2/ethsw: Add README

> -Original Message- > From: linux-arm-kernel [mailto:linux-arm-kernel-boun...@lists.infradead.org] > On Behalf Of Andrew Lunn > Sent: Tuesday, September 19, 2017 3:18 PM > To: Razvan Stefanescu > Cc: de...@driverdev.osuosl.org; Ruxandra Ioana Radulescu >

Re: [PATCH] Add new uio device for PCI with dynamic memory allocation

Looks good. A couple minor comments below. On Mon, Oct 02, 2017 at 03:02:09PM +, Stahl, Manuel wrote: > +static int open(struct uio_info *info, struct inode *inode) > +{ > + struct uio_pci_dmem_dev *priv = to_uio_pci_dmem_dev(info); > + struct uio_mem *uiomem; > + int ret = 0; >

Re: [PATCH RFC] media: staging/imx: fix complete handler

On Mon, Oct 02, 2017 at 05:59:30PM -0700, Steve Longerbeam wrote: > > > On 10/01/2017 04:36 PM, Russell King - ARM Linux wrote: > >On Sun, Oct 01, 2017 at 01:16:53PM -0700, Steve Longerbeam wrote: > >>Right, imx_media_add_vdev_to_pa() has followed a link to an > >>entity that imx is not aware

Re: [PATCH] binder: fix memory corruption in binder_transaction binder

Hi, On 12 September 2017 at 13:50, Martijn Coenen wrote: > Hi Amit, > > Can you try with the patch I sent to LKML recently, "[PATCH v2 10/13] > ANDROID: binder: call poll_wait() unconditionally."? This fixes a > problem in binder's poll() implementation that only causes issues >