[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1dd1ca81905f865f69ac2fbfbc778e7fb76c8ee3.camel@intel.com>
Date: Fri, 2 Jun 2023 18:01:39 +0000
From: "Verma, Vishal L" <vishal.l.verma@...el.com>
To: "Jonathan.Cameron@...wei.com" <Jonathan.Cameron@...wei.com>
CC: "Jiang, Dave" <dave.jiang@...el.com>,
"Schofield, Alison" <alison.schofield@...el.com>,
"linux-cxl@...r.kernel.org" <linux-cxl@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Williams, Dan J" <dan.j.williams@...el.com>,
"Weiny, Ira" <ira.weiny@...el.com>,
"bwidawsk@...nel.org" <bwidawsk@...nel.org>,
"Weight, Russell H" <russell.h.weight@...el.com>,
"dave@...olabs.net" <dave@...olabs.net>
Subject: Re: [PATCH 4/4] tools/testing/cxl: add firmware update emulation to
CXL memdevs
On Thu, 2023-05-11 at 17:18 +0100, Jonathan Cameron wrote:
>
> ...
Addressed everything else for v2
>
> > +static int do_sha256(u8 *data, unsigned int length, u8 *hash)
>
> Can't use the one in include/crypto/sha2.h? Don't think anyone really
> cares about extreme performance here.
>
>
Ah nice, I hadn't seen that before. I was slightly concerned by the
comment there saying this is really only for kexec, and the other
interfaces were more document/prevalent. But using the interfaces in
include/crypto/sha2.h made the code a whole lot easier to follow /
maintain, so I've gone forward with it. We can always switch back later
if need be.
Powered by blists - more mailing lists