From: Lee Jones <lee@kernel.org>
To: Matthias Brugger <mbrugger@suse.com>
Cc: matthias.bgg@kernel.org, robh+dt@kernel.org,
angelogioacchino.delregno@collabora.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org,
krzysztof.kozlowski+dt@linaro.org, matthias.bgg@gmail.com,
mandyjh.liu@mediatek.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] dt-bindings: mfd: Rename mediatek,mt8195-scpsys.yaml
Date: Tue, 20 Sep 2022 10:10:55 +0100 [thread overview]
Message-ID: <YymDn+ZEIFUqpIEb@google.com> (raw)
In-Reply-To: <336cb80f-8f58-92ba-aa92-1bb57a75f0fb@suse.com>
On Tue, 13 Sep 2022, Matthias Brugger wrote:
> On 08/09/2022 12:37, Lee Jones wrote:
> > On Tue, 30 Aug 2022, matthias.bgg@kernel.org wrote:
> >
> > > From: Matthias Brugger <mbrugger@suse.com>
> > >
> > > The file describes the scpsys node for all SoCs and not only the mt8195.
> > > Rename it to reflect this fact.
> >
> > Actually, this is fairly typical. Same with actual drivers.
> >
> > Both tend to adopt the name of the module first supported.
> >
>
> Well I think that's unfortunate as it can create confusion for people
> searching for the binding as well as people adding a new compatible as they
> might think each SoC should have a independent yaml file. For that I reason
> I think it makes sense to fix the naming.
I'm not keen to open those flood-gates right now, sorry.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2022-09-20 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 9:11 [PATCH v2] dt-bindings: mfd: Rename mediatek,mt8195-scpsys.yaml matthias.bgg
2022-09-06 16:41 ` Rob Herring
2022-09-08 10:37 ` Lee Jones
2022-09-13 11:51 ` Matthias Brugger
2022-09-20 9:10 ` Lee Jones [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=YymDn+ZEIFUqpIEb@google.com \
--to=lee@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mandyjh.liu@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=matthias.bgg@kernel.org \
--cc=mbrugger@suse.com \
--cc=robh+dt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).