From: <Conor.Dooley@microchip.com>
To: <wsa@kernel.org>, <linux-i2c@vger.kernel.org>,
<ben.dooks@codethink.co.uk>, <linux-kernel@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <Daire.McNamara@microchip.com>
Subject: Re: [PATCH v6 2/2] MAINTAINERS: add the polarfire soc's i2c driver
Date: Wed, 6 Jul 2022 07:41:17 +0000 [thread overview]
Message-ID: <0832f4e2-ae53-568d-91c9-2f76581d8860@microchip.com> (raw)
In-Reply-To: <YsU33mo+8MwmgPr4@shikoro>
On 06/07/2022 08:21, Wolfram Sang wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Tue, Jun 21, 2022 at 08:42:39AM +0100, Conor Dooley wrote:
>> Add the newly added i2c controller driver to the existing entry for
>> PolarFire SoC.
>>
>> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
>> ---
>> New in v6.
>> FYI: I have several maintainers updates in flight - usb, pwm, spi
>> of which some will be in 5.20 & clk/hwrng/pci that are likely to
>> go into 5.19-rcN.
>
> Then, I'd suggest you collect all of them and send them as one patch at
> the end of the next merge window?
Hmm, couple of them have actually already gone in. I doubt the pwm will
make it but the others have. If this driver is cleaned up in time for
5.20, I'll rebase this patch after the first week of the mw & resubmit
with your Ack.
Thanks.
>
> For that case:
>
> Acked-by: Wolfram Sang <wsa@kernel.org>
>
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-07-06 7:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 7:42 [PATCH v6 1/2] i2c: add support for microchip fpga i2c controllers Conor Dooley
2022-06-21 7:42 ` [PATCH v6 2/2] MAINTAINERS: add the polarfire soc's i2c driver Conor Dooley
2022-07-06 7:21 ` Wolfram Sang
2022-07-06 7:41 ` Conor.Dooley [this message]
2022-07-06 7:19 ` [PATCH v6 1/2] i2c: add support for microchip fpga i2c controllers Wolfram Sang
2022-07-06 8:03 ` Conor.Dooley
2022-07-06 10:32 ` Wolfram Sang
2022-07-06 10:50 ` Conor.Dooley
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=0832f4e2-ae53-568d-91c9-2f76581d8860@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Daire.McNamara@microchip.com \
--cc=ben.dooks@codethink.co.uk \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=wsa@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).