mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Hans de Goede <johannes.goede@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Sudeep Holla <sudeep.holla@kernel.org>,
	Cristian Marussi <cristian.marussi@arm.com>,
	Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>,
	Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
	Frank.Li@kernel.org, arm-scmi@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, imx@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/2] module: add SCMI device table alias support
Date: Mon, 21 Sep 2026 09:28:48 +0100	[thread overview]
Message-ID: <20260921-jumping-affable-agama-023caf@sudeepholla> (raw)
In-Reply-To: <aq-xJE196Skvk2pX@monoceros>

On Sun, Sep 20, 2026 at 12:18:47PM +0200, Uwe Kleine-König wrote:
> On Sun, Sep 20, 2026 at 08:36:10AM +0100, Sudeep Holla wrote:

[...]

> > 
> > I am confused. I am asking to align with what's done in
> > Commit ad428f5811bd ("mod_devicetable.h: Split into per subsystem headers")
> > and you are disagreeing with that ?
> > 
> > I am not comfortable taking this patch unless there are other similar
> > examples that are agreed upon to break the pattern followed in the above
> > mentioned commit.
> > 
> > Uwe, please suggest.
> 
> I didn't start removing stuff from mod_devicetable.h yet, as changes
> there are expensive (regarding build dependencies). So the plan is to
> stop drivers consuming mod_devicetable.h and then drop it. (Not sure
> this is sensible as new users come in faster than I can fight them, but
> I didn't give up yet.)
> 
> So while adding new device_id structures to mod_devicetable.h is
> consistent with the existing practise, it still makes the situation
> worse, as every consumer of mod_devicetable.h then also depends on the
> new header for the new structure. That's why I think it's a good idea to
> deviate here, even if you're the first one doing so, to not worsen the
> already bad situation.
> 

It would be good if you provide your reviewed-by for mod_devicetable.h
and associated parts specifically here.

Also there is another patch under discussion [1], it would be good to have
similar suggestion there as well, so that there is less divergence in the
newly added code from now on.

> If it helps you, I can propose a patch changing modpost to not use that
> catch-(nearly)-all header and use the needed linux/device-id/*.h
> instead. I put this on my list for tomorrow.
> 

That's helpful too, but for the things that are being planned to be in
v7.4, they may not see that unless you push that as a fix.

-- 
Regards,
Sudeep


[1] https://lore.kernel.org/all/20260921053807.354802-2-aneesh.kumar@kernel.org

  reply	other threads:[~2026-09-21  8:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18  9:29 [PATCH v7 0/2] firmware: arm_scmi: fix module auto-loading Hans de Goede
2026-09-18  9:29 ` [PATCH v7 1/2] module: add SCMI device table alias support Hans de Goede
2026-09-18  9:53   ` Daniel Lezcano
2026-09-18 10:02     ` Hans de Goede
2026-09-18 10:13       ` Daniel Lezcano
2026-09-18 13:38         ` Sudeep Holla
2026-09-18 14:43           ` Rob Clark
2026-09-18 14:48           ` Daniel Lezcano
2026-09-18 20:15           ` Daniel Lezcano
2026-09-18 13:32   ` Sudeep Holla
2026-09-18 14:09     ` Hans de Goede
2026-09-18 20:39       ` Uwe Kleine-König
2026-09-20  7:36         ` Sudeep Holla
2026-09-20 10:18           ` Uwe Kleine-König
2026-09-21  8:28             ` Sudeep Holla [this message]
2026-09-21 15:19   ` Uwe Kleine-König
2026-09-18  9:29 ` [PATCH v7 2/2] firmware: arm_scmi: Always create devices for standard protocols Hans de Goede

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=20260921-jumping-affable-agama-023caf@sudeepholla \
    --to=sudeep.holla@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=andersson@kernel.org \
    --cc=arm-scmi@vger.kernel.org \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=cristian.marussi@arm.com \
    --cc=daniel.lezcano@oss.qualcomm.com \
    --cc=imx@lists.linux.dev \
    --cc=johannes.goede@oss.qualcomm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®