[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YauRykMtyjNKTp+q@kernel.org>
Date: Sat, 4 Dec 2021 18:05:30 +0200
From: Mike Rapoport <rppt@...nel.org>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Martin Fernandez <martin.fernandez@...ypsium.com>,
linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org,
platform-driver-x86@...r.kernel.org, linux-mm@...ck.org,
tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
ardb@...nel.org, dvhart@...radead.org, andy@...radead.org,
rafael@...nel.org, akpm@...ux-foundation.org,
daniel.gutson@...ypsium.com, hughsient@...il.com,
alex.bazhaniuk@...ypsium.com, alison.schofield@...el.com
Subject: Re: [PATCH v3 3/5] Tag e820_entry with crypto capabilities
On Sat, Dec 04, 2021 at 09:21:51AM +0100, Greg KH wrote:
> On Fri, Dec 03, 2021 at 04:21:46PM -0300, Martin Fernandez wrote:
> > Add a new member in e820_entry to hold whether an entry is able to do
> > hardware memory encryption or not.
> >
> > Add a new argument to __e820__range_add to accept this new
> > crypto_capable.
>
> Shouldn't this Subject have the same prefix as patch 4/5?
I'd say it should be x86/e820
> thanks,
>
> greg k-h
--
Sincerely yours,
Mike.
Powered by blists - more mailing lists