From: Marc Zyngier <maz@kernel.org>
To: lewis.hanly@microchip.com
Cc: linux-gpio@vger.kernel.org, linux-riscv@lists.infradead.org,
linus.walleij@linaro.org, brgl@bgdev.pl,
linux-kernel@vger.kernel.org, palmer@dabbelt.com,
conor.dooley@microchip.com, daire.mcnamara@microchip.com
Subject: Re: [PATCH v6 0/1] Add Polarfire SoC GPIO support
Date: Mon, 15 Aug 2022 13:16:19 +0100 [thread overview]
Message-ID: <727f07f843a9d06d84c1c28c3b905a4c@kernel.org> (raw)
In-Reply-To: <20220815120834.1562544-1-lewis.hanly@microchip.com>
On 2022-08-15 13:08, lewis.hanly@microchip.com wrote:
> From: Lewis Hanly <lewis.hanly@microchip.com>
>
>
> Add a driver to support the Polarfire SoC gpio controller.
> Tested with latest 5.19 kernel.
>
> MPFS gpio interrupts are connected to IOMUX configured by system
> register GPIO_INTERRUPT_FAB_CR(31:0). Interrupt connection for
> some GPIO's to the PLIC (Platform Level Interrupt Controller) can be
> shared (not directly connected) or direct if connection is available.
>
> previously upstreamed dt-bindings: gpio: microchip,mpfs-gpio.yaml
>
> Changes in v6
> Fixed typo causing compile issue with kernel 6.0-rc1
3 versions in just over 5 hours. How about taking a step back
and *wait* for people to review this code? It isn't like this
is going to be merged tomorrow anyway...
The expected rate for new versions of a patch is about once
a week (see Documentation/process/submitting-patches.rst).
M.
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2022-08-15 12:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 12:08 [PATCH v6 0/1] Add Polarfire SoC GPIO support lewis.hanly
2022-08-15 12:08 ` [PATCH v6 1/1] gpio: mpfs: add polarfire soc gpio support lewis.hanly
2022-08-15 16:18 ` Conor.Dooley
2022-08-22 11:28 ` Linus Walleij
2022-08-30 4:50 ` Lewis.Hanly
2022-08-31 13:19 ` Linus Walleij
2022-09-05 10:45 ` Lewis.Hanly
2022-09-06 13:09 ` Linus Walleij
2022-08-31 21:04 ` Andy Shevchenko
2022-09-05 10:46 ` Lewis.Hanly
2022-08-15 12:16 ` Marc Zyngier [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=727f07f843a9d06d84c1c28c3b905a4c@kernel.org \
--to=maz@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=lewis.hanly@microchip.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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).