LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Chen-Yu Tsai <wenst@chromium.org> To: Hsin-Yi Wang <hsinyi@chromium.org> Cc: Matthias Brugger <matthias.bgg@gmail.com>, Rob Herring <robh+dt@kernel.org>, Enric Balletbo Serra <eballetbo@gmail.com>, Eizan Miyamoto <eizan@chromium.org>, Devicetree List <devicetree@vger.kernel.org>, "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" <linux-arm-kernel@lists.infradead.org>, "moderated list:ARM/Mediatek SoC support" <linux-mediatek@lists.infradead.org>, LKML <linux-kernel@vger.kernel.org> Subject: Re: [PATCH 2/2] arm64: dts: mt8173: elm: Use aliases to mmc nodes Date: Wed, 28 Jul 2021 11:51:34 +0800 [thread overview] Message-ID: <CAGXv+5Hua63GZ839kQEscAXBeKPYTv_63E2pYNBw4jXz1B_PWA@mail.gmail.com> (raw) In-Reply-To: <20210727112208.2508675-2-hsinyi@chromium.org> Hi, The subject for this patch wasn't tagged with v3. This might cause some issues with scripted tooling. On Tue, Jul 27, 2021 at 7:22 PM Hsin-Yi Wang <hsinyi@chromium.org> wrote: > > fa2d0aa96941 ("mmc: core: Allow setting slot index via device tree alias") > allows the use of aliases to number SD/MMC slots. This patch use aliases > to mmc nodes so the partition name for eMMC and SD card will be consistent > across boots. Device trees are supposed to be a description of the hardware and therefore should be implementation agnostic. The commit logs should be the same, unless the implementation details influenced the changes made. The MMC binding change already specified that aliases provide a way to assign fixed mmcN indices, so the log should reference the binding change commit instead. ChenYu > Signed-off-by: Hsin-Yi Wang <hsinyi@chromium.org> > Reviewed-by: Chen-Yu Tsai <wenst@chromium.org> > --- > v2->v3: add more commit message. > --- > arch/arm64/boot/dts/mediatek/mt8173-elm.dtsi | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/arch/arm64/boot/dts/mediatek/mt8173-elm.dtsi b/arch/arm64/boot/dts/mediatek/mt8173-elm.dtsi > index 21452c51a20a8..d5a2cad39c9c7 100644 > --- a/arch/arm64/boot/dts/mediatek/mt8173-elm.dtsi > +++ b/arch/arm64/boot/dts/mediatek/mt8173-elm.dtsi > @@ -10,6 +10,12 @@ > #include "mt8173.dtsi" > > / { > + aliases { > + mmc0 = &mmc0; > + mmc1 = &mmc1; > + mmc2 = &mmc3; > + }; > + > memory@40000000 { > device_type = "memory"; > reg = <0 0x40000000 0 0x80000000>; > -- > 2.32.0.432.gabb21c7263-goog > > > _______________________________________________ > Linux-mediatek mailing list > Linux-mediatek@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-mediatek
prev parent reply other threads:[~2021-07-28 3:51 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-27 11:22 [PATCH v3 1/2] arm64: dts: mt8183: kukui: Use aliases to mmc nodes Hsin-Yi Wang 2021-07-27 11:22 ` [PATCH 2/2] arm64: dts: mt8173: elm: " Hsin-Yi Wang 2021-07-28 3:51 ` Chen-Yu Tsai [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=CAGXv+5Hua63GZ839kQEscAXBeKPYTv_63E2pYNBw4jXz1B_PWA@mail.gmail.com \ --to=wenst@chromium.org \ --cc=devicetree@vger.kernel.org \ --cc=eballetbo@gmail.com \ --cc=eizan@chromium.org \ --cc=hsinyi@chromium.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mediatek@lists.infradead.org \ --cc=matthias.bgg@gmail.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: linkBe 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).