From: Johannes Berg <johannes@sipsolutions.net>
To: Eric Biggers <ebiggers@kernel.org>,
akpm@linux-foundation.org, linux-raid@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, x86@kernel.org,
Christoph Hellwig <hch@lst.de>,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
linux-um@lists.infradead.org
Subject: Re: [PATCH 1/3] um: Define kernel_fpu_begin_mask()
Date: Thu, 12 Nov 2026 08:28:38 +0100 [thread overview]
Message-ID: <199b6e10af2267bb60e7e73fda243f73b1b818ad.camel@sipsolutions.net> (raw)
In-Reply-To: <20261111205604.47547-2-ebiggers@kernel.org>
On Wed, 2026-11-11 at 12:56 -0800, Eric Biggers wrote:
> Define a stub for kernel_fpu_begin_mask() on user-mode Linux so that
> lib/raid/ can switch from kernel_fpu_begin() to kernel_fpu_begin_mask().
>
> Note: this causes a checkpatch error due to the macro's value not having
> outer parentheses, but it's left as-is for consistency with the existing
> kernel_fpu_begin() and kernel_fpu_end() definitions right next to it.
>
Probably should've CCed linux-um (done now), but the change seems fine.
There's no FPU handling needed in UM since the host kernel deals with
it.
johannes
next prev parent reply other threads:[~2026-11-12 7:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 20:56 [PATCH 0/3] lib/raid: opt out of initializing MXCSR and 387 state Eric Biggers
2026-11-11 20:56 ` [PATCH 1/3] um: Define kernel_fpu_begin_mask() Eric Biggers
2026-11-12 7:28 ` Johannes Berg [this message]
2026-11-11 20:56 ` [PATCH 2/3] xor: opt out of initializing MXCSR and 387 state Eric Biggers
2026-11-11 20:56 ` [PATCH 3/3] raid6: " Eric Biggers
2026-11-12 13:40 ` [PATCH 0/3] lib/raid: " Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199b6e10af2267bb60e7e73fda243f73b1b818ad.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=akpm@linux-foundation.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox