From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Julius Werner <jwerner@chromium.org>
Cc: Dmitry Osipenko <digetx@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Hunter <jonathanh@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
linux-tegra <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 3/3] ARM: dts: Update jedec,lpddr2 revision-id binding
Date: Thu, 24 Feb 2022 08:29:27 +0100 [thread overview]
Message-ID: <ec0c90b9-58a9-669f-fe4a-73e60df335d5@canonical.com> (raw)
In-Reply-To: <20220224003421.3440124-4-jwerner@chromium.org>
On 24/02/2022 01:34, Julius Werner wrote:
> This patch updates the tegra20-asus-tf101 device tree to replace the
> deprecated `revision-id1` binding with the new `revision-id` binding in
> its "jedec,lpddr2"-compatible node. This was the only DTS in the tree
> using this binding.
>
> The revision-id2 (mode register 7) of this memory chip was not given in
> the existing device tree, so let's assume 0 for now until it becomes
> relevant.
>
> Signed-off-by: Julius Werner <jwerner@chromium.org>
> ---
> arch/arm/boot/dts/tegra20-asus-tf101.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Please use scripts/get_maintainer.pl to get the list of people/lists to
CC. You skipped here Tegra maintainers, so no one would pick up this patch.
I bounced the mail to Jonathan, Thierry and linux-tegra (+Cc), so
hopefully they will get it. If not, series might need resend with proper
addresses.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-02-24 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220224003421.3440124-1-jwerner@chromium.org>
2022-02-24 0:34 ` [PATCH 3/3] ARM: dts: Update jedec,lpddr2 revision-id binding Julius Werner
2022-02-24 7:29 ` Krzysztof Kozlowski [this message]
2022-02-24 12:38 ` Thierry Reding
2022-02-25 1:41 ` Julius Werner
2022-02-25 7:08 ` Krzysztof Kozlowski
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=ec0c90b9-58a9-669f-fe4a-73e60df335d5@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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