From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Yury Norov <yury.norov@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [PATCH v1 1/1] bitops: Move aligned_byte_mask() to wordpart.h
Date: Tue, 7 May 2024 22:35:37 +0300 [thread overview]
Message-ID: <ZjqCiXADLDSfP2U9@smile.fi.intel.com> (raw)
In-Reply-To: <Zjp9sm8s50rb9N/+@yury-ThinkPad>
On Tue, May 07, 2024 at 12:14:58PM -0700, Yury Norov wrote:
> On Tue, May 07, 2024 at 05:01:54PM +0300, Andy Shevchenko wrote:
> > The bitops.h is for bit related operations. The aligned_byte_mask()
> > is about byte (or part of the machine word) operations, for which
> > we have a separate header, move the mentioned macro to wordpart.h
> > to consolidate similar operations.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> Hi Andy,
>
> I see the macro is used in lib/strnlen_user.c and in lib/usercopy.c.
> In case of strnlen_user, the wordpart.h is included via linux/kernel.h,
> which is OK to me. But In case of usercopy.c, I can't find how the
> header is included.
>
> I'm sure there is some inclusion path, but it's always better to have
> the dependencies listed explicitly.
>
> Can you please send a 2nd version with the lib/usercopy.c including
> wordpart.h?
I think it's unrelated right now. The inclusions in usercopy is a mess.
It should be cleaned up in a separate patch for all inclusions.
But okay, making slightly more mess there won't harm :-)
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-05-07 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 14:01 [PATCH v1 1/1] bitops: Move aligned_byte_mask() to wordpart.h Andy Shevchenko
2024-05-07 19:14 ` Yury Norov
2024-05-07 19:35 ` 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=ZjqCiXADLDSfP2U9@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=yury.norov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox