[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191109083607.GB1289162@kroah.com>
Date: Sat, 9 Nov 2019 09:36:07 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Jules Irenge <jbi.octave@...il.com>
Cc: devel@...verdev.osuosl.org, Boqun.Feng@...rosoft.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: wfx: add gcc extension __force cast
On Fri, Nov 08, 2019 at 11:38:37PM +0000, Jules Irenge wrote:
> Add gcc extension __force and __le32 cast to fix warning issued by Sparse tool."warning: cast to restricted __le32"
Can you wrap your lines properly please?
>
> Signed-off-by: Jules Irenge <jbi.octave@...il.com>
> ---
> drivers/staging/wfx/debug.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/wfx/debug.c b/drivers/staging/wfx/debug.c
> index 0a9ca109039c..aa7b2dd691b9 100644
> --- a/drivers/staging/wfx/debug.c
> +++ b/drivers/staging/wfx/debug.c
> @@ -72,7 +72,7 @@ static int wfx_counters_show(struct seq_file *seq, void *v)
> return -EIO;
>
> #define PUT_COUNTER(name) \
> - seq_printf(seq, "%24s %d\n", #name ":", le32_to_cpu(counters.count_##name))
> + seq_printf(seq, "%24s %d\n", #name ":", le32_to_cpu((__force __le32)(counters.count_##name)))
That's usually a huge hint that something is wrong here. If the data
type isn't already le32, then why is the data needed to be printed out
that way? Shouldn't the data type itself be fixed instead?
thanks,
greg k-h
Powered by blists - more mailing lists