From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Johannes Berg <johannes@sipsolutions.net>,
Thomas Gleixner <tglx@linutronix.de>,
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>
Cc: linux-um@lists.infradead.org, linux-kernel@vger.kernel.org,
"Thomas Weißschuh" <linux@weissschuh.net>
Subject: [PATCH 0/4] x86/um/vdso: Cleanups
Date: Mon, 13 Oct 2025 12:40:17 +0200 [thread overview]
Message-ID: <20251013-uml-vdso-cleanup-v1-0-a079c7adcc69@weissschuh.net> (raw)
Various cleanups I stumbled up while looking at the UML vDSO.
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
---
Thomas Weißschuh (4):
x86/um/vdso: Fix prototype of clock_gettime()
x86/um/vdso: Use prototypes from generic vDSO headers
x86/um/vdso: Panic when vDSO can not be allocated
x86/um/vdso: Drop VDSO64-y from Makefile
arch/x86/um/vdso/Makefile | 7 ++-----
arch/x86/um/vdso/um_vdso.c | 8 +++-----
arch/x86/um/vdso/vma.c | 12 +-----------
3 files changed, 6 insertions(+), 21 deletions(-)
---
base-commit: 3a8660878839faadb4f1a6dd72c3179c1df56787
change-id: 20250930-uml-vdso-cleanup-001f600ffcff
Best regards,
--
Thomas Weißschuh <linux@weissschuh.net>
next reply other threads:[~2025-10-13 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 10:40 Thomas Weißschuh [this message]
2025-10-13 10:40 ` [PATCH 1/4] x86/um/vdso: Fix prototype of clock_gettime() Thomas Weißschuh
2025-10-13 10:40 ` [PATCH 2/4] x86/um/vdso: Use prototypes from generic vDSO headers Thomas Weißschuh
2025-10-13 10:40 ` [PATCH 3/4] x86/um/vdso: Panic when vDSO can not be allocated Thomas Weißschuh
2025-10-13 10:40 ` [PATCH 4/4] x86/um/vdso: Drop VDSO64-y from Makefile Thomas Weißschuh
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=20251013-uml-vdso-cleanup-v1-0-a079c7adcc69@weissschuh.net \
--to=linux@weissschuh.net \
--cc=anton.ivanov@cambridgegreys.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=mingo@redhat.com \
--cc=richard@nod.at \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).