All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH 0/2] Fix sparse warnings
@ 2023-02-21  7:03 Ashok Reddy Soma
  2023-02-21  7:03 ` [PATCH 1/2] xilinx: zynqmp: Add missing prototype for zynqmp_mmio_write Ashok Reddy Soma
  2023-02-21  7:03 ` [PATCH 2/2] xilinx: zynqmp: Add missing prototype for board_boot_order Ashok Reddy Soma
  0 siblings, 2 replies; 15+ messages in thread
From: Ashok Reddy Soma @ 2023-02-21  7:03 UTC (permalink / raw)
  To: u-boot
  Cc: michal.simek, peng.fan, jh80.chung, jagan, sjg, alpernebiyasak,
	nathan.morrison, git, Ashok Reddy Soma

Run and fix sparse warnings in below files
 -arch/arm/mach-zynqmp/include/mach/sys_proto.h
 -common/spl/spl.c
 -arch/arm/mach-versal-net/include/mach/sys_proto.h
 -arch/arm/mach-versal/include/mach/sys_proto.h
 -drivers/mmc/zynq_sdhci.c
 -drivers/spi/zynqmp_gqspi.c



Algapally Santosh Sagar (2):
  xilinx: zynqmp: Add missing prototype for zynqmp_mmio_write
  xilinx: zynqmp: Add missing prototype for board_boot_order

 arch/arm/mach-versal-net/include/mach/sys_proto.h | 7 +------
 arch/arm/mach-versal/include/mach/sys_proto.h     | 6 +-----
 arch/arm/mach-zynqmp/include/mach/sys_proto.h     | 1 +
 common/spl/spl.c                                  | 1 +
 drivers/mmc/zynq_sdhci.c                          | 1 +
 drivers/spi/zynqmp_gqspi.c                        | 5 +++++
 6 files changed, 10 insertions(+), 11 deletions(-)

-- 
2.17.1


^ permalink raw reply	[flat|nested] 15+ messages in thread

* [PATCH 1/2] xilinx: zynqmp: Add missing prototype for zynqmp_mmio_write
  2023-02-21  7:03 [PATCH 0/2] Fix sparse warnings Ashok Reddy Soma
@ 2023-02-21  7:03 ` Ashok Reddy Soma
  2023-02-21  7:03 ` [PATCH 2/2] xilinx: zynqmp: Add missing prototype for board_boot_order Ashok Reddy Soma
  1 sibling, 0 replies; 15+ messages in thread
From: Ashok Reddy Soma @ 2023-02-21  7:03 UTC (permalink / raw)
  To: u-boot
  Cc: michal.simek, peng.fan, jh80.chung, jagan, sjg, alpernebiyasak,
	nathan.morrison, git, Algapally Santosh Sagar, Ashok Reddy Soma

From: Algapally Santosh Sagar <santoshsagar.algapally@amd.com>

Add missing prototype to fix the sparse warning, warning: no
previous prototype for 'zynqmp_mmio_write' [-Wmissing-prototypes].

Signed-off-by: Algapally Santosh Sagar <santoshsagar.algapally@amd.com>
Signed-off-by: Ashok Reddy Soma <ashok.reddy.soma@amd.com>
---

 arch/arm/mach-versal-net/include/mach/sys_proto.h | 7 +------
 arch/arm/mach-versal/include/mach/sys_proto.h     | 6 +-----
 drivers/mmc/zynq_sdhci.c                          | 1 +
 drivers/spi/zynqmp_gqspi.c                        | 5 +++++
 4 files changed, 8 insertions(+), 11 deletions(-)

diff --git a/arch/arm/mach-versal-net/include/mach/sys_proto.h b/arch/arm/mach-versal-net/include/mach/sys_proto.h
index 5bba9030f2..a20cf02712 100644
--- a/arch/arm/mach-versal-net/include/mach/sys_proto.h
+++ b/arch/arm/mach-versal-net/include/mach/sys_proto.h
@@ -8,9 +8,4 @@
 
 void mem_map_fill(void);
 
