From: Sasha Levin <sashal@kernel.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Hou Tao <houtao1@huawei.com>, Sohil Mehta <sohil.mehta@intel.com>,
Alexei Starovoitov <ast@kernel.org>,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org
Subject: Re: [PATCH AUTOSEL 4.19 1/4] x86/mm: Move is_vsyscall_vaddr() into asm/vsyscall.h
Date: Mon, 18 Mar 2024 08:49:47 -0400 [thread overview]
Message-ID: <Zfg4a5Y1UnFO3O1m@sashalap> (raw)
In-Reply-To: <Ze9zol7kZucywfOy@duo.ucw.cz>
On Mon, Mar 11, 2024 at 10:12:02PM +0100, Pavel Machek wrote:
>Hi!
>
>> Move is_vsyscall_vaddr() into asm/vsyscall.h to make it available for
>> copy_from_kernel_nofault_allowed() in arch/x86/mm/maccess.c.
>
>This seems to be just part of a patch -- it does not move anything --
>and we should not really need it for 4.19, as we don't have those
>copy_from_kernel_nofault_allowed changes.
Yup, looks like it's not needed on <5.10.
--
Thanks,
Sasha
prev parent reply other threads:[~2024-03-18 12:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 20:42 [PATCH AUTOSEL 4.19 1/4] x86/mm: Move is_vsyscall_vaddr() into asm/vsyscall.h Sasha Levin
2024-02-29 20:42 ` [PATCH AUTOSEL 4.19 2/4] net/iucv: fix the allocation size of iucv_path_table array Sasha Levin
2024-02-29 20:42 ` [PATCH AUTOSEL 4.19 3/4] block: sed-opal: handle empty atoms when parsing response Sasha Levin
2024-02-29 20:42 ` [PATCH AUTOSEL 4.19 4/4] dm-verity, dm-crypt: align "struct bvec_iter" correctly Sasha Levin
2024-03-11 21:12 ` [PATCH AUTOSEL 4.19 1/4] x86/mm: Move is_vsyscall_vaddr() into asm/vsyscall.h Pavel Machek
2024-03-18 12:49 ` Sasha Levin [this message]
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=Zfg4a5Y1UnFO3O1m@sashalap \
--to=sashal@kernel.org \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=houtao1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=sohil.mehta@intel.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--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