From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: jic23@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
andy@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: mapping file for include-what-you-use tool
Date: Tue, 12 May 2026 11:00:44 +0300 [thread overview]
Message-ID: <agLeLDtXxfFHSjJj@ashevche-desk.local> (raw)
In-Reply-To: <CALoEA-x8XVqx+S9Kue7VsocO1Ca1wQS10nt=COF-pGOQ_qa_jQ@mail.gmail.com>
On Tue, May 12, 2026 at 09:36:57AM +0200, Joshua Crofts wrote:
> On Tue, 12 May 2026 at 09:35, Joshua Crofts <joshua.crofts1@gmail.com> wrote:
> >
> > As promised, I'm sending my IWYU mapping file, based on Jonathan's
> > version with a few additional tweaks by me.
> >
> > Other than adding support for more assembly file business, I've also
> > experimented with individual symbol definition (see BIT() and GENMASK()
> > in the following file) - this is to prevent issues such as the tool
> > wanting you to include <linux/bits.h> when you already have
> > <linux/bitops.h> in the source file (I agree, doing this symbol by
> > symbol is tedious, but BIT() and GENMASK() are symbols that especially
> > do this, and they're included in most, if not all drivers).
> >
> > Feel free to improve this file and pass it on. I wouldn't really fully
> > rely on IWYU as even with the mapping file the results can be weird,
> > but it definitely serves as a good starting point when doing driver
> > cleanup.
> >
> > I'm making this patch an RFC - this is not intended for merging.
>
> Annnd I forgot to add the RFC tag... Either way, the above still stands.
Thanks for sharing anyways!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-05-12 8:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 7:35 [PATCH] iio: mapping file for include-what-you-use tool Joshua Crofts
2026-05-12 7:36 ` Joshua Crofts
2026-05-12 8:00 ` Andy Shevchenko [this message]
2026-05-12 8:00 ` Andy Shevchenko
2026-05-12 8:04 ` Joshua Crofts
2026-05-12 8:07 ` Andy Shevchenko
2026-05-12 8:10 ` Joshua Crofts
2026-05-12 15:36 ` David Lechner
2026-05-12 15:51 ` Andy Shevchenko
2026-05-12 15:57 ` David Lechner
2026-05-13 8:24 ` Joshua Crofts
2026-05-12 17:07 ` Jonathan Cameron
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=agLeLDtXxfFHSjJj@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=joshua.crofts1@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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