-static inline int zynqmp_mmio_write(const u32 address, const u32 mask,
-				    const u32 value)
-{
-	BUILD_BUG();
-	return -EINVAL;
-}
+int zynqmp_mmio_write(const u32 address, const u32 mask, const u32 value);
diff --git a/arch/arm/mach-versal/include/mach/sys_proto.h b/arch/arm/mach-versal/include/mach/sys_proto.h
index 8e5712e0c9..3f01508ecb 100644
--- a/arch/arm/mach-versal/include/mach/sys_proto.h
+++ b/arch/arm/mach-versal/include/mach/sys_proto.h
@@ -13,8 +13,4 @@ enum {
 void tcm_init(u8 mode);
 void mem_map_fill(void);
 
-static inline int zynqmp_mmio_write(const u32 address, const u32 mask, const u32 value)
-{
-	BUILD_BUG();
-	return -EINVAL;
-}
+int zynqmp_mmio_write(const u32 address, const u32 mask, const u32 value);
diff --git a/drivers/mmc/zynq_sdhci.c b/drivers/mmc/zynq_sdhci.c
index 8b559d8a7a..9dc310663f 100644
--- a/drivers/mmc/zynq_sdhci.c
+++ b/drivers/mmc/zynq_sdhci.c
@@ -14,6 +14,7 @@
 #include "mmc_private.h"
 #include <log.h>
 #include <reset.h>
+#include <asm/arch/sys_proto.h>
 #include <dm/device_compat.h>
 #include <linux/err.h>
 #include <linux/libfdt.h>
diff --git a/drivers/spi/zynqmp_gqspi.c b/drivers/spi/zynqmp_gqspi.c
index 335b458cb9..c4aee279aa 100644
--- a/drivers/spi/zynqmp_gqspi.c
+++ b/drivers/spi/zynqmp_gqspi.c
@@ -183,6 +183,11 @@ struct zynqmp_qspi_priv {
 	const struct spi_mem_op *op;
 };
 
+__weak int zynqmp_mmio_write(const u32 address, const u32 mask, const u32 value)
+{
+	return 0;
+}
+
 static int zynqmp_qspi_of_to_plat(struct udevice *bus)
 {
 	struct zynqmp_qspi_plat *plat = dev_get_plat(bus);
-- 
2.17.1


^ permalink raw reply related	[flat|nested] 15+ messages in thread

* [PATCH 2/2] xilinx: zynqmp: Add missing prototype for board_boot_order
  2023-02-21  7:03 [PATCH 0/2] Fix sparse warnings Ashok Reddy Soma
  2023-02-21  7:03 ` [PATCH 1/2] xilinx: zynqmp: Add missing prototype for zynqmp_mmio_write Ashok Reddy Soma
@ 2023-02-21  7:03 ` Ashok Reddy Soma
  2023-02-21  7:51   ` Michal Simek
  1 sibling, 1 reply; 15+ messages in thread
From: Ashok Reddy Soma @ 2023-02-21  7:03 UTC (permalink / raw)
  To: u-boot
  Cc: michal.simek, peng.fan, jh80.chung, jagan, sjg, alpernebiyasak,
	nathan.morrison, git, Algapally Santosh Sagar, Ashok Reddy Soma

From: Algapally Santosh Sagar <santoshsagar.algapally@amd.com>

Add missing prototype to fix the sparse warning, warning: no
previous prototype for 'board_boot_order' [-Wmissing-prototypes].

Signed-off-by: Algapally Santosh Sagar <santoshsagar.algapally@amd.com>
Signed-off-by: Ashok Reddy Soma <ashok.reddy.soma@amd.com>
---

 arch/arm/mach-zynqmp/include/mach/sys_proto.h | 1 +
 common/spl/spl.c                              | 1 +
 2 files changed, 2 insertions(+)

diff --git a/arch/arm/mach-zynqmp/include/mach/sys_proto.h b/arch/arm/mach-zynqmp/include/mach/sys_proto.h
index c6733ed1bb..0f648c47a3 100644
--- a/arch/arm/mach-zynqmp/include/mach/sys_proto.h
+++ b/arch/arm/mach-zynqmp/include/mach/sys_proto.h
@@ -51,6 +51,7 @@ unsigned int zynqmp_get_silicon_version(void);
 int zynqmp_mmio_write(const u32 address, const u32 mask, const u32 value);
 int zynqmp_mmio_read(const u32 address, u32 *value);
 
+void board_boot_order(u32 *spl_boot_list);
 void initialize_tcm(bool mode);
 void mem_map_fill(void);
 #if defined(CONFIG_SYS_MEM_RSVD_FOR_MMU) || defined(CONFIG_DEFINE_TCM_OCM_MMAP)
diff --git a/common/spl/spl.c b/common/spl/spl.c
index a630e79866..6e5f326481 100644
--- a/common/spl/spl.c
+++ b/common/spl/spl.c
@@ -20,6 +20,7 @@
 #include <serial.h>
 #include <spl.h>
 #include <system-constants.h>
+#include <asm/arch/sys_proto.h>
 #include <asm/global_data.h>
 #include <asm-generic/gpio.h>
 #include <asm/u-boot.h>
-- 
2.17.1


^ permalink raw reply related	[flat|nested] 15+ messages in thread

* Re: [PATCH 2/2] xilinx: zynqmp: Add missing prototype for board_boot_order
  2023-02-21  7:03 ` [PATCH 2/2] xilinx: zynqmp: Add missing prototype for board_boot_order Ashok Reddy Soma
@ 2023-02-21  7:51   ` Michal Simek
  0 siblings, 0 replies; 15+ messages in thread
From: Michal Simek @ 2023-02-21  7:51 UTC (permalink / raw)
  To: Ashok Reddy Soma, u-boot
  Cc: peng.fan, jh80.chung, jagan, sjg, alpernebiyasak,
	nathan.morrison, git, Algapally Santosh Sagar



On 2/21/23 08:03, Ashok Reddy Soma wrote:
> From: Algapally Santosh Sagar <santoshsagar.algapally@amd.com>
> 
> Add missing prototype to fix the sparse warning, warning: no
> previous prototype for 'board_boot_order' [-Wmissing-prototypes].
> 
> Signed-off-by: Algapally Santosh Sagar <santoshsagar.algapally@amd.com>
> Signed-off-by: Ashok Reddy Soma <ashok.reddy.soma@amd.com>
> ---
> 
>   arch/arm/mach-zynqmp/include/mach/sys_proto.h | 1 +
>   common/spl/spl.c                              | 1 +
>   2 files changed, 2 insertions(+)
> 
> diff --git a/arch/arm/mach-zynqmp/include/mach/sys_proto.h b/arch/arm/mach-zynqmp/include/mach/sys_proto.h
> index c6733ed1bb..0f648c47a3 100644
> --- a/arch/arm/mach-zynqmp/include/mach/sys_proto.h
> +++ b/arch/arm/mach-zynqmp/include/mach/sys_proto.h
> @@ -51,6 +51,7 @@ unsigned int zynqmp_get_silicon_version(void);
>   int zynqmp_mmio_write(const u32 address, const u32 mask, const u32 value);
>   int zynqmp_mmio_read(const u32 address, u32 *value);
>   
> +void board_boot_order(u32 *spl_boot_list);
>   void initialize_tcm(bool mode);
>   void mem_map_fill(void);
>   #if defined(CONFIG_SYS_MEM_RSVD_FOR_MMU) || defined(CONFIG_DEFINE_TCM_OCM_MMAP)
> diff --git a/common/spl/spl.c b/common/spl/spl.c
> index a630e79866..6e5f326481 100644
> --- a/common/spl/spl.c
> +++ b/common/spl/spl.c
> @@ -20,6 +20,7 @@
>   #include <serial.h>
>   #include <spl.h>
>   #include <system-constants.h>
> +#include <asm/arch/sys_proto.h>

This doesn't look right because then you expect all spl platforms will have this 
header which is not the case.

It should go to include/spl.h

>   #include <asm/global_data.h>
>   #include <asm-generic/gpio.h>
>   #include <asm/u-boot.h>

M

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 0/2] Fix sparse warnings
  2023-06-09  9:05 [PATCH 0/2] Fix sparse warnings Ashok Reddy Soma
@ 2023-06-12  6:36 ` Michal Simek
  0 siblings, 0 replies; 15+ messages in thread
From: Michal Simek @ 2023-06-12  6:36 UTC (permalink / raw)
  To: Ashok Reddy Soma, u-boot; +Cc: git



On 6/9/23 11:05, Ashok Reddy Soma wrote:
> In this patch series, fix sparse warnings in below files
>   - arch/arm/mach-versal/mp.c
>   - arch/arm/mach-versal/include/mach/sys_proto.h
> 
> 
> 
> Algapally Santosh Sagar (2):
>    arm64: versal: Add missing prototype for initialize_tcm
>    arm64: versal: Add missing prototypes
> 
>   arch/arm/mach-versal/include/mach/sys_proto.h | 1 +
>   arch/arm/mach-versal/mp.c                     | 8 ++++----
>   2 files changed, 5 insertions(+), 4 deletions(-)
> 

Applied.
M

^ permalink raw reply	[flat|nested] 15+ messages in thread

* [PATCH 0/2] Fix sparse warnings
@ 2023-06-09  9:05 Ashok Reddy Soma
  2023-06-12  6:36 ` Michal Simek
  0 siblings, 1 reply; 15+ messages in thread
From: Ashok Reddy Soma @ 2023-06-09  9:05 UTC (permalink / raw)
  To: u-boot; +Cc: michal.simek, git, Ashok Reddy Soma

In this patch series, fix sparse warnings in below files
 - arch/arm/mach-versal/mp.c
 - arch/arm/mach-versal/include/mach/sys_proto.h



Algapally Santosh Sagar (2):
  arm64: versal: Add missing prototype for initialize_tcm
  arm64: versal: Add missing prototypes

 arch/arm/mach-versal/include/mach/sys_proto.h | 1 +
 arch/arm/mach-versal/mp.c                     | 8 ++++----
 2 files changed, 5 insertions(+), 4 deletions(-)

-- 
2.17.1


^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 0/2] fix sparse warnings
  2021-02-24 15:06     ` Dan Carpenter
@ 2021-02-24 16:12       ` karthek
  -1 siblings, 0 replies; 15+ messages in thread
From: karthek @ 2021-02-24 16:12 UTC (permalink / raw)
  To: Dan Carpenter
  Cc: Greg Kroah-Hartman, Lee Jones, Jakub Kicinski, Arnd Bergmann,
	Johannes Berg, devel, linux-kernel

On Wed, Feb 24, 2021 at 06:06:48PM +0300, Dan Carpenter wrote:
> On Wed, Feb 24, 2021 at 08:26:41PM +0530, karthek wrote:
> > On Sun, Feb 21, 2021 at 09:00:48PM +0530, karthik alapati wrote:
> > > the following patches fixes two  byte-order issues
> > > and fixes these sparse warnings
> > > 
> > > 
> > > drivers/staging//wimax/i2400m/op-rfkill.c:89:25: warning: incorrect type in assignment (different base types)
> > > drivers/staging//wimax/i2400m/op-rfkill.c:89:25:    expected restricted __le16 [usertype] length
> > > drivers/staging//wimax/i2400m/op-rfkill.c:89:25:    got unsigned long
> > > .
> > > drivers/staging//wimax/i2400m/fw.c:514:27: warning: restricted __le32 degrades to integer
> > > 
> > > 
> > > karthik alapati (2):
> > >   staging: wimax/i2400m: fix byte-order issue
> > >   staging: wimax/i2400m: convert __le32 type to host byte-order
> > > 
> > >  drivers/staging/wimax/i2400m/fw.c        | 2 +-
> > >  drivers/staging/wimax/i2400m/op-rfkill.c | 2 +-
> > >  2 files changed, 2 insertions(+), 2 deletions(-)
> > > 
> > > -- 
> > > 2.30.1
> > > 
> > ping?
> 
> The merge window is open so no one is merging these types of fixes now.
> Wait until -rc1 is out, and then give the maintainer two weeks to look
> at your patch and get back to you.
> 
> regards,
> dan carpenter
>
thanks dan, Got it.

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 0/2] fix sparse warnings
@ 2021-02-24 16:12       ` karthek
  0 siblings, 0 replies; 15+ messages in thread
From: karthek @ 2021-02-24 16:12 UTC (permalink / raw)
  To: Dan Carpenter
  Cc: devel, Arnd Bergmann, Greg Kroah-Hartman, linux-kernel,
	Jakub Kicinski, Johannes Berg, Lee Jones

On Wed, Feb 24, 2021 at 06:06:48PM +0300, Dan Carpenter wrote:
> On Wed, Feb 24, 2021 at 08:26:41PM +0530, karthek wrote:
> > On Sun, Feb 21, 2021 at 09:00:48PM +0530, karthik alapati wrote:
> > > the following patches fixes two  byte-order issues
> > > and fixes these sparse warnings
> > > 
> > > 
> > > drivers/staging//wimax/i2400m/op-rfkill.c:89:25: warning: incorrect type in assignment (different base types)
> > > drivers/staging//wimax/i2400m/op-rfkill.c:89:25:    expected restricted __le16 [usertype] length
> > > drivers/staging//wimax/i2400m/op-rfkill.c:89:25:    got unsigned long
> > > .
> > > drivers/staging//wimax/i2400m/fw.c:514:27: warning: restricted __le32 degrades to integer
> > > 
> > > 
> > > karthik alapati (2):
> > >   staging: wimax/i2400m: fix byte-order issue
> > >   staging: wimax/i2400m: convert __le32 type to host byte-order
> > > 
> > >  drivers/staging/wimax/i2400m/fw.c        | 2 +-
> > >  drivers/staging/wimax/i2400m/op-rfkill.c | 2 +-
> > >  2 files changed, 2 insertions(+), 2 deletions(-)
> > > 
> > > -- 
> > > 2.30.1
> > > 
> > ping?
> 
> The merge window is open so no one is merging these types of fixes now.
> Wait until -rc1 is out, and then give the maintainer two weeks to look
> at your patch and get back to you.
> 
> regards,
> dan carpenter
>
thanks dan, Got it.
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 0/2] fix sparse warnings
  2021-02-24 14:56   ` karthek
@ 2021-02-24 15:06     ` Dan Carpenter
  -1 siblings, 0 replies; 15+ messages in thread
From: Dan Carpenter @ 2021-02-24 15:06 UTC (permalink / raw)
  To: karthek
  Cc: Greg Kroah-Hartman, Lee Jones, Jakub Kicinski, Arnd Bergmann,
	Johannes Berg, devel, linux-kernel

On Wed, Feb 24, 2021 at 08:26:41PM +0530, karthek wrote:
> On Sun, Feb 21, 2021 at 09:00:48PM +0530, karthik alapati wrote:
> > the following patches fixes two  byte-order issues
> > and fixes these sparse warnings
> > 
> > 
> > drivers/staging//wimax/i2400m/op-rfkill.c:89:25: warning: incorrect type in assignment (different base types)
> > drivers/staging//wimax/i2400m/op-rfkill.c:89:25:    expected restricted __le16 [usertype] length
> > drivers/staging//wimax/i2400m/op-rfkill.c:89:25:    got unsigned long
> > .
> > drivers/staging//wimax/i2400m/fw.c:514:27: warning: restricted __le32 degrades to integer
> > 
> > 
> > karthik alapati (2):
> >   staging: wimax/i2400m: fix byte-order issue
> >   staging: wimax/i2400m: convert __le32 type to host byte-order
> > 
> >  drivers/staging/wimax/i2400m/fw.c        | 2 +-
> >  drivers/staging/wimax/i2400m/op-rfkill.c | 2 +-
> >  2 files changed, 2 insertions(+), 2 deletions(-)
> > 
> > -- 
> > 2.30.1
> > 
> ping?

The merge window is open so no one is merging these types of fixes now.
Wait until -rc1 is out, and then give the maintainer two weeks to look
at your patch and get back to you.

regards,
dan carpenter


^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 0/2] fix sparse warnings
@ 2021-02-24 15:06     ` Dan Carpenter
  0 siblings, 0 replies; 15+ messages in thread
From: Dan Carpenter @ 2021-02-24 15:06 UTC (permalink / raw)
  To: karthek
  Cc: devel, Arnd Bergmann, Greg Kroah-Hartman, linux-kernel,
	Jakub Kicinski, Johannes Berg, Lee Jones

On Wed, Feb 24, 2021 at 08:26:41PM +0530, karthek wrote:
> On Sun, Feb 21, 2021 at 09:00:48PM +0530, karthik alapati wrote:
> > the following patches fixes two  byte-order issues
> > and fixes these sparse warnings
> > 
> > 
> > drivers/staging//wimax/i2400m/op-rfkill.c:89:25: warning: incorrect type in assignment (different base types)
> > drivers/staging//wimax/i2400m/op-rfkill.c:89:25:    expected restricted __le16 [usertype] length
> > drivers/staging//wimax/i2400m/op-rfkill.c:89:25:    got unsigned long
> > .
> > drivers/staging//wimax/i2400m/fw.c:514:27: warning: restricted __le32 degrades to integer
> > 
> > 
> > karthik alapati (2):
> >   staging: wimax/i2400m: fix byte-order issue
> >   staging: wimax/i2400m: convert __le32 type to host byte-order
> > 
> >  drivers/staging/wimax/i2400m/fw.c        | 2 +-
> >  drivers/staging/wimax/i2400m/op-rfkill.c | 2 +-
> >  2 files changed, 2 insertions(+), 2 deletions(-)
> > 
> > -- 
> > 2.30.1
> > 
> ping?

The merge window is open so no one is merging these types of fixes now.
Wait until -rc1 is out, and then give the maintainer two weeks to look
at your patch and get back to you.

regards,
dan carpenter

_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 0/2] fix sparse warnings
  2021-02-21 15:30 ` karthik alapati
