[PATCH AUTOSEL 5.5 019/542] media: meson: add missing allocation failure check on new_buf

2020-02-14 Thread Sasha Levin
From: Colin Ian King [ Upstream commit 11e0e167d071a28288a7a0a211d48c571d19b56f ] Currently if the allocation of new_buf fails then a null pointer dereference occurs when assiging new_buf->vb. Avoid this by returning early on a memory allocation failure as there is not much more can be done at

[PATCH AUTOSEL 5.4 015/459] media: meson: add missing allocation failure check on new_buf

2020-02-14 Thread Sasha Levin
From: Colin Ian King [ Upstream commit 11e0e167d071a28288a7a0a211d48c571d19b56f ] Currently if the allocation of new_buf fails then a null pointer dereference occurs when assiging new_buf->vb. Avoid this by returning early on a memory allocation failure as there is not much more can be done at

[PATCH 3/8] staging: wilc1000: refactor interrupt handling for sdio

2020-02-14 Thread Ajay.Kathat
From: Ajay Singh Make use of FIELD_PREP/FIELD_GET macro to refactor the interrupt handling for SDIO. Signed-off-by: Ajay Singh --- drivers/staging/wilc1000/sdio.c | 98 - drivers/staging/wilc1000/spi.c | 4 -- drivers/staging/wilc1000/wlan.h | 3 + 3 files

[PATCH 1/8] staging: wilc1000: make use of FIELD_GET/_PREP macro

2020-02-14 Thread Ajay.Kathat
From: Ajay Singh Simplified the code by making use of FIELD_GET/_PREP bitfield macro. Signed-off-by: Ajay Singh --- drivers/staging/wilc1000/cfg80211.c | 2 +- drivers/staging/wilc1000/mon.c | 2 +- drivers/staging/wilc1000/netdev.h | 2 -- drivers/staging/wilc1000/spi.c | 2

[PATCH 8/8] staging: wilc1000: define macros to replace magic number values

2020-02-14 Thread Ajay.Kathat
From: Ajay Singh Define macros for global as well as SPI/SDIO specific register to avoid use of magic numbers. Signed-off-by: Ajay Singh --- drivers/staging/wilc1000/sdio.c | 7 ++- drivers/staging/wilc1000/spi.c | 17 --- drivers/staging/wilc1000/wlan.c | 83

[PATCH 7/8] staging: wilc1000: use short name for hif local variable in chip_wakeup()

2020-02-14 Thread Ajay.Kathat
From: Ajay Singh Make use of a shorter name for 'hif' variable to avoid possible 80 character checkpatch warning while the replacing hardcoded value with macros in chip_wakeup(). Signed-off-by: Ajay Singh --- drivers/staging/wilc1000/wlan.c | 35 +++-- 1 file

[PATCH 2/8] staging: wilc1000: remove use of MAX_NUN_INT_THRPT_ENH2 macro

2020-02-14 Thread Ajay.Kathat
From: Ajay Singh Make use of MAX_NUM_INT existing macro to handle the maximum supported interrupts count and removed MAX_NUN_INT_THRPT_ENH2 macro. Signed-off-by: Ajay Singh --- drivers/staging/wilc1000/sdio.c | 20 +++- drivers/staging/wilc1000/wlan.h | 2 +- 2 files changed,

[PATCH AUTOSEL 5.5 313/542] staging: rtl8188: avoid excessive stack usage

2020-02-14 Thread Sasha Levin
From: Arnd Bergmann [ Upstream commit c497ae2077c055b85c1bf04f3d182a84bd8f365b ] The rtl8188 copy of the os_dep support code causes a warning about a very significant stack usage in the translate_scan() function: drivers/staging/rtl8188eu/os_dep/ioctl_linux.c: In function 'translate_scan':

[PATCH AUTOSEL 5.5 353/542] vme: bridges: reduce stack usage

2020-02-14 Thread Sasha Levin
From: Arnd Bergmann [ Upstream commit 7483e7a939c074d887450ef1c4d9ccc5909405f8 ] With CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE_O3, the stack usage in vme_fake grows above the warning limit: drivers/vme/bridges/vme_fake.c: In function 'fake_master_read': drivers/vme/bridges/vme_fake.c:610:1: error:

