Re: [PATCH 10/49] staging: hikey9xx/gpu: add debug prints for this driver

2020-08-21 Thread Joe Perches
On Wed, 2020-08-19 at 13:45 +0200, Mauro Carvalho Chehab wrote: > From: Xiubin Zhang > > Add some debug prints on adv7535 and kirin_drm_drv. bikeshed: > diff --git a/drivers/staging/hikey9xx/gpu/hdmi/adv7535.c > b/drivers/staging/hikey9xx/gpu/hdmi/adv7535.c [] > @@ -785,19 +786,25 @@ adv7511_d

Re: [PATCH 25/49] staging: hikey9xx/gpu: do some code cleanups

2020-08-21 Thread John Stultz
On Thu, Aug 20, 2020 at 1:23 AM Mauro Carvalho Chehab wrote: > > (added c/c Rob Herring) > > Em Wed, 19 Aug 2020 18:53:06 -0700 > John Stultz escreveu: > > > On Wed, Aug 19, 2020 at 4:46 AM Mauro Carvalho Chehab > > wrote: > > > @@ -376,7 +355,7 @@ static int kirin_drm_platform_resume(struct >

[PATCH v3] binder: print warnings when detecting oneway spamming.

2020-08-21 Thread Martijn Coenen
The most common cause of the binder transaction buffer filling up is a client rapidly firing oneway transactions into a process, before it has a chance to handle them. Yet the root cause of this is often hard to debug, because either the system or the app will stop, and by that time binder debug in

Re: [PATCH v4 2/2] staging: android: Remove BUG from ion_system_heap.c

2020-08-21 Thread Randy Dunlap
On 8/21/20 8:28 AM, Tomer Samara wrote: > Remove BUG() from ion_sytem_heap.c > > this fix the following checkpatch issue: > Avoid crashing the kernel - try using WARN_ON & > recovery code ratherthan BUG() or BUG_ON(). > > Signed-off-by: Tomer Samara > --- > drivers/staging/android/ion/ion_syste

[PATCH AUTOSEL 4.9 19/26] cec-api: prevent leaking memory through hole in structure

2020-08-21 Thread Sasha Levin
From: Hans Verkuil [ Upstream commit 6c42227c3467549ddc65efe99c869021d2f4a570 ] Fix this smatch warning: drivers/media/cec/core/cec-api.c:156 cec_adap_g_log_addrs() warn: check that 'log_addrs' doesn't leak information (struct has a hole after 'features') Signed-off-by: Hans Verkuil Signed-o

[PATCH AUTOSEL 5.7 16/61] staging: rts5208: fix memleaks on error handling paths in probe

2020-08-21 Thread Sasha Levin
From: Evgeny Novikov [ Upstream commit 11507bf9a8832741db69efd32bf09a2ab26426bf ] rtsx_probe() allocates host, but does not free it on error handling paths. The patch adds missed scsi_host_put(). Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Evgeny Novikov Link

[PATCH AUTOSEL 5.8 16/62] staging: rts5208: fix memleaks on error handling paths in probe

2020-08-21 Thread Sasha Levin
From: Evgeny Novikov [ Upstream commit 11507bf9a8832741db69efd32bf09a2ab26426bf ] rtsx_probe() allocates host, but does not free it on error handling paths. The patch adds missed scsi_host_put(). Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Evgeny Novikov Link

Re: [PATCH 00/49] DRM driver for Hikey 970

2020-08-21 Thread Joe Perches
On Wed, 2020-08-19 at 22:48 +0200, Sam Ravnborg wrote: > And sometimes checkpatch is just wrong. I'm interested in examples for when checkpatch is "just wrong". ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org

Re: [PATCH 00/49] DRM driver for Hikey 970

2020-08-21 Thread Sam Ravnborg
Hi Mauro. On Fri, Aug 21, 2020 at 04:41:58PM +0200, Mauro Carvalho Chehab wrote: > Another quick question: > > Em Wed, 19 Aug 2020 19:35:58 +0200 > Sam Ravnborg escreveu: > > > > +#define DSS_REDUCE(x)((x) > 0 ? ((x) - 1) : (x)) > > Use generic macros for this? > > Do you know a generic

Re: [PATCH 00/49] DRM driver for Hikey 970

2020-08-21 Thread Sam Ravnborg
Hi Mauro. Thanks for the detailed feedabck. Two comments in the following. Sam > > > > + ctx->dss_pri_clk = devm_clk_get(dev, "clk_edc0"); > > > + if (!ctx->dss_pri_clk) { > > > + DRM_ERROR("failed to parse dss_pri_clk\n"); > > > + return -ENODEV; > > > + } > ... > > > I had ex

[PATCH v4 2/2] staging: android: Remove BUG from ion_system_heap.c

2020-08-21 Thread Tomer Samara
Remove BUG() from ion_sytem_heap.c this fix the following checkpatch issue: Avoid crashing the kernel - try using WARN_ON & recovery code ratherthan BUG() or BUG_ON(). Signed-off-by: Tomer Samara --- drivers/staging/android/ion/ion_system_heap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletio

[PATCH v4 1/2] staging: android: Remove BUG_ON from ion_page_pool.c

2020-08-21 Thread Tomer Samara
BUG_ON() is removed at ion_page_pool.c Fixes the following issue: Avoid crashing the kernel - try using WARN_ON & recovery code ratherthan BUG() or BUG_ON(). Signed-off-by: Tomer Samara --- drivers/staging/android/ion/ion_page_pool.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-)