@ 2021-02-24 14:56   ` karthek
  -1 siblings, 0 replies; 15+ messages in thread
From: karthek @ 2021-02-24 14:56 UTC (permalink / raw)
  To: Greg Kroah-Hartman, Lee Jones, Jakub Kicinski, Arnd Bergmann,
	Johannes Berg
  Cc: devel, linux-kernel

On Sun, Feb 21, 2021 at 09:00:48PM +0530, karthik alapati wrote:
> the following patches fixes two  byte-order issues
> and fixes these sparse warnings
> 
> 
> drivers/staging//wimax/i2400m/op-rfkill.c:89:25: warning: incorrect type in assignment (different base types)
> drivers/staging//wimax/i2400m/op-rfkill.c:89:25:    expected restricted __le16 [usertype] length
> drivers/staging//wimax/i2400m/op-rfkill.c:89:25:    got unsigned long
> .
> drivers/staging//wimax/i2400m/fw.c:514:27: warning: restricted __le32 degrades to integer
> 
> 
> karthik alapati (2):
>   staging: wimax/i2400m: fix byte-order issue
>   staging: wimax/i2400m: convert __le32 type to host byte-order
> 
>  drivers/staging/wimax/i2400m/fw.c        | 2 +-
>  drivers/staging/wimax/i2400m/op-rfkill.c | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> -- 
> 2.30.1
> 
ping?

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: [PATCH 0/2] fix sparse warnings
@ 2021-02-24 14:56   ` karthek
  0 siblings, 0 replies; 15+ messages in thread
