devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Thierry Reding <treding@nvidia.com>
Cc: Jon Hunter <jonathanh@nvidia.com>,
	devicetree@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: Correct GV11B GPU register sizes
Date: Thu, 10 Dec 2020 16:34:28 -0600	[thread overview]
Message-ID: <CAL_JsqLzzWAmJ-hwgxZv6utpiGnsVTWvWjgV+Gn0L8XRVFBxGQ@mail.gmail.com> (raw)
In-Reply-To: <X8+FCbks0dax2L4J@ulmo>

On Tue, Dec 8, 2020 at 7:52 AM Thierry Reding <treding@nvidia.com> wrote:
>
> On Mon, Dec 07, 2020 at 05:13:52PM -0600, Rob Herring wrote:
> > On Tue, 24 Nov 2020 12:18:42 +0000, Jon Hunter wrote:
> > > Commit 90a09178f309 ("dt-bindings: Add documentation for GV11B GPU")
> > > added the GV11B GPU device-tree bindings information but incorrectly
> > > added an additional 0 to the size of the addresses in the example.
> > >
> > > Fixes: 90a09178f309 ("dt-bindings: Add documentation for GV11B GPU")
> > > Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> > > ---
> > >  Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt | 4 ++--
> > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> >
> > Applied, thanks!
> >
> > But really, it's just an example and rather than fix trivial things in
> > txt bindings, convert them to schema please.
>
> The conversion to schema of this binding was part of a series I sent out
> earlier this year converting a bunch of Tegra-related bindings. At the
> time you had requested that rather than converting one binding after
> another it might be easier to review if whole directories were converted
> at a time.

That's largely just because the issues tend to be the same (both doing
the conversion and reviewing it).

> I've been struggling to find time to do so, so I wonder if you'd prefer
> me to send out that series again, or perhaps in smaller chunks? That
> sounds better than not doing any conversions at all because I lack the
> time to do whole directories at once.

The whole series is fine.

Rob

      reply	other threads:[~2020-12-10 23:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24 12:18 [PATCH] dt-bindings: Correct GV11B GPU register sizes Jon Hunter
2020-11-30 12:23 ` Thierry Reding
2020-12-07 23:13 ` Rob Herring
2020-12-08 13:52   ` Thierry Reding
2020-12-10 22:34     ` 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_JsqLzzWAmJ-hwgxZv6utpiGnsVTWvWjgV+Gn0L8XRVFBxGQ@mail.gmail.com \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=treding@nvidia.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).