Re: [PATCH] staging: sm750fb: format description of parameters the to kernel doc format

2019-10-16 Thread Randy Dunlap
On 10/16/19 6:29 PM, gbittencourt wrote: > Hi Randy, > > On 10/16/19 10:25 PM, Randy Dunlap wrote: >> Hi, >> >> On 10/16/19 6:18 PM, Gabriela Bittencourt wrote: >>> Cluster comments that describes parameters of functions and create one >>> single comment before the function in kernel doc format.

Re: [PATCH] staging: sm750fb: format description of parameters the to kernel doc format

2019-10-16 Thread gbittencourt
Hi Randy, On 10/16/19 10:25 PM, Randy Dunlap wrote: Hi, On 10/16/19 6:18 PM, Gabriela Bittencourt wrote: Cluster comments that describes parameters of functions and create one single comment before the function in kernel doc format. Good plan. How did you test this patch? I haven't test

Re: [PATCH] staging: sm750fb: format description of parameters the to kernel doc format

2019-10-16 Thread Randy Dunlap
Hi, On 10/16/19 6:18 PM, Gabriela Bittencourt wrote: > Cluster comments that describes parameters of functions and create one > single comment before the function in kernel doc format. Good plan. How did you test this patch? > Signed-off-by: Gabriela Bittencourt > --- >

[PATCH] staging: sm750fb: format description of parameters the to kernel doc format

2019-10-16 Thread Gabriela Bittencourt
Cluster comments that describes parameters of functions and create one single comment before the function in kernel doc format. Signed-off-by: Gabriela Bittencourt --- drivers/staging/sm750fb/sm750_accel.c | 65 +++ 1 file changed, 37 insertions(+), 28 deletions(-) diff

[driver-core:device_h_splitup 11/11] include/linux/device_printk.h:106:2: warning: this statement may fall through

2019-10-16 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git device_h_splitup head: 965681d8272ce30aa68375c25c4c797731e18dd3 commit: 965681d8272ce30aa68375c25c4c797731e18dd3 [11/11] device.h: move dev_printk()-like functions to device_printk.h config:

Re: [PATCH] staging: exfat: add exfat filesystem code to staging

2019-10-16 Thread Valdis Klētnieks
On Wed, 16 Oct 2019 16:33:17 -0400, Sasha Levin said: > It looks like the reason this wasn't made public along with the exFAT > spec is that TexFAT is pretty much dead - it's old, there are no users > we are aware of, and digging it out of it's grave to make it public is > actually quite the

Re: [PATCH -next] staging: fieldbus: arcx-anybus:use devm_platform_ioremap_resource() to simplify code

2019-10-16 Thread Sven Van Asbroeck
On Wed, Oct 16, 2019 at 4:50 AM YueHaibing wrote: > > Use devm_platform_ioremap_resource() to simplify the code a bit. > This is detected by coccinelle. > > Signed-off-by: YueHaibing > --- > drivers/staging/fieldbus/anybuss/arcx-anybus.c | 8 ++-- > 1 file changed, 2 insertions(+), 6

Re: [PATCH] staging: exfat: add exfat filesystem code to staging

2019-10-16 Thread Sasha Levin
On Wed, Oct 16, 2019 at 06:03:49PM +0200, Pali Rohár wrote: On Wednesday 16 October 2019 10:31:13 Sasha Levin wrote: On Wed, Oct 16, 2019 at 04:03:53PM +0200, Pali Rohár wrote: > On Friday 30 August 2019 09:56:47 Pali Rohár wrote: > > On Thursday 29 August 2019 19:35:06 Sasha Levin wrote: > > >

Re: [Outreachy kernel] [PATCH] staging: vc04_services: fix line over 80 characters checks warning

2019-10-16 Thread Jules Irenge
On Wed, 16 Oct 2019, Julia Lawall wrote: > > #ifndef VCHI_BULK_GRANULARITY > > # if __VCCOREVER__ >= 0x0400 > > -# define VCHI_BULK_GRANULARITY 32 // Allows for the need to do cache > > cleans > > +# define VCHI_BULK_GRANULARITY 32 // Allows for the need of cache cleans > > #

Re: [PATCH] staging: exfat: add exfat filesystem code to staging

2019-10-16 Thread Greg Kroah-Hartman
On Wed, Oct 16, 2019 at 06:32:31PM +0200, Pali Rohár wrote: > On Wednesday 16 October 2019 09:22:11 Greg Kroah-Hartman wrote: > > On Wed, Oct 16, 2019 at 06:03:49PM +0200, Pali Rohár wrote: > > > > Can I assume you will be implementing TexFAT support once the spec is > > > > available? > > > > >

