From: Linus Walleij <linus.walleij@linaro.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Rob Herring" <robh+dt@kernel.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH 2/2] dt-bindings: pinctrl: use pinctrl.yaml
Date: Thu, 2 Dec 2021 03:01:58 +0100 [thread overview]
Message-ID: <CACRpkdby+9qwGJ4LqwMw0tQZHSDCBRVtH+FXOYW1ob5tii3pOw@mail.gmail.com> (raw)
In-Reply-To: <20211110165720.30242-2-zajec5@gmail.com>
On Wed, Nov 10, 2021 at 5:57 PM Rafał Miłecki <zajec5@gmail.com> wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> Also fix some examples to avoid warnings like:
> brcm,ns-pinmux.example.dt.yaml: pin-controller@1800c1c0: $nodename:0: 'pin-controller@1800c1c0' does not match '^pinctrl|pinmux@[0-9a-f]+$'
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Unfortunately I have some changes in my tree colliding with this.
This is the development branch for v5.17:
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/log/?h=devel
Do you think you could rebase on this and resend?
I would normally try to do it myself, but I have very little time these days.
Yours,
Linus Walleij
next prev parent reply other threads:[~2021-12-02 2:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 16:57 [PATCH 1/2] dt-bindings: pinctrl: convert controller description to the json-schema Rafał Miłecki
2021-11-10 16:57 ` [PATCH 2/2] dt-bindings: pinctrl: use pinctrl.yaml Rafał Miłecki
2021-11-21 22:58 ` Linus Walleij
2021-11-29 20:49 ` Rob Herring
2021-12-02 2:01 ` Linus Walleij [this message]
2021-11-21 22:56 ` [PATCH 1/2] dt-bindings: pinctrl: convert controller description to the json-schema Linus Walleij
2021-11-29 20:45 ` Rob Herring
2021-12-02 2:00 ` Linus Walleij
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=CACRpkdby+9qwGJ4LqwMw0tQZHSDCBRVtH+FXOYW1ob5tii3pOw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=zajec5@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).