linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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, sgoud@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 V4 0/7] gpio: zynq: Update on gpio-zynq driver
Date: Wed, 24 Jun 2020 12:18:08 +0200	[thread overview]
Message-ID: <CAMpxmJX1YQWEiY-Oa-UvniHJcX=sM2uCVG8q+p=3Or3ZCt_kbg@mail.gmail.com> (raw)
In-Reply-To: <1592393847-1415-1-git-send-email-srinivas.neeli@xilinx.com>

śr., 17 cze 2020 o 13:37 Srinivas Neeli <srinivas.neeli@xilinx.com> napisał(a):
>
> This patch series does the following:
> -protect direction in/out with a spinlock
> -Add binding for Versal gpio
> -Add binding for pmc gpio node
> -Add Versal support
> -Disable the irq if it is not a wakeup source
> -Add pmc gpio support
> -Remove error prints in EPROBE_DEFER
>
> ---
> Changes in V2:
> - In previous series [PATCH 1/8] already applied on "linux-next".
> - Fixed checkpatch warning for spinlock description.
> - Added description for Versal PS_GPIO and PMC_GPIO.
> Changes in V3:
> - Updated commit description for PATCH 4 and 6.
> Changes in V4:
> - Updated commit description for PATCH 2 and 3.
> ---
>
> Glenn Langedock (1):
>   gpio: zynq: protect direction in/out with a spinlock
>
> Shubhrajyoti Datta (6):
>   dt-bindings: gpio: Add binding for Versal gpio
>   devicetree-binding: Add pmc gpio node
>   gpio: zynq: Add Versal support
>   gpio: zynq: Disable the irq if it is not a wakeup source
>   gpio: zynq: Add pmc gpio support
>   gpio: zynq: Remove error prints in EPROBE_DEFER
>
>  .../devicetree/bindings/gpio/gpio-zynq.txt         |  4 +-
>  drivers/gpio/gpio-zynq.c                           | 66 +++++++++++++++++++++-
>  2 files changed, 67 insertions(+), 3 deletions(-)
>
> --
> 2.7.4
>

Series applied to for-next.

Bart

      parent reply	other threads:[~2020-06-24 10:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17 11:37 [PATCH V4 0/7] gpio: zynq: Update on gpio-zynq driver Srinivas Neeli
2020-06-17 11:37 ` [PATCH V4 1/7] gpio: zynq: protect direction in/out with a spinlock Srinivas Neeli
2020-06-17 11:37 ` [PATCH V4 2/7] dt-bindings: gpio: Add binding for Versal gpio Srinivas Neeli
2020-06-17 11:37 ` [PATCH V4 3/7] devicetree-binding: Add pmc gpio node Srinivas Neeli
2020-06-24 10:18   ` Bartosz Golaszewski
2020-06-17 11:37 ` [PATCH V4 4/7] gpio: zynq: Add Versal support Srinivas Neeli
2020-06-17 11:37 ` [PATCH V4 5/7] gpio: zynq: Disable the irq if it is not a wakeup source Srinivas Neeli
2020-06-17 11:37 ` [PATCH V4 6/7] gpio: zynq: Add pmc gpio support Srinivas Neeli
2020-06-17 11:37 ` [PATCH V4 7/7] gpio: zynq: Remove error prints in EPROBE_DEFER Srinivas Neeli
2020-06-24 10:18 ` Bartosz Golaszewski [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='CAMpxmJX1YQWEiY-Oa-UvniHJcX=sM2uCVG8q+p=3Or3ZCt_kbg@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=sgoud@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).