From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Christopher Obbard <chris.obbard@collabora.com>,
Heiko Stuebner <heiko@sntech.de>,
linux-rockchip@lists.infradead.org
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Riesch <michael.riesch@wolfvision.net>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH v1 1/3] arm64: dts: rockchip: Update sdhci alias for rock-5a
Date: Tue, 10 Jan 2023 20:21:52 +0100 [thread overview]
Message-ID: <615a84c8-0b5a-8f3f-517b-af1feea6d005@linaro.org> (raw)
In-Reply-To: <20230110155252.189300-2-chris.obbard@collabora.com>
On 10/01/2023 16:52, Christopher Obbard wrote:
> In the previous version, the sdhci alias was set
> to mmc1: an artifact leftover from the port from
> vendor kernel. Update the alias to mmc0 to match
Please wrap
commit
message
according
to
Linux
coding style / submission process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v5.18-rc4/source/Documentation/process/submitting-patches.rst#L586
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-01-10 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 15:52 [PATCH v1 0/3] Update eMMC alias for Radxa ROCK 5 Model A and Model B DTS Christopher Obbard
2023-01-10 15:52 ` [PATCH v1 1/3] arm64: dts: rockchip: Update sdhci alias for rock-5a Christopher Obbard
2023-01-10 19:21 ` Krzysztof Kozlowski [this message]
2023-01-10 19:55 ` Christopher Obbard
2023-01-10 15:52 ` [PATCH v1 2/3] arm64: dts: rockchip: Remove empty line from rock-5a Christopher Obbard
2023-01-10 15:52 ` [PATCH v1 3/3] arm64: dts: rockchip: Update sdhci alias for rock-5b Christopher Obbard
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=615a84c8-0b5a-8f3f-517b-af1feea6d005@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=chris.obbard@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael.riesch@wolfvision.net \
--cc=robh+dt@kernel.org \
--cc=sebastian.reichel@collabora.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).