From: Rob Herring <robh@kernel.org>
To: David Mosberger-Tang <davidm@egauge.net>
Cc: Ajay Singh <ajay.kathat@microchip.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, Kalle Valo <kvalo@codeaurora.org>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
Claudiu Beznea <claudiu.beznea@microchip.com>,
"David S. Miller" <davem@davemloft.net>,
Adham Abozaeid <adham.abozaeid@microchip.com>
Subject: Re: [PATCH v6 2/2] wilc1000: Document enable-gpios and reset-gpios properties
Date: Tue, 21 Dec 2021 11:12:50 -0400 [thread overview]
Message-ID: <YcHu8qkzguAPZcKx@robh.at.kernel.org> (raw)
In-Reply-To: <20211220180334.3990693-3-davidm@egauge.net>
On Mon, 20 Dec 2021 18:03:38 +0000, David Mosberger-Tang wrote:
> Add documentation for the ENABLE and RESET GPIOs that may be needed by
> wilc1000-spi.
>
> Signed-off-by: David Mosberger-Tang <davidm@egauge.net>
> ---
> .../net/wireless/microchip,wilc1000.yaml | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.
If a tag was not added on purpose, please state why and what changed.
next prev parent reply other threads:[~2021-12-21 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 18:03 [PATCH v6 0/2] wilc1000: Add reset/enable GPIO support to SPI driver David Mosberger-Tang
2021-12-20 18:03 ` [PATCH v6 2/2] wilc1000: Document enable-gpios and reset-gpios properties David Mosberger-Tang
2021-12-21 15:12 ` Rob Herring [this message]
2021-12-21 16:06 ` David Mosberger-Tang
2021-12-21 16:28 ` Kalle Valo
2021-12-20 18:03 ` [PATCH v6 1/2] wilc1000: Add reset/enable GPIO support to SPI driver David Mosberger-Tang
2021-12-21 18:11 ` Kalle Valo
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=YcHu8qkzguAPZcKx@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=adham.abozaeid@microchip.com \
--cc=ajay.kathat@microchip.com \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=davidm@egauge.net \
--cc=devicetree@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@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).