linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Conor Dooley <Conor.Dooley@microchip.com>
Cc: "Palmer Dabbelt" <palmer@rivosinc.com>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Arnd Bergmann" <arnd@arndb.de>,
	Cyril.Jean@microchip.com,
	"Daire McNamara" <Daire.McNamara@microchip.com>,
	"Lewis Hanly" <Lewis.Hanly@microchip.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	gregkh <gregkh@linuxfoundation.org>,
	"Herbert Xu" <herbert@gondor.apana.org.au>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	linux-clk <linux-clk@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	linux-pci <linux-pci@vger.kernel.org>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Paul Walmsley" <paul.walmsley@sifive.com>,
	"Rob Herring" <robh@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Stephen Boyd" <sboyd@kernel.org>,
	"Wolfram Sang" <wsa@kernel.org>
Subject: Re: [RESEND PATCH v4] MAINTAINERS: add polarfire rng, pci and clock drivers
Date: Thu, 7 Jul 2022 15:37:40 +0200	[thread overview]
Message-ID: <CAK8P3a04WLx4Me_=hm9v+Kpq31i3ZCDfPiDhT64RyE_pZZPDVg@mail.gmail.com> (raw)
In-Reply-To: <a39bad24-d2bb-ef3e-d57a-2ac4fa1156ef@microchip.com>

On Thu, Jul 7, 2022 at 3:30 PM <Conor.Dooley@microchip.com> wrote:
>
> On 22/06/2022 23:58, Conor Dooley wrote:
> > From: Conor Dooley <conor.dooley@microchip.com>
> >
> > Hardware random, PCI and clock drivers for the PolarFire SoC have been
> > upstreamed but are not covered by the MAINTAINERS entry, so add them.
> > Daire is the author of the clock & PCI drivers, so add him as a
> > maintainer in place of Lewis.
> >
> > Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> > Acked-by: Stephen Boyd <sboyd@kernel.org>
> > Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
>
> Arnd, Palmer:
> Does the SoC tree make more sense for this patch?
> I am missing an ack from Herbert (but I don't think that's blocking
> for a MAINTAINERS update to my own entry?).
>
> If SoC is the better option, should I resend this to soc@kernel.org?
> Unfortunately, since I originally sent this patch there have been
> other changes to this entry that will conflict in -next (all are
> additions so easily resolved...).
>
> I was hoping to get this patch applied to v5.19-rc(foo) since we
> never added maintainers entries for these drivers rather than wait
> for v5.20.
>
> If you (plural) would rather wait for v5.20, I can resubmit this patch
> after v5.20-mw1 with an additional i2c entry (if the driver is applied)
> that already has an ack from Wolfram.

I tend to take MAINTAINERS updates as bugfixes in the soc tre
(for 5.19), and I can pick it up if you send it to soc@kernel.org.

There should never be a need to wait for the merge window
with these updates, it's either a bugfix (for 5.19) or for the current
-next cycle (5.20).

       Arnd

  reply	other threads:[~2022-07-07 14:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 22:58 [RESEND PATCH v4] MAINTAINERS: add polarfire rng, pci and clock drivers Conor Dooley
2022-07-07 13:30 ` Conor.Dooley
2022-07-07 13:37   ` Arnd Bergmann [this message]
2022-07-07 14:07     ` Conor.Dooley
2022-07-08  5:14   ` Herbert Xu

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='CAK8P3a04WLx4Me_=hm9v+Kpq31i3ZCDfPiDhT64RyE_pZZPDVg@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=Conor.Dooley@microchip.com \
    --cc=Cyril.Jean@microchip.com \
    --cc=Daire.McNamara@microchip.com \
    --cc=Lewis.Hanly@microchip.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=bhelgaas@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kw@linux.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=palmer@dabbelt.com \
    --cc=palmer@rivosinc.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.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).