[PATCH v4 0/2] staging: android: Remove BUG/BUG_ON from ion

2020-08-21 Thread Tomer Samara
Remove BUG/BUG_ON from androind/ion -v4: some changes based on Dan Carpenter review: - Remove error check at ion_page_pool_remove (conditions are impossible) - Remove error check at opn_page_pool_alloc - restore WARN_ON at ion_page_pool_free - Remove unnece

Re: [PATCH 00/49] DRM driver for Hikey 970

2020-08-21 Thread Mauro Carvalho Chehab
Another quick question: Em Wed, 19 Aug 2020 19:35:58 +0200 Sam Ravnborg escreveu: > > +#define DSS_REDUCE(x) ((x) > 0 ? ((x) - 1) : (x)) > Use generic macros for this? Do you know a generic macro similar to this? Or do you mean adding it to include/kernel.h? There are the atomic sub one

Re: [PATCH 00/49] DRM driver for Hikey 970

2020-08-21 Thread Mauro Carvalho Chehab
Em Wed, 19 Aug 2020 19:35:58 +0200 Sam Ravnborg escreveu: > Also a few high level comments: Hi Sam, Finally finished addressing the things you pointed, except by a few ones: - bridge bindings; - use drm_foo() instead of DRM_foo() when possible. A few answers to some of your com

Re: [PATCH 00/49] DRM driver for Hikey 970

2020-08-21 Thread Mauro Carvalho Chehab
Hi Sam, Em Wed, 19 Aug 2020 19:35:58 +0200 Sam Ravnborg escreveu: > > + ret = drm_bridge_attach(encoder, bridge, NULL, 0); > The bridge should be attached with the falg that tell the bridge NOT to > create a connector. > > The display driver shall created the connector. > > Please see how

Re: [PATCH v3 2/2] staging: android: Remove BUG from ion_system_heap.c

2020-08-21 Thread Dan Carpenter
On Wed, Aug 19, 2020 at 10:39:34PM +0300, Tomer Samara wrote: > Remove BUG() at ion_sytem_heap.c and error handling to: > - free_buffer_page > - alloc_buffer_page > this fix the following checkpatch issue: > Avoid crashing the kernel - try using WARN_ON & > recovery code ratherthan BUG() or BUG_

Information

2020-08-21 Thread Lukman Jemba
My dear, I pray you receive this message in good health. My name is Lukman Jemba 78 Catholic Reverend father. I am presently at hospital where I am being diagnosed cancer ailment. I have contact you to inform you about $18,500,000.00 deposited in bank meant for orphanage foundation. Doctor

Re: [PATCH v3 1/2] staging: android: Remove BUG_ON from ion_page_pool.c

2020-08-21 Thread Dan Carpenter
On Wed, Aug 19, 2020 at 10:38:47PM +0300, Tomer Samara wrote: > BUG_ON() is removed at ion_page_pool.c and add error handleing to > ion_page_pool_shrink > > Fixes the following issue: > Avoid crashing the kernel - try using WARN_ON & recovery code ratherthan > BUG() or BUG_ON(). > > Signed-off-b

[PATCH] staging: rtl8192e: fix missing failure check on a call to dev_alloc_name

2020-08-21 Thread Colin King
From: Colin Ian King Currently the second call to dev_alloc_name is not checking if this failed. Add the check and perform necessary cleanup on an error. Addresses-Coverity: ("Unchecked return value") Fixes: 94a799425eee ("rtl8192e: Import new version of driver from realtek") Signed-off-by: Col

Re: [PATCH v4 3/3] media: atomisp: Only use trace_printk if allowed

2020-08-21 Thread Nicolas Boichat
On Fri, Aug 21, 2020 at 8:18 PM David Laight wrote: > > From: Nicolas Boichat > > Sent: 21 August 2020 13:07 > ... > > > You might also want a #define that can set temporarily > > > to enable traces in a specific file/module even though > > > CONFIG_TRACE=n. > > > > I don't understand how traces a

Re: [PATCH v4 3/3] media: atomisp: Only use trace_printk if allowed

2020-08-21 Thread Nicolas Boichat
On Fri, Aug 21, 2020 at 11:01 AM Steven Rostedt wrote: > > On Fri, 21 Aug 2020 10:39:02 +0800 > Nicolas Boichat wrote: > > > I'm not sure how that helps? I mean, the use case you have in mind is > > somebody reusing a distro/random config and not being able to use > > trace_printk, right? If that

