mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>, "Crt Mori" <cmo@melexis.com>,
	"Puranjay Mohan" <puranjay@kernel.org>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 03/11] iio: temperature: ltc2983: make headers conform to IWYU
Date: Sun, 30 Aug 2026 00:48:07 +0100	[thread overview]
Message-ID: <20260830004807.64a68777@jic23-huawei> (raw)
In-Reply-To: <CALoEA-yLuDJFfL4MszuY5GAdOL5ZyLK12ZLXE=-tQbtQswhoOQ@mail.gmail.com>

On Sat, 29 Aug 2026 22:24:47 +0200
Joshua Crofts <joshua.crofts1@gmail.com> wrote:

> On Sat, 29 Aug 2026 at 19:57, Jonathan Cameron <jic23@kernel.org> wrote:
> >  
> > > Remove the catch-all kernel.h header and add the missing headers to
> > > enforce IWYU.  
> >
> > Sashiko correctly observed that this wasn't really IWYU.  So, to avoid
> > confusion we should be referring to something "approximate IWYU taking into
> > account some headers that always include others".  
> 
> On another note - since we paste Sashiko outputs regularly into patch reviews,
> isn't it time to send a pull request to the Sashiko repo to Cc
> linux-iio on reviews?
> I remember the last email thread discussing this died out unfortunately :(
Let's pick up on that original thread again rather than buried in here.

There were some valid concerns and there is work more generally going on
to solve the new contributor information gap.

Jonathan

> 
> --
> Kind regards,
> Joshua Crofts
> 


  reply	other threads:[~2026-08-29 23:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-29 16:25 [PATCH v2 00/11] iio: temperature: " Joshua Crofts
2026-08-29 16:25 ` [PATCH v2 01/11] iio: temperature: iqs620at-temp: " Joshua Crofts
2026-08-29 16:25 ` [PATCH v2 02/11] iio: temperature: ltc2983: reorder headers Joshua Crofts
2026-08-29 16:26 ` [PATCH v2 03/11] iio: temperature: ltc2983: make headers conform to IWYU Joshua Crofts
2026-08-29 17:57   ` Jonathan Cameron
2026-08-29 20:24     ` Joshua Crofts
2026-08-29 23:48       ` Jonathan Cameron [this message]
2026-08-29 16:26 ` [PATCH v2 04/11] iio: temperature: mlx90632: " Joshua Crofts
2026-08-29 16:26 ` [PATCH v2 05/11] iio: temperature: mlx90635: " Joshua Crofts
2026-08-29 16:26 ` [PATCH v2 06/11] iio: temperature: tmp117: sort headers alphabetically Joshua Crofts
2026-08-29 16:26 ` [PATCH v2 07/11] iio: temperature: tmp117: make headers conform to IWYU Joshua Crofts
2026-08-29 16:26 ` [PATCH v2 08/11] iio: temperature: tsys01: reorder headers Joshua Crofts
2026-08-29 16:26 ` [PATCH v2 09/11] iio: temperature: tsys01: make headers conform to IWYU Joshua Crofts
2026-08-29 17:57   ` Jonathan Cameron
2026-08-29 18:09     ` Joshua Crofts
2026-08-29 16:26 ` [PATCH v2 10/11] iio: temperature: tsys02d: reorder headers Joshua Crofts
2026-08-29 16:26 ` [PATCH v2 11/11] iio: temperature: tsys02d: make headers conform to IWYU Joshua Crofts
2026-08-29 16:36   ` Joshua Crofts

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=20260830004807.64a68777@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=cmo@melexis.com \
    --cc=dlechner@baylibre.com \
    --cc=joshua.crofts1@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=puranjay@kernel.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

all inboxes | Powered by JetHome®