linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	devicetree@vger.kernel.org,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] devicetree: Expose dtbs_check and dt_binding_check some more
Date: Tue, 13 Aug 2019 15:44:39 -0700	[thread overview]
Message-ID: <20190813224440.0468920644@mail.kernel.org> (raw)
In-Reply-To: <CAL_JsqLivZNf9A2bVXKf8eqdmsywQV+KEh5dYVLywNQPfn0P=w@mail.gmail.com>

Quoting Rob Herring (2019-08-13 15:32:48)
> On Tue, Aug 13, 2019 at 12:38 PM Stephen Boyd <sboyd@kernel.org> wrote:
> >
> > It wasn't obvious that this was a command to run based on 'make help',
> > so add it to the top-level help for devicetree builds. Also, add an
> > example to the documentation to show that db_binding_check can be run
> > with DT_SCHEMA_FILES= to only check one schema file instead of all of
> > them.
> >
> > Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
> > Cc: <linux-kbuild@vger.kernel.org>
> > Cc: <devicetree@vger.kernel.org>
> > Cc: <linux-doc@vger.kernel.org>
> > Signed-off-by: Stephen Boyd <sboyd@kernel.org>
> > ---
> >
> > I didn't find this sent, so sending again!
> 
> You had. :)

Oh no, sorry! :(

> 
> >
> >  Documentation/devicetree/writing-schema.md | 1 +
> >  Makefile                                   | 6 ++++--
> >  2 files changed, 5 insertions(+), 2 deletions(-)
> 
> writing-schema.md got converted to rst, so I fixed up and applied.

Thanks!


      reply	other threads:[~2019-08-13 22:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-13 18:38 [PATCH] devicetree: Expose dtbs_check and dt_binding_check some more Stephen Boyd
2019-08-13 22:32 ` Rob Herring
2019-08-13 22:44   ` Stephen Boyd [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=20190813224440.0468920644@mail.kernel.org \
    --to=sboyd@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=yamada.masahiro@socionext.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).