From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Srinivas Neeli <srinivas.neeli@xilinx.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Michal Simek <michal.simek@xilinx.com>,
shubhrajyoti.datta@xilinx.com,
linux-gpio <linux-gpio@vger.kernel.org>,
arm-soc <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
git@xilinx.com
Subject: Re: [PATCH V3 3/7] devicetree-binding: Add pmc gpio node
Date: Thu, 20 Feb 2020 11:26:36 +0100 [thread overview]
Message-ID: <CAMpxmJWshBbSxL1FrOrb=Rq2bRvvijoaLn5xq5HxA01k0qX7BA@mail.gmail.com> (raw)
In-Reply-To: <1581942793-19468-4-git-send-email-srinivas.neeli@xilinx.com>
pon., 17 lut 2020 o 13:33 Srinivas Neeli <srinivas.neeli@xilinx.com> napisał(a):
>
> From: Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>
>
> Add the pmc gpio node to the device tree.
>
Same here: I don't know what pmc gpio node is nor do I need to. Please
make your commit messages more verbose.
Bartosz
next prev parent reply other threads:[~2020-02-20 10:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 12:33 [PATCH V3 0/7] gpio: zynq: Update on gpio-zynq driver Srinivas Neeli
2020-02-17 12:33 ` [PATCH V3 1/7] gpio: zynq: protect direction in/out with a spinlock Srinivas Neeli
2020-02-17 12:33 ` [PATCH V3 2/7] dt-bindings: gpio: Add binding for Versal gpio Srinivas Neeli
2020-02-20 10:25 ` Bartosz Golaszewski
2020-02-17 12:33 ` [PATCH V3 3/7] devicetree-binding: Add pmc gpio node Srinivas Neeli
2020-02-20 10:26 ` Bartosz Golaszewski [this message]
2020-02-17 12:33 ` [PATCH V3 4/7] gpio: zynq: Add Versal support Srinivas Neeli
2020-02-17 12:33 ` [PATCH V3 5/7] gpio: zynq: Disable the irq if it is not a wakeup source Srinivas Neeli
2020-02-17 12:33 ` [PATCH V3 6/7] gpio: zynq: Add pmc gpio support Srinivas Neeli
2020-02-17 12:33 ` [PATCH V3 7/7] gpio: zynq: Remove error prints in EPROBE_DEFER Srinivas Neeli
2020-02-20 10:28 ` [PATCH V3 0/7] gpio: zynq: Update on gpio-zynq driver Bartosz Golaszewski
2020-02-21 13:45 ` 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='CAMpxmJWshBbSxL1FrOrb=Rq2bRvvijoaLn5xq5HxA01k0qX7BA@mail.gmail.com' \
--to=bgolaszewski@baylibre.com \
--cc=git@xilinx.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=shubhrajyoti.datta@xilinx.com \
--cc=srinivas.neeli@xilinx.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).