From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, Christian Brauner <brauner@kernel.org>
Subject: [git pull][6.17] vfs.git 4/9: asm/param.h pile
Date: Sat, 26 Jul 2025 09:04:22 +0100 [thread overview]
Message-ID: <20250726080422.GC1456602@ZenIV> (raw)
In-Reply-To: <20250726080119.GA222315@ZenIV>
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-headers_param
for you to fetch changes up to 2560014ec150fd41b969ea6bcf8a985ae910eea5:
loongarch, um, xtensa: get rid of generated arch/$ARCH/include/asm/param.h (2025-06-24 22:02:05 -0400)
----------------------------------------------------------------
This series massages asm/param.h to simpler and more uniform shape.
By the end of it,
* all arch/*/include/uapi/asm/param.h are either generated includes
of <asm-generic/param.h> or a #define or two followed by such include.
* no arch/*/include/asm/param.h anywhere, generated or not.
* include <asm/param.h> resolves to arch/*/include/uapi/asm/param.h
of the architecture in question (or that of host in case of uml).
* include/asm-generic/param.h pulls uapi/asm-generic/param.h and
deals with USER_HZ, CLOCKS_PER_SEC and with HZ redefinition after that.
----------------------------------------------------------------
Al Viro (3):
xtensa: get rid uapi/asm/param.h
alpha: regularize the situation with asm/param.h
loongarch, um, xtensa: get rid of generated arch/$ARCH/include/asm/param.h
arch/alpha/include/asm/param.h | 12 ------------
arch/alpha/include/uapi/asm/param.h | 9 ++-------
arch/loongarch/include/asm/Kbuild | 1 -
arch/um/include/asm/Kbuild | 1 -
arch/xtensa/include/asm/Kbuild | 1 -
arch/xtensa/include/uapi/asm/param.h | 31 -------------------------------
include/asm-generic/param.h | 2 +-
include/uapi/asm-generic/param.h | 6 +++++-
8 files changed, 8 insertions(+), 55 deletions(-)
delete mode 100644 arch/alpha/include/asm/param.h
delete mode 100644 arch/xtensa/include/uapi/asm/param.h
next prev parent reply other threads:[~2025-07-26 8:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-26 8:01 [git pull][6.17] vfs.git 1/9: d_flags pile Al Viro
2025-07-26 8:02 ` [git pull][6.17] vfs.git 2/9: simple_recursive_removal Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:03 ` [git pull][6.17] vfs.git 3/9: rpc_pipefs Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:04 ` Al Viro [this message]
2025-07-28 23:41 ` [git pull][6.17] vfs.git 4/9: asm/param.h pile pr-tracker-bot
2025-07-26 8:05 ` [git pull][6.17] vfs.git 5/9: securityfs Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:05 ` [git pull][6.17] vfs.git 6/9: misc pile Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:08 ` [git pull][6.17] vfs.git 7/9: ceph d_name fixes Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:08 ` [git pull][6.17] vfs.git 8/9: CLASS(fd) followup Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:09 ` [git pull][6.17] vfs.git 9/9: mount pile Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-28 23:41 ` [git pull][6.17] vfs.git 1/9: d_flags pile pr-tracker-bot
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=20250726080422.GC1456602@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.