From: Brian Masney <bmasney@redhat.com>
To: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Jagadeesh Kona <jagadeesh.kona@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] clk: qcom: Drop inclusions of <linux/mod_devicetable.h>
Date: Thu, 16 Jul 2026 18:50:29 -0400 [thread overview]
Message-ID: <allgNY_1HwlRZPB9@redhat.com> (raw)
In-Reply-To: <alk1--PeUJ7pKbvA@monoceros>
On Thu, Jul 16, 2026 at 09:55:23PM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> On Thu, Jul 16, 2026 at 03:15:55PM -0400, Brian Masney wrote:
> > On Thu, Jul 16, 2026 at 08:21:05PM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> > > The only used symbol in these four drivers that is provided by
> > > <linux/mod_devicetable.h> is of_device_id and this is also provided by
> > > <linux/platform_device.h>.
> >
> > I don't see it defined in platform_device, unless I am missing
> > something?
> >
> > It looks like the reason this compiles is because of this chain of
> > includes:
> >
> > linux/clk-provider.h -> linux/of.h -> linux/device-id/of.h
>
> Well, the chain for <linux/platform_device.h> is:
>
> <linux/platform_device.h>
> -> <linux/device.h>
> -> <linux/device/driver.h>
> -> <linux/device-id/of.h>
>
> but the more relevant thing is: <linux/platform_device.h> makes use of
> struct of_device_id and most consumer of that header (typically platform
> drivers) need struct of_device_id. So it's very sensible that
> <linux/platform_device.h> is enough to get that definition. The include
> chain is just an implementation detail.
>
> > > So drop the unneeded include which brings us
> > > one step closer to removing <linux/mod_devicetable.h>.
> > >
> > > Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
> >
> > With an updated commit message:
> >
> > Reviewed-by: Brian Masney <bmasney@redhat.com>
>
> Does this discussion convince you that the commit log is ok as is?
Yes, agreed. Thanks for the clarification.
Brian
prev parent reply other threads:[~2026-07-16 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 18:21 [PATCH v1] clk: qcom: Drop inclusions of <linux/mod_devicetable.h> Uwe Kleine-König (The Capable Hub)
2026-07-16 19:15 ` Brian Masney
2026-07-16 19:55 ` Uwe Kleine-König (The Capable Hub)
2026-07-16 22:50 ` Brian Masney [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=allgNY_1HwlRZPB9@redhat.com \
--to=bmasney@redhat.com \
--cc=andersson@kernel.org \
--cc=jagadeesh.kona@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.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