From: Ingo Molnar <mingo@kernel.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Andy Lutomirski <luto@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Eric Biederman <ebiederm@xmission.com>,
Kees Cook <kees@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/2] x86: vdso: Two small ifdef cleanups
Date: Tue, 22 Apr 2025 14:25:34 +0200 [thread overview]
Message-ID: <aAeKvpzKsLsKzK8J@gmail.com> (raw)
In-Reply-To: <20240910-x86-vdso-ifdef-v1-0-877c9df9b081@linutronix.de>
* Thomas Weißschuh <thomas.weissschuh@linutronix.de> wrote:
> Some small non-functional cleanups to make the vdso setup easier to
> read.
>
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> ---
> Thomas Weißschuh (2):
> x86: vdso: Remove ifdeffery around page setup variants
> x86: vdso: Remove redundant ifdeffery around in_ia32_syscall()
>
> arch/x86/entry/vdso/vma.c | 35 ++++++++++++-----------------------
> arch/x86/include/asm/elf.h | 4 ----
> arch/x86/include/asm/vdso.h | 8 --------
> 3 files changed, 12 insertions(+), 35 deletions(-)
Looks like these patches fell between the cracks - I'm applying them to
tip:x86/vdso if nobody objects.
Thanks,
Ingo
prev parent reply other threads:[~2025-04-22 12:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 10:11 [PATCH 0/2] x86: vdso: Two small ifdef cleanups Thomas Weißschuh
2024-09-10 10:11 ` [PATCH 1/2] x86: vdso: Remove ifdeffery around page setup variants Thomas Weißschuh
2025-04-22 12:47 ` [tip: x86/entry] x86/vdso: Remove #ifdeffery " tip-bot2 for Thomas Weißschuh
2024-09-10 10:11 ` [PATCH 2/2] x86: vdso: Remove redundant ifdeffery around in_ia32_syscall() Thomas Weißschuh
2024-09-10 14:34 ` Eric W. Biederman
2024-09-10 18:10 ` Thomas Weißschuh
2025-04-22 12:47 ` [tip: x86/entry] x86/vdso: Remove redundant #ifdeffery " tip-bot2 for Thomas Weißschuh
2025-04-22 12:25 ` Ingo Molnar [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=aAeKvpzKsLsKzK8J@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=thomas.weissschuh@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