RE

2020-02-14 Thread David Abula
Hallo, Schönen Tag, Bitte nehmen Sie meine aufrichtigen Glückwünsche an und ich weiß, dass diese Botschaft Sie überraschen kann, aber ich rate Ihnen, sie mit gutem Verständnis zu lesen. Ich bin Rechtsanwalt David Abula aus Togo. Daher gibt es einen bestimmten Betrag von 11,7 Mio. USD, der von

[PATCH 6/8] staging: wilc1000: define macros for different register address for SDIO

2020-02-14 Thread Ajay.Kathat
From: Ajay Singh Instead of using hardcoded value for SDIO register address added the macro for them. Signed-off-by: Ajay Singh --- drivers/staging/wilc1000/sdio.c | 77 + drivers/staging/wilc1000/wlan.h | 36 +++ 2 files changed, 76 insertions(+),

[PATCH 0/8] staging: wilc1000: remove magic values and handle review comments

2020-02-14 Thread Ajay.Kathat
From: Ajay Singh This patch series mainly contains changes to remove the magic value for different registers and define the macros for constant numbers. Also, it contains few patches to make use FIELD_GET/_PUT macro to extract the bitfield element. Ajay Singh (8): staging: wilc1000: make use

[PATCH 5/8] staging: wilc1000: use commmon function to set SDIO block size

2020-02-14 Thread Ajay.Kathat
From: Ajay Singh Use common function wilc_sdio_set_block_size() to set the block size for SDIO. Signed-off-by: Ajay Singh --- drivers/staging/wilc1000/sdio.c | 51 +++-- 1 file changed, 11 insertions(+), 40 deletions(-) diff --git a/drivers/staging/wilc1000/sdio.c

[PATCH 4/8] staging: wilc1000: make use of ALIGN macro

2020-02-14 Thread Ajay.Kathat
From: Ajay Singh Make use of 'ALIGN' macro to align the size data value. Signed-off-by: Ajay Singh --- drivers/staging/wilc1000/sdio.c | 34 ++--- drivers/staging/wilc1000/wlan.c | 4 +--- 2 files changed, 3 insertions(+), 35 deletions(-) diff --git

[PATCH AUTOSEL 5.4 308/459] vme: bridges: reduce stack usage

2020-02-14 Thread Sasha Levin
From: Arnd Bergmann [ Upstream commit 7483e7a939c074d887450ef1c4d9ccc5909405f8 ] With CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE_O3, the stack usage in vme_fake grows above the warning limit: drivers/vme/bridges/vme_fake.c: In function 'fake_master_read': drivers/vme/bridges/vme_fake.c:610:1: error:

[PATCH AUTOSEL 4.19 144/252] staging: rtl8188: avoid excessive stack usage

2020-02-14 Thread Sasha Levin
From: Arnd Bergmann [ Upstream commit c497ae2077c055b85c1bf04f3d182a84bd8f365b ] The rtl8188 copy of the os_dep support code causes a warning about a very significant stack usage in the translate_scan() function: drivers/staging/rtl8188eu/os_dep/ioctl_linux.c: In function 'translate_scan':

[PATCH AUTOSEL 5.4 272/459] staging: rtl8188: avoid excessive stack usage

2020-02-14 Thread Sasha Levin
From: Arnd Bergmann [ Upstream commit c497ae2077c055b85c1bf04f3d182a84bd8f365b ] The rtl8188 copy of the os_dep support code causes a warning about a very significant stack usage in the translate_scan() function: drivers/staging/rtl8188eu/os_dep/ioctl_linux.c: In function 'translate_scan':

[PATCH AUTOSEL 4.14 124/186] vme: bridges: reduce stack usage

2020-02-14 Thread Sasha Levin
From: Arnd Bergmann [ Upstream commit 7483e7a939c074d887450ef1c4d9ccc5909405f8 ] With CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE_O3, the stack usage in vme_fake grows above the warning limit: drivers/vme/bridges/vme_fake.c: In function 'fake_master_read': drivers/vme/bridges/vme_fake.c:610:1: error:

[PATCH AUTOSEL 4.9 097/141] vme: bridges: reduce stack usage

