[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024010509-pretty-proclaim-78e5@gregkh>
Date: Fri, 5 Jan 2024 08:44:36 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: jeffxu@...omium.org
Cc: akpm@...ux-foundation.org, keescook@...omium.org, jannh@...gle.com,
sroettger@...gle.com, willy@...radead.org,
torvalds@...ux-foundation.org, usama.anjum@...labora.com,
jeffxu@...gle.com, jorgelo@...omium.org, groeck@...omium.org,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-mm@...ck.org, pedro.falcato@...il.com, dave.hansen@...el.com,
linux-hardening@...r.kernel.org, deraadt@...nbsd.org
Subject: Re: [RFC PATCH v4 1/4] mseal: Wire up mseal syscall
On Thu, Jan 04, 2024 at 06:51:34PM +0000, jeffxu@...omium.org wrote:
> From: Jeff Xu <jeffxu@...omium.org>
>
> Wire up mseal syscall for all architectures.
>
> Signed-off-by: Jeff Xu <jeffxu@...omium.org>
Doesn't this break the build at this point in the patch series?
Normally you add the code for the syscall first, and then you wire it
up.
thanks,
greg k-h
Powered by blists - more mailing lists