From: Rob Herring <robh+dt@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Jon Hunter <jonathanh@nvidia.com>,
linux-tegra <linux-tegra@vger.kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: memory-controller: Update example for Tegra124 EMC
Date: Wed, 19 Feb 2020 09:04:06 -0600 [thread overview]
Message-ID: <CAL_JsqL5NzRcr6G-f0soGjb9p=+aJmU6xXEMQCLG7n0GSaxH1w@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqKJUdhjWx5z_-kedNNm4mD6oSGizqEQ57vxtGbMFySbbQ@mail.gmail.com>
On Tue, Jan 14, 2020 at 12:32 PM Rob Herring <robh+dt@kernel.org> wrote:
>
> On Tue, Jan 14, 2020 at 6:38 AM Thierry Reding <thierry.reding@gmail.com> wrote:
> >
> > From: Thierry Reding <treding@nvidia.com>
> >
> > The example in the Tegra124 EMC device tree binding looks like an old
> > version that doesn't contain all the required fields. Update it with a
> > version from the current DTS files to fix the make dt_binding_check
> > target.
> >
> > Reported-by: Rob Herring <robh+dt@kernel.org>
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> > .../nvidia,tegra124-emc.yaml | 19 +++++++++++--------
> > 1 file changed, 11 insertions(+), 8 deletions(-)
>
> Acked-by: Rob Herring <robh@kernel.org>
>
> Thanks for fixing quickly.
Or not. I assumed you were going to send this via arm-soc given that's
where the problem was, but given it still hasn't appeared anywhere and
it's in master now I'll apply it.
Rob
prev parent reply other threads:[~2020-02-19 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 12:38 [PATCH] dt-bindings: memory-controller: Update example for Tegra124 EMC Thierry Reding
2020-01-14 18:32 ` Rob Herring
2020-02-19 15:04 ` Rob Herring [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='CAL_JsqL5NzRcr6G-f0soGjb9p=+aJmU6xXEMQCLG7n0GSaxH1w@mail.gmail.com' \
--to=robh+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--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).