Received-SPF: pass (google.com: domain of linux-kernel+bounces-17555-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Date: Fri, 5 Jan 2024 08:44:36 +0100
From: Greg KH <gregkh@linuxfoundation.org>
To: jeffxu@chromium.org
Cc: akpm@linux-foundation.org, keescook@chromium.org, jannh@google.com,
	sroettger@google.com, willy@infradead.org,
	torvalds@linux-foundation.org, usama.anjum@collabora.com,
	jeffxu@google.com, jorgelo@chromium.org, groeck@chromium.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-mm@kvack.org, pedro.falcato@gmail.com, dave.hansen@intel.com,
	linux-hardening@vger.kernel.org, deraadt@openbsd.org
Subject: Re: [RFC PATCH v4 1/4] mseal: Wire up mseal syscall
Message-ID: <2024010509-pretty-proclaim-78e5@gregkh>
References: <20240104185138.169307-1-jeffxu@chromium.org>
 <20240104185138.169307-2-jeffxu@chromium.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20240104185138.169307-2-jeffxu@chromium.org>

On Thu, Jan 04, 2024 at 06:51:34PM +0000, jeffxu@chromium.org wrote:
> From: Jeff Xu <jeffxu@chromium.org>
> 
> Wire up mseal syscall for all architectures.
> 
> Signed-off-by: Jeff Xu <jeffxu@chromium.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