public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@intel.com>,
	lars@metafoo.de, Michael.Hennerich@analog.com,
	gregkh@linuxfoundation.org, dlechner@baylibre.com,
	nuno.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] iio: frequency: ad9834: clean up includes
Date: Sun, 19 Apr 2026 17:59:13 +0100	[thread overview]
Message-ID: <20260419175913.16ede123@jic23-huawei> (raw)
In-Reply-To: <CALoEA-yWpZa88nTRsTCVnaNFL9w8+pq53xKY7Nh+jLgEWZYTdQ@mail.gmail.com>

On Fri, 17 Apr 2026 09:34:38 +0200
Joshua Crofts <joshua.crofts1@gmail.com> wrote:

> On Fri, 17 Apr 2026 at 09:26, Andy Shevchenko
> <andriy.shevchenko@intel.com> wrote:
> > Yes, that's why one still needs to understand more about headers in the Linux
> > kernel to do such a "simple" change.  
> 
> Yup, it's definitely a task that seems easy on the surface level (but
> isn't). Also the concept of
> kernel.h is truly a fun one.
> 
> > Oh, surprise surprise :-), thanks for pointing this out!  
> 
> No problem, surprisingly one of the things that IWYU got right.
> 
Looks fine to me.
Applied to the testing branch of iio.git

Thanks,

Jonathan

      reply	other threads:[~2026-04-19 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-16  9:32 [PATCH v3] iio: frequency: ad9834: clean up includes Joshua Crofts
2026-04-17  6:47 ` Andy Shevchenko
2026-04-17  7:13   ` Joshua Crofts
2026-04-17  7:26     ` Andy Shevchenko
2026-04-17  7:34       ` Joshua Crofts
2026-04-19 16:59         ` Jonathan Cameron [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=20260419175913.16ede123@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joshua.crofts1@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --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