Re: [PATCH] staging: exfat: add exfat filesystem code to staging

2019-10-16 Thread Pali Rohár
On Wednesday 16 October 2019 09:22:11 Greg Kroah-Hartman wrote: > On Wed, Oct 16, 2019 at 06:03:49PM +0200, Pali Rohár wrote: > > > Can I assume you will be implementing TexFAT support once the spec is > > > available? > > > > I cannot promise that I would implement something which I do not know

Re: [PATCH] staging: exfat: add exfat filesystem code to staging

2019-10-16 Thread Greg Kroah-Hartman
On Wed, Oct 16, 2019 at 06:03:49PM +0200, Pali Rohár wrote: > > Can I assume you will be implementing TexFAT support once the spec is > > available? > > I cannot promise that I would implement something which I do not know > how is working... It depends on how complicated TexFAT is and also how >

Re: [PATCH] staging: exfat: add exfat filesystem code to staging

2019-10-16 Thread Sasha Levin
On Wed, Oct 16, 2019 at 06:03:49PM +0200, Pali Rohár wrote: On Wednesday 16 October 2019 10:31:13 Sasha Levin wrote: On Wed, Oct 16, 2019 at 04:03:53PM +0200, Pali Rohár wrote: > On Friday 30 August 2019 09:56:47 Pali Rohár wrote: > > On Thursday 29 August 2019 19:35:06 Sasha Levin wrote: > > >

Re: [PATCH] staging: exfat: add exfat filesystem code to staging

2019-10-16 Thread Valdis Klētnieks
On Wed, 16 Oct 2019 10:31:13 -0400, Sasha Levin said: > On Wed, Oct 16, 2019 at 04:03:53PM +0200, Pali Roh�r wrote: > >Now one month passed, so do you have some information when missing parts > >of documentation like TexFAT would be released to public? > > Sure, I'll see if I can get an approval

Re: [PATCH] staging: exfat: add exfat filesystem code to staging

2019-10-16 Thread Pali Rohár
On Wednesday 16 October 2019 10:31:13 Sasha Levin wrote: > On Wed, Oct 16, 2019 at 04:03:53PM +0200, Pali Rohár wrote: > > On Friday 30 August 2019 09:56:47 Pali Rohár wrote: > > > On Thursday 29 August 2019 19:35:06 Sasha Levin wrote: > > > > With regards to missing specs/docs/whatever - our main

Re: [PATCH 1/2] binder: Don't modify VMA bounds in ->mmap handler

2019-10-16 Thread Christian Brauner
On Wed Oct 16, 2019 at 5:01 PM Jann Horn wrote: > binder_mmap() tries to prevent the creation of overly big binder mappings > by silently truncating the size of the VMA to 4MiB. However, this violates > the API contract of mmap(). If userspace attempts to create a large binder > VMA, and later

Re: [PATCH 2/2] binder: Use common definition of SZ_1K

2019-10-16 Thread Christian Brauner
On Wed Oct 16, 2019 at 5:01 PM Jann Horn wrote: > SZ_1K has been defined in include/linux/sizes.h since v3.6. Get rid of the > duplicate definition. > > Signed-off-by: Jann Horn Acked-by: Christian Brauner ___ devel mailing list

Re: [PATCH] staging: iio: ad9834: add a check for devm_clk_get

2019-10-16 Thread Dan Carpenter
On Wed, Oct 16, 2019 at 10:25:40PM +0800, Chuhong Yuan wrote: > ad9834_probe misses a check for devm_clk_get and may cause problems. > Add a check like what ad9832 does to fix it. > > Signed-off-by: Chuhong Yuan Looks good. Reviewed-by: Dan Carpenter regards, dan carpenter

Re: [PATCH] staging:rtl8723bs: removed unwanted if..else condition

