From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: bcm-kernel-feedback-list@broadcom.com,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Álvaro Fernández Rojas" <noltari@gmail.com>,
linux-gpio@vger.kernel.org, "Rob Herring" <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
"Linus Walleij" <linus.walleij@linaro.org>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Jonas Gorski" <jonas.gorski@gmail.com>
Subject: Re: [PATCH 1/2] dt-bindings: pinctrl: Add binding for BCM4908 pinctrl
Date: Thu, 16 Dec 2021 09:35:01 -0600 [thread overview]
Message-ID: <YbtcpbLIlUV89qEK@robh.at.kernel.org> (raw)
In-Reply-To: <20211215204753.5956-1-zajec5@gmail.com>
On Wed, 15 Dec 2021 21:47:52 +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> It's hardware block that is part of every SoC from BCM4908 family.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> .../pinctrl/brcm,bcm4908-pinctrl.yaml | 72 +++++++++++++++++++
> MAINTAINERS | 7 ++
> 2 files changed, 79 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,bcm4908-pinctrl.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2021-12-16 15:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 20:47 [PATCH 1/2] dt-bindings: pinctrl: Add binding for BCM4908 pinctrl Rafał Miłecki
2021-12-15 20:47 ` [PATCH 2/2] pinctrl: bcm: add driver for BCM4908 pinmux Rafał Miłecki
2021-12-16 6:34 ` kernel test robot
2021-12-16 14:26 ` kernel test robot
2021-12-16 19:55 ` Andy Shevchenko
2021-12-22 10:19 ` Rafał Miłecki
2021-12-22 12:12 ` Andy Shevchenko
2021-12-15 22:27 ` [PATCH 1/2] dt-bindings: pinctrl: Add binding for BCM4908 pinctrl Rob Herring
2021-12-15 22:35 ` Rafał Miłecki
2021-12-16 15:32 ` Rob Herring
2021-12-16 15:35 ` 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=YbtcpbLIlUV89qEK@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=rafal@milecki.pl \
--cc=rdunlap@infradead.org \
--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).