From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Max Kellermann <max.kellermann@ionos.com>
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.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: Thu, 15 Feb 2024 15:51:39 +0200 [thread overview]
Message-ID: <Zc4W66VdxC2udn64@smile.fi.intel.com> (raw)
In-Reply-To: <Zc4Wu4dAJTXcGGVs@smile.fi.intel.com>
On Thu, Feb 15, 2024 at 03:50:51PM +0200, Andy Shevchenko wrote:
> On Thu, Feb 15, 2024 at 09:53:48AM +0100, Max Kellermann wrote:
> > On Thu, Feb 15, 2024 at 9:49 AM Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> 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.
> >
> > Sigh. This was actually a copy of my patch which I submitted a week
> > before yours. https://lore.kernel.org/lkml/20240209164027.2582906-34-max.kellermann@ionos.com/
>
> But it was not standalone and the series has issues AFAICS.
> Nevertheless, I like it!
>
> In any case the wordpart.h is only in Kees' tree, hence can't be applied
> separately right now, so if you continue with a series it's technically can't
> be applied before v6.9-rc1.
Btw, you need to look to the patches by Ingo, you are repeating some of them.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-02-15 13:51 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
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 [this message]
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=Zc4W66VdxC2udn64@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max.kellermann@ionos.com \
--cc=michal.wajdeczko@intel.com \
/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.