From: karthek @ 2021-02-24 14:56 UTC (permalink / raw)
  To: Greg Kroah-Hartman, Lee Jones, Jakub Kicinski, Arnd Bergmann,
	Johannes Berg
  Cc: devel, linux-kernel

On Sun, Feb 21, 2021 at 09:00:48PM +0530, karthik alapati wrote:
> the following patches fixes two  byte-order issues
> and fixes these sparse warnings
> 
> 
> drivers/staging//wimax/i2400m/op-rfkill.c:89:25: warning: incorrect type in assignment (different base types)
> drivers/staging//wimax/i2400m/op-rfkill.c:89:25:    expected restricted __le16 [usertype] length
> drivers/staging//wimax/i2400m/op-rfkill.c:89:25:    got unsigned long
> .
> drivers/staging//wimax/i2400m/fw.c:514:27: warning: restricted __le32 degrades to integer
> 
> 
> karthik alapati (2):
>   staging: wimax/i2400m: fix byte-order issue
>   staging: wimax/i2400m: convert __le32 type to host byte-order
> 
>  drivers/staging/wimax/i2400m/fw.c        | 2 +-
>  drivers/staging/wimax/i2400m/op-rfkill.c | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> -- 
> 2.30.1
> 
ping?
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* [PATCH 0/2] fix sparse warnings
@ 2021-02-21 15:30 ` karthik alapati
  0 siblings, 0 replies; 15+ messages in thread
From: karthik alapati @ 2021-02-21 15:30 UTC (permalink / raw)
  To: Greg Kroah-Hartman, Lee Jones, Jakub Kicinski, Arnd Bergmann,
	Johannes Berg
  Cc: devel, linux-kernel

the following patches fixes two  byte-order issues
and fixes these sparse warnings


drivers/staging//wimax/i2400m/op-rfkill.c:89:25: warning: incorrect type in assignment (different base types)
drivers/staging//wimax/i2400m/op-rfkill.c:89:25:    expected restricted __le16 [usertype] length
drivers/staging//wimax/i2400m/op-rfkill.c:89:25:    got unsigned long
.
drivers/staging//wimax/i2400m/fw.c:514:27: warning: restricted __le32 degrades to integer


karthik alapati (2):
  staging: wimax/i2400m: fix byte-order issue
  staging: wimax/i2400m: convert __le32 type to host byte-order

 drivers/staging/wimax/i2400m/fw.c        | 2 +-
 drivers/staging/wimax/i2400m/op-rfkill.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

-- 
2.30.1


^ permalink raw reply	[flat|nested] 15+ messages in thread

* [PATCH 0/2] fix sparse warnings
@ 2021-02-21 15:30 ` karthik alapati
  0 siblings, 0 replies; 15+ messages in thread
