From: Al Viro <viro@zeniv.linux.org.uk>
To: linux-arch@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-parisc@vger.kernel.org, Vineet Gupta <vgupta@kernel.org>
Subject: Re: [RFC][PATCHES] asm/unaligned.h removal
Date: Tue, 1 Oct 2024 21:34:49 +0100 [thread overview]
Message-ID: <20241001203449.GA4138323@ZenIV> (raw)
In-Reply-To: <20241001195107.GA4017910@ZenIV>
On Tue, Oct 01, 2024 at 08:51:07PM +0100, Al Viro wrote:
> There are only two instances of asm/unaligned.h in the tree -
> arc and parisc. Everything else picks it from asm-generic/unaligned.h
> and if not these two, we could just move asm-generic/unaligned.h into
> include/linux/unaligned.h and do a tree-wide search-and-replace that
> would kill the largest class of asm/*.h includes in the entire kernel.
Second largest, actually - asm/io.h has more users (1035 vs. 825).
Top twelve by number of includes:
1035 asm/io.h
825 asm/unaligned.h
767 asm/page.h
490 asm/processor.h
482 asm/irq.h
475 asm/cacheflush.h
423 asm/ptrace.h
402 asm/setup.h
287 asm/tlbflush.h
284 asm/sections.h
237 asm/mmu_context.h
205 asm/smp.h
Still, asm/io.h has a lot more reasons to be heavily arch-dependent...
next prev parent reply other threads:[~2024-10-01 20:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 19:51 [RFC][PATCHES] asm/unaligned.h removal Al Viro
2024-10-01 19:51 ` [PATCH 1/3] parisc: get rid of private asm/unaligned.h Al Viro
2024-10-02 0:57 ` Helge Deller
2024-10-02 3:23 ` Al Viro
2024-10-02 8:10 ` Rolf Eike Beer
2024-10-01 19:53 ` [PATCH 2/3] arc: " Al Viro
2024-10-02 21:03 ` Vineet Gupta
2024-10-02 21:24 ` Al Viro
2024-10-01 19:54 ` [PATCH 3/3] move asm/unaligned.h to linux/unaligned.h Al Viro
2024-10-01 20:34 ` Al Viro [this message]
2024-10-02 18:33 ` [RFC][PATCHES] asm/unaligned.h removal Linus Torvalds
2024-10-02 22:17 ` Al Viro
2024-10-02 23:36 ` [git pull] " Al Viro
2024-10-03 0:04 ` 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=20241001203449.GA4138323@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-arch@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vgupta@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