From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Uwe Kleine-König (The Capable Hub)"
<u.kleine-koenig@baylibre.com>,
linux-kernel@vger.kernel.org, "Rob Herring" <robh@kernel.org>,
"Saravana Kannan" <saravanak@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Len Brown" <lenb@kernel.org>,
"Andi Shyti" <andi.shyti@kernel.org>,
"Mark Brown" <broonie@kernel.org>
Subject: Re: [PATCH] mod_devicetable.h: Split into per subsystem headers
Date: Tue, 23 Jun 2026 07:24:28 +0200 [thread overview]
Message-ID: <2026062300-suffix-freehand-e4e8@gregkh> (raw)
In-Reply-To: <CAHk-=wgYL0xJ=RaT+t1FR6Cw8E+VZkRKZjhw5h7m3FAqqNU8Hg@mail.gmail.com>
On Mon, Jun 22, 2026 at 02:49:01PM -0700, Linus Torvalds wrote:
> On Mon, 22 Jun 2026 at 14:07, Uwe Kleine-König (The Capable Hub)
> <u.kleine-koenig@baylibre.com> wrote:
> >
> > If there is a general agreement that this patch implements a good idea,
>
> Ack. This seems a good direction to me. Not only because of the whole
> "don't recompile unnecessarily" build optimization (eventually - when
> drivers start using the split-up headers), but simply as a "we
> shouldn't have mixed up different and unrelated drivers in the same
> header".
>
> Any objections?
None from me, I always wondered why we cramed these all into the same
file, I guess it just grew over time.
thanks,
greg k-h
next prev parent reply other threads:[~2026-06-23 5:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 21:07 [PATCH] mod_devicetable.h: Split into per subsystem headers Uwe Kleine-König (The Capable Hub)
2026-06-22 21:49 ` Linus Torvalds
2026-06-23 5:24 ` Greg Kroah-Hartman [this message]
2026-06-23 6:40 ` for next: ukleinek/linux.git:device-id-rework [Was: Re: [PATCH] mod_devicetable.h: Split into per subsystem headers] Uwe Kleine-König (The Capable Hub)
2026-06-23 11:12 ` Mark Brown
2026-06-22 22:06 ` [PATCH] mod_devicetable.h: Split into per subsystem headers Linus Torvalds
2026-06-23 14:47 ` Uwe Kleine-König (The Capable Hub)
2026-06-23 14:54 ` Linus Torvalds
2026-06-23 16:13 ` Uwe Kleine-König (The Capable Hub)
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=2026062300-suffix-freehand-e4e8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andi.shyti@kernel.org \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=saravanak@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=u.kleine-koenig@baylibre.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