[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZXFlbn8oaTAS8PaZ@infradead.org>
Date: Wed, 6 Dec 2023 22:25:50 -0800
From: Christoph Hellwig <hch@...radead.org>
To: Nick Desaulniers <ndesaulniers@...gle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, tanzirh@...gle.com,
Kees Cook <keescook@...omium.org>,
Andy Shevchenko <andy@...nel.org>,
linux-hardening@...r.kernel.org, linux-kernel@...r.kernel.org,
Nick DeSaulniers <nnn@...gle.com>, llvm@...ts.linux.dev
Subject: Re: [PATCH] lib/string: shrink lib/string.i via IWYU
On Tue, Dec 05, 2023 at 01:39:47PM -0800, Nick Desaulniers wrote:
> Hmm...how does one know that linux/bits.h is the higher-level include
> of asm/bitsperlong.h?
I think this the wrong way of thinking. In general we should always
avoid including asm/ headers unless there is no other way. No other
way is not formalized right now, but I think the answer is roughly if
no linux/ headers includes that asm header. This will probably give
a few wrong results at the moment, but it's probably worth fixing
them up.
Powered by blists - more mailing lists