Messages in this thread | | | From | Rajan Vaja <> | Subject | RE: [PATCH char-misc-next] crypto: xilinx: Handle AES PM API return status | Date | Fri, 1 May 2020 10:54:36 +0000 |
| |
Thanks Gerg for review.
I have updated reported by and fixes tag properly now. Sent v2.
Thanks Rajan
> -----Original Message----- > From: Greg KH <gregkh@linuxfoundation.org> > Sent: Friday, May 1, 2020 4:00 PM > To: Rajan Vaja <RAJANV@xilinx.com> > Cc: herbert@gondor.apana.org.au; davem@davemloft.net; Kalyani Akula > <kalyania@xilinx.com>; Michal Simek <michals@xilinx.com>; Jolly Shah > <JOLLYS@xilinx.com>; linux-crypto@vger.kernel.org; linux-arm- > kernel@lists.infradead.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH char-misc-next] crypto: xilinx: Handle AES PM API return > status > > 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 03:14:51AM -0700, Rajan Vaja wrote: > > Fixes: bc86f9c54616 ("firmware: xilinx: Remove eemi ops for aes > > engine") > > > > Return value of AES PM API is not handled which may result in > > unexpected value of "status" in zynqmp_pm_aes_engine(). > > > > Consider "status" value as valid only if AES PM API is successful. > > > > Signed-off-by: Rajan Vaja <rajan.vaja@xilinx.com> > > No "Reported-by:" line? > > And put the "Fixes:" line down in the s-o-b area please. > > thanks, > > greg k-h
| |