From: Kees Cook <keescook@chromium.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org,
Michal Wajdeczko <michal.wajdeczko@intel.com>
Subject: Re: [PATCH v1 1/1] kernel.h: Move upper_*_bits() and lower_*_bits() to wordpath.h
Date: Wed, 14 Feb 2024 10:54:47 -0800 [thread overview]
Message-ID: <202402141054.13640F7@keescook> (raw)
In-Reply-To: <Zc0CcNbpFrkkqiow@smile.fi.intel.com>
On Wed, Feb 14, 2024 at 08:12:00PM +0200, Andy Shevchenko wrote:
> On Wed, Feb 14, 2024 at 10:09:10AM -0800, Randy Dunlap wrote:
> > On 2/14/24 09:26, Andy Shevchenko wrote:
> > > The wordpart.h header is collecting APIs related to the handling
> > > parts of the word (usually in byte granularity). The upper_*_bits()
> > > and lower_*_bits() are good candidates to be moved to there.
> > >
> > > This helps to clean up header dependency hell with regard to kernel.h
> > > as the latter gathers completely unrelated stuff together and slows
> > > down compilation (especially when it's included into other header).
> > >
> > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > > ---
> > >
> > > Kees, since wordpart.h is now only in your tree, this is supposed
> > > to go there as well.
> >
> > after someone corrects the Subject (wordpath -> wordpart).
>
> Oh, indeed. Thanks for spotting this!
> Kees, should I send a v2 or you can amend when applying?
I've amended it; thanks for the catch Randy!
-Kees
>
> > Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
>
> Thanks!
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
--
Kees Cook
next prev parent reply other threads:[~2024-02-14 18:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 17:26 [PATCH v1 1/1] kernel.h: Move upper_*_bits() and lower_*_bits() to wordpath.h Andy Shevchenko
2024-02-14 18:09 ` Randy Dunlap
2024-02-14 18:12 ` Andy Shevchenko
2024-02-14 18:54 ` Kees Cook [this message]
2024-02-14 18:54 ` Kees Cook
2024-02-15 8:53 ` Max Kellermann
2024-02-15 13:50 ` Andy Shevchenko
2024-02-15 13:51 ` Andy Shevchenko
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=202402141054.13640F7@keescook \
--to=keescook@chromium.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.wajdeczko@intel.com \
--cc=rdunlap@infradead.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