2019-10-16 Thread Dan Carpenter
On Wed, Oct 16, 2019 at 07:37:53PM +0530, Aliasgar Surti wrote: > --- a/drivers/staging/rtl8723bs/core/rtw_cmd.c > +++ b/drivers/staging/rtl8723bs/core/rtw_cmd.c > @@ -507,19 +507,9 @@ int rtw_cmd_thread(void *context) > > cmd_process_time = jiffies_to_msecs(jiffies -

Re: [PATCH 2/4] staging: KPC2000: kpc2000_spi.c: Fix style issues (alignment)

2019-10-16 Thread Dan Carpenter
On Wed, Oct 16, 2019 at 12:49:25AM -0700, Chandra Annamaneni wrote: > Resolved: "CHECK: Alignment should match open parenthesis" from checkpatch > I think you accidentally copied the wrong commit message. This one and the next are the same. This description doesn't match the patch. regards,

Re: [PATCH] staging: exfat: add exfat filesystem code to staging

2019-10-16 Thread Sasha Levin
On Wed, Oct 16, 2019 at 04:03:53PM +0200, Pali Rohár wrote: On Friday 30 August 2019 09:56:47 Pali Rohár wrote: On Thursday 29 August 2019 19:35:06 Sasha Levin wrote: > With regards to missing specs/docs/whatever - our main concern with this > release was that we want full interoperability,

[PATCH] staging: iio: ad9834: add a check for devm_clk_get

2019-10-16 Thread Chuhong Yuan
ad9834_probe misses a check for devm_clk_get and may cause problems. Add a check like what ad9832 does to fix it. Signed-off-by: Chuhong Yuan --- drivers/staging/iio/frequency/ad9834.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/staging/iio/frequency/ad9834.c

[PATCH] staging:rtl8723bs: removed unwanted if..else condition

2019-10-16 Thread Aliasgar Surti
From: Aliasgar Surti There is use of if..elseif..else condition which has same logic in all three blocks. Removed if..else block and placed log message instead that. Signed-off-by: Aliasgar Surti --- drivers/staging/rtl8723bs/core/rtw_cmd.c | 16 +++- 1 file changed, 3

Re: [PATCH] staging: exfat: add exfat filesystem code to staging

2019-10-16 Thread Pali Rohár
On Friday 30 August 2019 09:56:47 Pali Rohár wrote: > On Thursday 29 August 2019 19:35:06 Sasha Levin wrote: > > With regards to missing specs/docs/whatever - our main concern with this > > release was that we want full interoperability, which is why the spec > > was made public as-is without

Re: [PATCH 5/7] PCI/PM: Make power management op coding style consistent

2019-10-16 Thread Dan Carpenter
On Mon, Oct 14, 2019 at 06:00:14PM -0500, Bjorn Helgaas wrote: > From: Bjorn Helgaas > > Some of the power management ops use this style: > > struct device_driver *drv = dev->driver; > if (drv && drv->pm && drv->pm->prepare(dev)) > drv->pm->prepare(dev); > > while others use this: > >

Re: [PATCH v2] media: imx7-mipi-csis: Add a check for devm_regulator_get

2019-10-16 Thread Rui Miguel Silva
Hi Marco, On Wed 16 Oct 2019 at 10:06, Marco Felsch wrote: > Hi Chuhong, > > On 19-10-15 21:59, Chuhong Yuan wrote: >> devm_regulator_get may return an error but mipi_csis_phy_init misses >> a check for it. >> This may lead to problems when regulator_set_voltage uses the unchecked >> pointer. >>

Re: [PATCH] staging: meson: add space to fix check warning

2019-10-16 Thread Hans Verkuil
On 10/16/19 12:34 AM, Jules Irenge wrote: > Fix "alignment should mactch open parenthesis" check. > Issue detected by checkpatch tool > > Signed-off-by: Jules Irenge > --- > drivers/staging/media/meson/vdec/codec_mpeg12.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [PATCH -next] staging: media: omap4iss: use devm_platform_ioremap_resource() to simplify code

2019-10-16 Thread Laurent Pinchart
Hello YueHaibing, Thank you for the patch. The same fix has already been submitted a week ago, and I have sent a pull request today that includes it. I'm afraid I thus can't take this patch. The good news is that the change was good :-) On Wed, Oct 16, 2019 at 04:51:36PM +0800, YueHaibing

Re: [PATCH] staging: media: make use of devm_platform_ioremap_resource

2019-10-16 Thread Laurent Pinchart
Hello Hariprasad, Thank you for the patch. As the patch only touches the omap4iss driver, you could have made the subject line a bit more specific, for instance "staging: media: omap4iss: Use devm_platform_ioremap_resource". No big deal though. On Tue, Oct 08, 2019 at 12:25:51PM +0530,

Re: [PATCH v2] media: imx7-mipi-csis: Add a check for devm_regulator_get

2019-10-16 Thread Marco Felsch
Hi Chuhong, On 19-10-15 21:59, Chuhong Yuan wrote: > devm_regulator_get may return an error but mipi_csis_phy_init misses > a check for it. > This may lead to problems when regulator_set_voltage uses the unchecked > pointer. > This patch adds a check for devm_regulator_get to avoid potential

[PATCH -next] staging: ralink-gdma: use devm_platform_ioremap_resource() to simplify code

