From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: virag.david003@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
phone-devel@vger.kernel.org, robh+dt@kernel.org,
~postmarketos/upstreaming@lists.sr.ht, m.szyprowski@samsung.com,
Henrik Grimler <henrik@grimler.se>,
alim.akhtar@samsung.com, krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v2 0/2] arm64: dts: add mmc aliases for Exynos devices
Date: Fri, 17 Mar 2023 13:45:36 +0100 [thread overview]
Message-ID: <167905713176.29125.2783264582338805395.b4-ty@linaro.org> (raw)
In-Reply-To: <20230315212814.15908-1-henrik@grimler.se>
On Wed, 15 Mar 2023 22:28:12 +0100, Henrik Grimler wrote:
> It is convenient to have fixed mmcblk numbering of the eMMC and sdcard
> so that assigned numbers will not change from boot-to-boot or
> depending on if storage devices are actually attached or not.
>
> Also drop mshc aliases while we are at it and instead add mmc
> capabilities to the individual device trees (right now they are added
> depending on alias index).
>
> [...]
Applied, thanks!
[1/2] arm64: dts: exynos: drop mshc aliases
https://git.kernel.org/krzk/linux/c/c04d7b263d3ff036ca124494c57011c1c274dbe6
[2/2] arm64: dts: exynos: add mmc aliases
https://git.kernel.org/krzk/linux/c/5f67124757464d632f0e5288e0ba48e3ff5531a9
Best regards,
--
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
prev parent reply other threads:[~2023-03-17 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 21:28 [PATCH v2 0/2] arm64: dts: add mmc aliases for Exynos devices Henrik Grimler
2023-03-15 21:28 ` [PATCH v2 1/2] arm64: dts: exynos: drop mshc aliases Henrik Grimler
2023-03-16 10:32 ` Marek Szyprowski
2023-03-15 21:28 ` [PATCH v2 2/2] arm64: dts: exynos: add mmc aliases Henrik Grimler
2023-03-16 10:32 ` Marek Szyprowski
2023-03-17 12:45 ` Krzysztof Kozlowski [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=167905713176.29125.2783264582338805395.b4-ty@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=henrik@grimler.se \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=virag.david003@gmail.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).