public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Joshua Crofts <joshua.crofts1@gmail.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 v6 1/2] iio: frequency: ad9832: remove kernel.h proxy header
Date: Sun, 19 Apr 2026 17:53:55 +0100	[thread overview]
Message-ID: <20260419175355.0b915e8c@jic23-huawei> (raw)
In-Reply-To: <aeJyzXXX-2zOgU3A@ashevche-desk.local>

On Fri, 17 Apr 2026 20:50:05 +0300
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:

> On Fri, Apr 17, 2026 at 10:16:22AM +0000, Joshua Crofts wrote:
> > Remove kernel.h proxy header and add replacement headers (array_size,
> > dev_printk.h, kstrtox, mod_devicetable, mutex, types, asm/byteorder) to  
> 
> I guess it's better to add .h to all of them.
> No need to resend for that. Perhaps Jonathan tweaks it.
> 
> > maintain atomicity. Moved asm/div64.h header below generic <linux/*>
> > headers. Additionally, add bitops.h for BIT_ULL() macro.
> > 
> > Audited using the include-what-you-use tool.  
> 
Tidied up. The Sashiko stuff disagreed a bit with one or two choices, but
nothing that I think warrants a change to this.

So applied this patch

Thanks,

Jonathan



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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17 10:16 [PATCH v6 0/2] iio: frequency: ad9832: cleanups Joshua Crofts
2026-04-17 10:16 ` [PATCH v6 1/2] iio: frequency: ad9832: remove kernel.h proxy header Joshua Crofts
2026-04-17 17:50   ` Andy Shevchenko
2026-04-19 16:53     ` Jonathan Cameron [this message]
2026-04-17 10:16 ` [PATCH v6 2/2] iio: frequency: ad9832: simplify bitwise math Joshua Crofts
2026-04-19 16:52   ` Jonathan Cameron
2026-04-19 17:19     ` 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=20260419175355.0b915e8c@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