Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Rajan Vaja <RAJANV@xilinx.com>
To:     Greg KH <greg@kroah.com>, Stephen Rothwell <sfr@canb.auug.org.au>,
        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
Thread-Topic: linux-next: build warning after merge of the char-misc tree
Thread-Index: AQHWH4G2altuXUaUlkqQcFuutK4Ug6iSy/gAgAA4OWA=
Date:   Fri, 1 May 2020 10:17:26 +0000
Message-ID: <BYAPR02MB3941A306B8435DD8B09E62CBB7AB0@BYAPR02MB3941.namprd02.prod.outlook.com>
References: <20200501162806.155c44ed@canb.auug.org.au>
 <20200501065526.GA886609@kroah.com>
In-Reply-To: <20200501065526.GA886609@kroah.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 7fbf77ef-92df-4839-aeb2-08d7edb8d8d3
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 May 2020 10:17:26.2182
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 657af505-d5df-48d0-8300-c31994686c5c
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: qW6Wq3u4yMC/f0Uh0rMGDAJhWnlFA4giF/lT0gvMuGjPbJdiNtD9Gaoa+r6zfdrck3VHnEmssD7uTotfQI2gxA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR02MB5736
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Greg,

Thanks for notifying. I have submitted "[PATCH char-misc-next] crypto: xili=
nx: 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
>=20
> 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.
>=20
>=20
> 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 declar=
ed
> here
> >    87 |  unsigned int status;
> >       |               ^~~~~~
> >
> > Introduced by commit
> >
> >   bc86f9c54616 ("firmware: xilinx: Remove eemi ops for aes engine")
>=20
> Rajan, can you send me a patch to fix this up please?
>=20
> thanks,
>=20
> greg k-h