lkml.org 
[lkml]   [2020]   [May]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: linux-next: build warning after merge of the char-misc tree
Date
Hi Greg,

Thanks for notifying. I have submitted "[PATCH char-misc-next] crypto: xilinx: Handle AES PM API return status" to fix warning.

Thanks,
Rajan

> -----Original Message-----
> From: Greg KH <greg@kroah.com>
> Sent: Friday, May 1, 2020 12:25 PM
> To: Stephen Rothwell <sfr@canb.auug.org.au>; Rajan Vaja
> <RAJANV@xilinx.com>; Jolly Shah <JOLLYS@xilinx.com>
> Cc: Arnd Bergmann <arnd@arndb.de>; Linux Next Mailing List <linux-
> next@vger.kernel.org>; Linux Kernel Mailing List <linux-
> kernel@vger.kernel.org>
> Subject: Re: linux-next: build warning after merge of the char-misc tree
>
> CAUTION: This message has originated from an External Source. Please use
> proper judgment and caution when opening attachments, clicking links, or
> responding to this email.
>
>
> On Fri, May 01, 2020 at 04:28:06PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the char-misc tree, today's linux-next build (x86_64
> > allmodconfig) produced this warning:
> >
> > drivers/crypto/xilinx/zynqmp-aes-gcm.c: In function
> 'zynqmp_handle_aes_req':
> > drivers/crypto/xilinx/zynqmp-aes-gcm.c:137:5: warning: 'status' may be
> used uninitialized in this function [-Wmaybe-uninitialized]
> > 137 | if (status) {
> > | ^
> > drivers/crypto/xilinx/zynqmp-aes-gcm.c:87:15: note: 'status' was declared
> here
> > 87 | unsigned int status;
> > | ^~~~~~
> >
> > Introduced by commit
> >
> > bc86f9c54616 ("firmware: xilinx: Remove eemi ops for aes engine")
>
> Rajan, can you send me a patch to fix this up please?
>
> thanks,
>
> greg k-h

\
 
 \ /
  Last update: 2020-05-01 12:18    [W:0.046 / U:0.392 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site