2020-02-14 Thread Sasha Levin
From: Arnd Bergmann [ Upstream commit 7483e7a939c074d887450ef1c4d9ccc5909405f8 ] With CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE_O3, the stack usage in vme_fake grows above the warning limit: drivers/vme/bridges/vme_fake.c: In function 'fake_master_read': drivers/vme/bridges/vme_fake.c:610:1: error:

[PATCH AUTOSEL 4.19 167/252] vme: bridges: reduce stack usage

2020-02-14 Thread Sasha Levin
From: Arnd Bergmann [ Upstream commit 7483e7a939c074d887450ef1c4d9ccc5909405f8 ] With CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE_O3, the stack usage in vme_fake grows above the warning limit: drivers/vme/bridges/vme_fake.c: In function 'fake_master_read': drivers/vme/bridges/vme_fake.c:610:1: error:

[PATCH] staging: fsl-dpaa2: ethsw: ethsw.c: Fix line over 80 characters

2020-02-14 Thread Sandesh Kenjana Ashok
Issue found by checkpatch. Signed-off-by: Sandesh Kenjana Ashok --- drivers/staging/fsl-dpaa2/ethsw/ethsw.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/staging/fsl-dpaa2/ethsw/ethsw.c b/drivers/staging/fsl-dpaa2/ethsw/ethsw.c index 39c0fe347188..676d1ad1b50d

Re: [PATCH v4 01/10] staging: most: remove device from interface structure

2020-02-14 Thread Greg KH
On Thu, Feb 06, 2020 at 09:14:55AM +, christian.gr...@microchip.com wrote: > On Fri, 2020-01-24 at 10:09 +0100, Greg KH wrote: > > EXTERNAL EMAIL: Do not click links or open attachments unless you > > know the content is safe > > > > On Fri, Jan 24, 2020 at 08:56:56AM +, > >

Re: [PATCH v2 1/2] staging: exfat: remove DOSNAMEs.

2020-02-14 Thread Greg Kroah-Hartman
On Fri, Feb 14, 2020 at 12:31:39PM +0900, Tetsuhiro Kohada wrote: > remove 'dos_name','ShortName' and related definitions. > > 'dos_name' and 'ShortName' are definitions before VFAT. > These are never used in exFAT. > > Signed-off-by: Tetsuhiro Kohada > --- > Changes in v2: > - Rebase to

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

2020-02-14 Thread Valdis Klētnieks
> Idea is simple. Expects that we have a clean filesystem in correct > state. We load primary/active/main FAT table (just call it FAT1) and all > changes to filesystem would be done via second non-active FAT table > (FAT2). At unmount or sync or flush buffer times, FAT2 would be copied > back to

Re: Fwd: GS_FPGABOOT

2020-02-14 Thread Greg KH
On Fri, Feb 14, 2020 at 07:07:23PM +0530, Shubakar Gowda wrote: > -- Forwarded message - > From: Shubakar Gowda > Date: Fri, 14 Feb 2020 at 19:04 > Subject: GS_FPGABOOT > To: > > > Hi, > > I am trying for Selectmap Programming using the driver gs_fgpaboot, But > when I load

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

2020-02-14 Thread Pali Rohár
On Friday 14 February 2020 17:16:18 Valdis Klētnieks wrote: > On Thu, 13 Feb 2020 16:18:47 -0500, Sasha Levin said: > > > >> I was hoping that it would be possible to easily use secondary FAT table > > >> (from TexFAT extension) for redundancy without need to implement full > > >> TexFAT, which

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

2020-02-14 Thread Valdis Klētnieks
On Thu, 13 Feb 2020 16:18:47 -0500, Sasha Levin said: > >> I was hoping that it would be possible to easily use secondary FAT table > >> (from TexFAT extension) for redundancy without need to implement full > >> TexFAT, which could be also backward compatible with systems which do > >> not

[PATCH AUTOSEL 5.5 392/542] staging: wfx: fix possible overflow on jiffies comparaison

2020-02-14 Thread Sasha Levin
From: Jérôme Pouiller [ Upstream commit def39be019b6494acd3570ce6f3f11ba1c3203a3 ] MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It is recommended to use function time_*() to compare jiffies. Signed-off-by: Jérôme Pouiller Link: