From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Rajan Vaja <rajan.vaja@xilinx.com>,
Jolly Shah <jolly.shah@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
Date: Fri, 1 May 2020 08:55:26 +0200 [thread overview]
Message-ID: <20200501065526.GA886609@kroah.com> (raw)
In-Reply-To: <20200501162806.155c44ed@canb.auug.org.au>
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
next prev parent reply other threads:[~2020-05-01 6:55 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 6:28 linux-next: build warning after merge of the char-misc tree Stephen Rothwell
2020-05-01 6:55 ` Greg KH [this message]
2020-05-01 10:17 ` Rajan Vaja
-- strict thread matches above, loose matches on Subject: below --
2024-04-15 5:22 Stephen Rothwell
2024-04-15 7:21 ` Greg KH
2022-07-15 11:43 Stephen Rothwell
2021-05-24 6:19 Stephen Rothwell
2021-04-06 11:44 Stephen Rothwell
2021-04-06 11:46 ` Stephen Rothwell
2021-04-06 14:07 ` Greg KH
2021-04-06 14:13 ` Gustavo Pimentel
2021-04-06 14:15 ` Greg KH
2021-04-06 17:28 ` Gustavo Pimentel
2021-04-06 17:33 ` Greg KH
2021-01-29 7:07 Stephen Rothwell
2019-04-26 5:56 Stephen Rothwell
2019-04-26 6:25 ` Greg KH
2019-04-26 14:30 ` Patrick Venture
2019-04-26 18:00 ` Patrick Venture
2018-10-02 9:12 Stephen Rothwell
2018-10-02 9:49 ` Bartosz Golaszewski
2018-10-02 9:56 ` Srinivas Kandagatla
2018-10-02 10:04 ` Bartosz Golaszewski
2018-10-02 5:31 Stephen Rothwell
2018-10-02 8:34 ` Bartosz Golaszewski
2017-12-12 3:39 Stephen Rothwell
2017-12-12 11:49 ` Greg KH
2017-07-20 4:12 Stephen Rothwell
2017-07-20 5:13 ` Greg KH
2017-07-20 14:52 ` KY Srinivasan
2017-07-20 9:14 ` Greg KH
2017-03-28 3:31 Stephen Rothwell
2017-03-28 3:58 ` Masahiro Yamada
2015-03-27 7:48 Stephen Rothwell
2015-03-31 19:35 ` Fabian Frederick
2015-04-03 14:05 ` Greg KH
2013-02-15 5:26 Stephen Rothwell
2013-02-15 17:34 ` Greg KH
2013-02-15 18:07 ` Arnd Bergmann
2013-02-15 20:05 ` Arnd Bergmann
2013-03-01 15:51 ` Sedat Dilek
2013-03-01 17:16 ` Arnd Bergmann
2013-03-01 17:43 ` Sedat Dilek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200501065526.GA886609@kroah.com \
--to=greg@kroah.com \
--cc=arnd@arndb.de \
--cc=jolly.shah@xilinx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rajan.vaja@xilinx.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).