All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: 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 09:21:02 +0200	[thread overview]
Message-ID: <YsU33mo+8MwmgPr4@shikoro> (raw)
In-Reply-To: <20220621074238.957177-2-conor.dooley@microchip.com>

[-- Attachment #1: Type: text/plain, Size: 568 bytes --]

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?

For that case:

Acked-by: Wolfram Sang <wsa@kernel.org>


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@kernel.org>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: 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 09:21:02 +0200	[thread overview]
Message-ID: <YsU33mo+8MwmgPr4@shikoro> (raw)
In-Reply-To: <20220621074238.957177-2-conor.dooley@microchip.com>


[-- Attachment #1.1: Type: text/plain, Size: 568 bytes --]

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?

For that case:

Acked-by: Wolfram Sang <wsa@kernel.org>


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2022-07-06  7:21 UTC|newest]

Thread overview: 16+ 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 ` Conor Dooley
2022-06-21  7:42 ` [PATCH v6 2/2] MAINTAINERS: add the polarfire soc's i2c driver Conor Dooley
2022-06-21  7:42   ` Conor Dooley
2022-07-06  7:21   ` Wolfram Sang [this message]
2022-07-06  7:21     ` Wolfram Sang
2022-07-06  7:41     ` Conor.Dooley
2022-07-06  7:41       ` Conor.Dooley
2022-07-06  7:19 ` [PATCH v6 1/2] i2c: add support for microchip fpga i2c controllers Wolfram Sang
2022-07-06  7:19   ` Wolfram Sang
2022-07-06  8:03   ` Conor.Dooley
2022-07-06  8:03     ` Conor.Dooley
2022-07-06 10:32     ` Wolfram Sang
2022-07-06 10:32       ` Wolfram Sang
2022-07-06 10:50       ` Conor.Dooley
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=YsU33mo+8MwmgPr4@shikoro \
    --to=wsa@kernel.org \
    --cc=ben.dooks@codethink.co.uk \
    --cc=conor.dooley@microchip.com \
    --cc=daire.mcnamara@microchip.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.