2019-10-16 Thread YueHaibing
Use devm_platform_ioremap_resource() to simplify the code a bit. This is detected by coccinelle. Signed-off-by: YueHaibing --- drivers/staging/ralink-gdma/ralink-gdma.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/staging/ralink-gdma/ralink-gdma.c

[PATCH -next] staging: netlogic: use devm_platform_ioremap_resource() to simplify code

2019-10-16 Thread YueHaibing
Use devm_platform_ioremap_resource() to simplify the code a bit. This is detected by coccinelle. Signed-off-by: YueHaibing --- drivers/staging/netlogic/xlr_net.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/staging/netlogic/xlr_net.c

[PATCH -next] staging: mt7621-dma: use devm_platform_ioremap_resource() to simplify code

2019-10-16 Thread YueHaibing
Use devm_platform_ioremap_resource() to simplify the code a bit. This is detected by coccinelle. Signed-off-by: YueHaibing --- drivers/staging/mt7621-dma/mtk-hsdma.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/staging/mt7621-dma/mtk-hsdma.c

[PATCH -next] staging: media: cedrus: use devm_platform_ioremap_resource() to simplify code

2019-10-16 Thread YueHaibing
Use devm_platform_ioremap_resource() to simplify the code a bit. This is detected by coccinelle. Signed-off-by: YueHaibing --- drivers/staging/media/sunxi/cedrus/cedrus_hw.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/staging/media/sunxi/cedrus/cedrus_hw.c

[PATCH -next] staging: media: omap4iss: use devm_platform_ioremap_resource() to simplify code

2019-10-16 Thread YueHaibing
Use devm_platform_ioremap_resource() to simplify the code a bit. This is detected by coccinelle. Signed-off-by: YueHaibing --- drivers/staging/media/omap4iss/iss.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/drivers/staging/media/omap4iss/iss.c

[PATCH -next] staging: fieldbus: arcx-anybus:use devm_platform_ioremap_resource() to simplify code

2019-10-16 Thread YueHaibing
Use devm_platform_ioremap_resource() to simplify the code a bit. This is detected by coccinelle. Signed-off-by: YueHaibing --- drivers/staging/fieldbus/anybuss/arcx-anybus.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git

[PATCH 2/4] staging: KPC2000: kpc2000_spi.c: Fix style issues (alignment)

2019-10-16 Thread Chandra Annamaneni
Resolved: "CHECK: Alignment should match open parenthesis" from checkpatch Signed-off-by: Chandra Annamaneni --- Previous versions of these patches were not split into different patches, did not have different patch numbers and did not have the keyword staging.

[PATCH 3/4] staging: KPC2000: kpc2000_spi.c: Fix style issues (alignment)

2019-10-16 Thread Chandra Annamaneni
Resolved: "CHECK: Alignment should match open parenthesis" from checkpatch Signed-off-by: Chandra Annamaneni --- Previous versions of these patches were not split into different patches, did not have different patch numbers and did not have the keyword staging.

[PATCH 4/4] staging: KPC2000: kpc2000_spi.c: Fix style issues (Unnecessary parenthesis)

2019-10-16 Thread Chandra Annamaneni
Resolved: CHECK: Unnecessary parentheses around table[i] Signed-off-by: Chandra Annamaneni --- Previous versions of these patches were not split into different patches, did not have different patch numbers and did not have the keyword staging. drivers/staging/kpc2000/kpc2000_spi.c | 2 +- 1

[PATCH 1/4] staging: KPC2000: kpc2000_spi.c: Fix style issues (missing blank line)

2019-10-16 Thread Chandra Annamaneni
Resolved: "CHECK: Please use a blank line after.." from checkpatch.pl Signed-off-by: Chandra Annamaneni --- Previous versions of these patches were not split into different patches, did not have different patch numbers and did not have the keyword staging. drivers/staging/kpc2000/kpc2000_spi.c

Re: [PATCH 1/5] KPC2000: kpc2000_spi.c: Fix style issues (line length)

2019-10-16 Thread
On Fri, Oct 11, 2019 at 08:32:19AM +0200, Greg KH wrote: > On Thu, Oct 10, 2019 at 10:51:51PM -0700, Chandra Annamaneni wrote: > > Resoved: "WARNING: line over 80 characters" from checkpatch.pl > > Please put "staging:" in your subject line, makes it easier to sort and > handle. It should look

[PATCH] staging: rtl8188eu: make efuse_power_switch() function static

2019-10-16 Thread Alexandru Ardelean
The `rtl8188eu` driver is built as a kmod in order to avoid symbol conflicts (at link-time) with other Realtek drivers. Internally, we use this driver as builtin [vs kmod], and we've identified the `efuse_power_switch()` symbol to be conflicting at link-time with the one from the `rtlwifi`