From: karthik alapati @ 2021-02-21 15:30 UTC (permalink / raw)
  To: Greg Kroah-Hartman, Lee Jones, Jakub Kicinski, Arnd Bergmann,
	Johannes Berg
  Cc: devel, linux-kernel

the following patches fixes two  byte-order issues
and fixes these sparse warnings


drivers/staging//wimax/i2400m/op-rfkill.c:89:25: warning: incorrect type in assignment (different base types)
drivers/staging//wimax/i2400m/op-rfkill.c:89:25:    expected restricted __le16 [usertype] length
drivers/staging//wimax/i2400m/op-rfkill.c:89:25:    got unsigned long
.
drivers/staging//wimax/i2400m/fw.c:514:27: warning: restricted __le32 degrades to integer


karthik alapati (2):
  staging: wimax/i2400m: fix byte-order issue
  staging: wimax/i2400m: convert __le32 type to host byte-order

 drivers/staging/wimax/i2400m/fw.c        | 2 +-
 drivers/staging/wimax/i2400m/op-rfkill.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

-- 
2.30.1

_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

^ permalink raw reply	[flat|nested] 15+ messages in thread

* [PATCH 0/2] Fix sparse warnings
@ 2015-10-29 20:41 Ksenija Stanojevic
  0 siblings, 0 replies; 15+ messages in thread
