linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: "Y.b. Lu" <yangbo.lu@nxp.com>, Shawn Guo <shawnguo@kernel.org>,
	Leo Li <leoyang.li@nxp.com>, Rob Herring <robh+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	Adrian Hunter <adrian.hunter@intel.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ashish Kumar <ashish.kumar@nxp.com>
Subject: Re: [PATCH] arm64: dts: ls1028a: make the eMMC and SD card controllers use fixed indices
Date: Mon, 23 Nov 2020 12:09:23 +0100	[thread overview]
Message-ID: <47517939c251b1bc2f04ee1962caddf4@walle.cc> (raw)
In-Reply-To: <20201120093015.duel3yx63cbya77w@skbuf>

Am 2020-11-20 10:30, schrieb Vladimir Oltean:
> On Fri, Nov 20, 2020 at 02:04:02AM +0000, Y.b. Lu wrote:
>> Hi Vladimir,
>> 
>> I have already upstreamed a patch for all affected layerscape boards.
>> https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git/commit/?h=imx/dt64&id=342ab37ecaf8c1b10dd3ca9a1271db29a6af0705
>> 
>> Please check whether it works for you.
> 
> Thanks, one can tell that I haven't done my due diligence of checking
> Shawn's tree first. I'll cherry-pick that patch and carry on with my
> work.
> 
> However, the fact still remains that Michael has expressed his opinion
> regarding mmcblk0 vs mmcblk1. Do you think that we could make the
> aliases a per-board option instead of per-SoC? Consider that there 
> might
> even be boards that only use SD card. It would be strange for the block
> device in that case to be called /dev/mmcblk1.

Yangbo, any news on this? I'd like to have this resorted out before it 
is
set in stone for 5.10.

-- 
-michael

  reply	other threads:[~2020-11-23 11:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 15:50 [PATCH] arm64: dts: ls1028a: make the eMMC and SD card controllers use fixed indices Vladimir Oltean
2020-11-19 16:08 ` Michael Walle
2020-11-19 16:32   ` Vladimir Oltean
2020-11-20  2:04 ` Y.b. Lu
2020-11-20  9:30   ` Vladimir Oltean
2020-11-23 11:09     ` Michael Walle [this message]
2020-11-24  7:41     ` Y.b. Lu
2020-11-24  8:03       ` Michael Walle
2020-11-24  8:47         ` Y.b. Lu
2020-11-24  8:55           ` Michael Walle
2020-11-24  9:02             ` Y.b. Lu
2020-11-24  9:08               ` Michael Walle
2020-11-24  9:22                 ` Y.b. Lu
2020-11-24  9:43                   ` Michael Walle
2020-11-24 10:22                     ` Y.b. Lu
2020-11-24 10:31               ` Vladimir Oltean
2020-11-24 11:15                 ` Y.b. Lu
2020-11-24 11:28                   ` Vladimir Oltean
2020-11-25  2:59                     ` Y.b. Lu
2020-11-25  8:25                       ` Michael Walle
2020-11-30 14:29                         ` Shawn Guo
2020-12-01  2:38                           ` Y.b. Lu

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=47517939c251b1bc2f04ee1962caddf4@walle.cc \
    --to=michael@walle.cc \
    --cc=adrian.hunter@intel.com \
    --cc=ashish.kumar@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=vladimir.oltean@nxp.com \
    --cc=yangbo.lu@nxp.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;
as well as URLs for NNTP newsgroup(s).