From: Julius Werner <jwerner@chromium.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Julius Werner <jwerner@chromium.org>,
Dmitry Osipenko <digetx@gmail.com>,
devicetree@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Jonathan Hunter <jonathanh@nvidia.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 17:41:16 -0800 [thread overview]
Message-ID: <CAODwPW9_cbsvU3Jf-9G6TSRUwHwu+HKCQug=eJ51tsRFo6HcPg@mail.gmail.com> (raw)
In-Reply-To: <Yhd8OoJQer86kTZ8@orome>
> > 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.
>
> Thanks for the bounce. Applied.
Sorry, I wasn't sure how this was supposed to work for interdependent
patches, I thought they would all go through the same maintainer tree.
If you do split them up please be aware of the dependency, i.e. this
patch should not be applied anywhere without patch 1 and 2 of this
series landing first.
next prev parent reply other threads:[~2022-02-25 1:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 0:34 [PATCH 0/3] Update lpddr2 revision-id binding to match lpddr3 Julius Werner
2022-02-24 0:34 ` [PATCH v3 1/3] dt-bindings: memory: lpddr2: Adjust revision ID property " Julius Werner
2022-02-24 20:24 ` Rob Herring
2022-02-25 12:35 ` Krzysztof Kozlowski
2022-02-24 0:34 ` [PATCH 2/3] memory: Update of_memory lpddr2 revision-id binding Julius Werner
2022-02-24 0:34 ` [PATCH 3/3] ARM: dts: Update jedec,lpddr2 " Julius Werner
2022-02-24 7:29 ` Krzysztof Kozlowski
2022-02-24 12:38 ` Thierry Reding
2022-02-25 1:41 ` Julius Werner [this message]
2022-02-25 7:08 ` Krzysztof Kozlowski
2022-02-25 12:37 ` [PATCH 0/3] Update lpddr2 revision-id binding to match lpddr3 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='CAODwPW9_cbsvU3Jf-9G6TSRUwHwu+HKCQug=eJ51tsRFo6HcPg@mail.gmail.com' \
--to=jwerner@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski@canonical.com \
--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;
as well as URLs for NNTP newsgroup(s).