RE: [PATCH v4 3/3] media: atomisp: Only use trace_printk if allowed

2020-08-21 Thread David Laight
From: Nicolas Boichat > Sent: 21 August 2020 13:07 ... > > You might also want a #define that can set temporarily > > to enable traces in a specific file/module even though > > CONFIG_TRACE=n. > > I don't understand how traces are supposed to work with CONFIG_TRACE=n? Probably because I meant som

Re: [PATCH v4 3/3] media: atomisp: Only use trace_printk if allowed

2020-08-21 Thread Nicolas Boichat
On Fri, Aug 21, 2020 at 7:32 PM David Laight wrote: > > From: Nicolas Boichat > > Sent: 21 August 2020 11:28 > > > > On Fri, Aug 21, 2020 at 4:48 PM David Laight > > wrote: > > > > > > From: Steven Rostedt > > > > Sent: 21 August 2020 01:36 > > > > On Fri, 21 Aug 2020 08:13:00 +0800 > > > > Nico

RE: [PATCH v4 3/3] media: atomisp: Only use trace_printk if allowed

2020-08-21 Thread David Laight
From: Nicolas Boichat > Sent: 21 August 2020 11:28 > > On Fri, Aug 21, 2020 at 4:48 PM David Laight wrote: > > > > From: Steven Rostedt > > > Sent: 21 August 2020 01:36 > > > On Fri, 21 Aug 2020 08:13:00 +0800 > > > Nicolas Boichat wrote: > > > > > > > On Thu, Aug 20, 2020 at 10:23 PM Steven Ros

Re: [PATCH v4 3/3] media: atomisp: Only use trace_printk if allowed

2020-08-21 Thread Joe Perches
On Thu, 2020-08-20 at 21:57 -0400, Steven Rostedt wrote: > On Fri, 21 Aug 2020 09:39:19 +0800 > Nicolas Boichat wrote: [] > > Some other approaches/ideas: > > 1. Filter all lkml messages that contain trace_printk. Already found > > 1 instance, and I can easily reply to those with a semi-canned an

Re: [PATCH v4 3/3] media: atomisp: Only use trace_printk if allowed

2020-08-21 Thread Nicolas Boichat
On Fri, Aug 21, 2020 at 4:48 PM David Laight wrote: > > From: Steven Rostedt > > Sent: 21 August 2020 01:36 > > On Fri, 21 Aug 2020 08:13:00 +0800 > > Nicolas Boichat wrote: > > > > > On Thu, Aug 20, 2020 at 10:23 PM Steven Rostedt > > > wrote: > > > > > > > > On Thu, 20 Aug 2020 17:14:12 +0800

RE: [PATCH v4 3/3] media: atomisp: Only use trace_printk if allowed

2020-08-21 Thread David Laight
From: Steven Rostedt > Sent: 21 August 2020 01:36 > On Fri, 21 Aug 2020 08:13:00 +0800 > Nicolas Boichat wrote: > > > On Thu, Aug 20, 2020 at 10:23 PM Steven Rostedt wrote: > > > > > > On Thu, 20 Aug 2020 17:14:12 +0800 > > > Nicolas Boichat wrote: > > > > > > > Technically, we could only initi

Re: [PATCH RESEND v10 07/11] device-mapping: Introduce DMA range map, supplanting dma_pfn_offset

2020-08-21 Thread Andy Shevchenko
On Thu, Aug 20, 2020 at 09:37:12AM -0400, Jim Quinlan wrote: > On Tue, Aug 18, 2020 at 4:14 AM Andy Shevchenko > wrote: > > On Mon, Aug 17, 2020 at 05:53:09PM -0400, Jim Quinlan wrote: ... > > > +static inline u64 dma_offset_from_dma_addr(struct device *dev, > > > dma_addr_t dma_addr) > > > +{

Re: [PATCH] staging: qlge: fix build breakage with dumping enabled

2020-08-21 Thread Benjamin Poirier
On 2020-08-21 15:03 +0800, Coiby Xu wrote: > This fixes commit 0107635e15ac > ("staging: qlge: replace pr_err with netdev_err") which introduced an > build breakage with dumping enabled, i.e., > > $ QL_ALL_DUMP=1 QL_OB_DUMP=1 QL_CB_DUMP=1 QL_REG_DUMP=1 \ > QL_IB_DUMP=1 QL_DEV_DUMP=1 make

[PATCH] staging: qlge: fix build breakage with dumping enabled

2020-08-21 Thread Coiby Xu
This fixes commit 0107635e15ac ("staging: qlge: replace pr_err with netdev_err") which introduced an build breakage with dumping enabled, i.e., $ QL_ALL_DUMP=1 QL_OB_DUMP=1 QL_CB_DUMP=1 QL_REG_DUMP=1 \ QL_IB_DUMP=1 QL_DEV_DUMP=1 make M=drivers/staging/qlge Fixes: 0107635e15ac ("taging: