Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Fri, 1 May 2020 12:30:21 +0200
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Rajan Vaja <rajan.vaja@xilinx.com>
Cc:     herbert@gondor.apana.org.au, davem@davemloft.net,
        kalyani.akula@xilinx.com, michal.simek@xilinx.com,
        jolly.shah@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
Message-ID: <20200501103021.GA1416784@kroah.com>
References: <1588328091-16368-1-git-send-email-rajan.vaja@xilinx.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1588328091-16368-1-git-send-email-rajan.vaja@xilinx.com>
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk

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