From: Ksenija Stanojevic @ 2015-10-29 20:41 UTC (permalink / raw)
  To: outreachy-kernel; +Cc: Ksenija Stanojevic

Remove EFUSE_Write1Byte and make Efuse_ReadAllMap function static

Found by sparse.

Signed-off-by: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>

Ksenija Stanojevic (2):
  Staging: rtl8723au: Remove unused EFUSE_Write1Byte function
  Staging: rtl8723au: Declare function static

 drivers/staging/rtl8723au/core/rtw_efuse.c | 45 ++----------------------------
 1 file changed, 2 insertions(+), 43 deletions(-)

-- 
1.9.1



^ permalink raw reply	[flat|nested] 15+ messages in thread

end of thread, other threads:[~2023-06-12  6:36 UTC | newest]

Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-21  7:03 [PATCH 0/2] Fix sparse warnings Ashok Reddy Soma
2023-02-21  7:03 ` [PATCH 1/2] xilinx: zynqmp: Add missing prototype for zynqmp_mmio_write Ashok Reddy Soma
2023-02-21  7:03 ` [PATCH 2/2] xilinx: zynqmp: Add missing prototype for board_boot_order Ashok Reddy Soma
2023-02-21  7:51   ` Michal Simek
  -- strict thread matches above, loose matches on Subject: below --
2023-06-09  9:05 [PATCH 0/2] Fix sparse warnings Ashok Reddy Soma
2023-06-12  6:36 ` Michal Simek
2021-02-21 15:30 [PATCH 0/2] fix " karthik alapati
2021-02-21 15:30 ` karthik alapati
2021-02-24 14:56 ` karthek
2021-02-24 14:56   ` karthek
2021-02-24 15:06   ` Dan Carpenter
2021-02-24 15:06     ` Dan Carpenter
2021-02-24 16:12     ` karthek
2021-02-24 16:12       ` karthek
2015-10-29 20:41 [PATCH 0/2] Fix " Ksenija Stanojevic

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.