linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: devicetree@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andy Whitcroft <apw@canonical.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] checkpatch: Warn if DT bindings are not in schema format
Date: Fri, 11 Oct 2019 14:32:45 -0500	[thread overview]
Message-ID: <CAL_Jsq+YHDRkPYQwMWAvXM8kPz92AVYuaiLKAbZwhYeufFJQvw@mail.gmail.com> (raw)
In-Reply-To: <a6933fa81cf1510528ed7a4cfa55f57900800fc6.camel@perches.com>

On Fri, Oct 11, 2019 at 1:02 PM Joe Perches <joe@perches.com> wrote:
>
> On Fri, 2019-10-11 at 12:56 -0500, Rob Herring wrote:
> > On Fri, Sep 27, 2019 at 10:39 AM Rob Herring <robh@kernel.org> wrote:
> > > On Fri, Sep 27, 2019 at 9:29 AM Joe Perches <joe@perches.com> wrote:
> > > > On Fri, 2019-09-27 at 09:02 -0500, Rob Herring wrote:
> > > > > On Fri, Sep 13, 2019 at 4:48 PM Joe Perches <joe@perches.com> wrote:
> > > > > > On Fri, 2019-09-13 at 16:13 -0500, Rob Herring wrote:
> > > > > > > DT bindings are moving to using a json-schema based schema format
> > > > > > > instead of freeform text. Add a checkpatch.pl check to encourage using
> > > > > > > the schema for new bindings. It's not yet a requirement, but is
> > > > > > > progressively being required by some maintainers.
> > > > > > []
> > > > > > > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > > > > > []
> > > > > > > @@ -2822,6 +2822,14 @@ sub process {
> > > > > > >                            "added, moved or deleted file(s), does MAINTAINERS need updating?\n" . $herecurr);
> > > > > > >               }
> > > > > > >
> > > > > > > +# Check for adding new DT bindings not in schema format
> > > > > > > +             if (!$in_commit_log &&
> > > > > > > +                 ($line =~ /^new file mode\s*\d+\s*$/) &&
> > > > > > > +                 ($realfile =~ m@^Documentation/devicetree/bindings/.*\.txt$@)) {
> > > > > > > +                     WARN("DT_SCHEMA_BINDING_PATCH",
> > > > > > > +                          "DT bindings should be in DT schema format. See: Documentation/devicetree/writing-schema.rst\n");
> > > > > > > +             }
> > > > > > > +
> > > > > >
> > > > > > As this already seems to be git dependent, perhaps
> > > > >
> > > > > It's quite rare to see a non git generated diff these days.
> > > > >
> > > > > > it's easier to read with a single line test like:
> > > > > >
> > > > > >                 if ($line =~ m{^\s*create mode\s*\d+\s*Documentation/devicetree/bindings/.*\.txt$}) {
> > > > > >                         etc...
> > > > > >                 }
> > > > >
> > > > > I frequently do 'git show $commit | scripts/checkpatch.pl' and this
> > > > > doesn't work with that. I really should have a '--pretty=email' in
> > > > > there, but I just ignore the commit msg warnings. In any case, that
> > > > > still doesn't help because there's no diffstat. There's probably some
> > > > > way to turn that on or just use git-format-patch, but really we want
> > > > > this to work with any git diff.
> > > >
> > > > I don't understand your argument against what I proposed at all.
> > >
> > > It is dependent on the commit message rather than the diff itself. I
> > > want it to work with or without a diffstat.
> > >
> > > > and btw:
> > > >
> > > > $ git format-patch -1 --stdout <commit> | ./scripts/checkpatch.pl
> > >
> > > Yes, I stated this was possible. My concern is there are lots of ways
> > > to generate a diff in git. My way works for *all* of them. Yours
> > > doesn't.
> >
> > Joe, are you okay with this?
>
> Sure, Andrew Morton does most of the checkpatch upstreaming, but
> if you want to send your own pull request, I've no objection.

Thanks, I've applied this to the DT tree.

Rob

      reply	other threads:[~2019-10-11 19:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-13 21:13 [PATCH] checkpatch: Warn if DT bindings are not in schema format Rob Herring
2019-09-13 21:48 ` Joe Perches
2019-09-16 18:21   ` Rob Herring
2019-09-27 14:02   ` Rob Herring
2019-09-27 14:29     ` Joe Perches
2019-09-27 15:39       ` Rob Herring
2019-10-11 17:56         ` Rob Herring
2019-10-11 18:02           ` Joe Perches
2019-10-11 19:32             ` 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_Jsq+YHDRkPYQwMWAvXM8kPz92AVYuaiLKAbZwhYeufFJQvw@mail.gmail.com \
    --to=robh@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=devicetree@vger.kernel.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    /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).