From: Bjorn Helgaas <helgaas@kernel.org>
To: Conor.Dooley@microchip.com
Cc: palmer@rivosinc.com, gregkh@linuxfoundation.org, arnd@arndb.de,
akpm@linux-foundation.org, sboyd@kernel.org,
linux-pci@vger.kernel.org, mturquette@baylibre.com,
paul.walmsley@sifive.com, kw@linux.com,
linux-clk@vger.kernel.org, aou@eecs.berkeley.edu,
lorenzo.pieralisi@arm.com, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, Daire.McNamara@microchip.com,
Lewis.Hanly@microchip.com, Cyril.Jean@microchip.com,
robh@kernel.org
Subject: Re: [PATCH v4 1/1] MAINTAINERS: add polarfire rng, pci and clock drivers
Date: Thu, 2 Jun 2022 11:31:52 -0500 [thread overview]
Message-ID: <20220602163152.GA22276@bhelgaas> (raw)
In-Reply-To: <fffa1761-9636-f6bc-fff3-54b6a60f5c8d@microchip.com>
On Thu, Jun 02, 2022 at 04:39:08AM +0000, Conor.Dooley@microchip.com wrote:
> On 02/06/2022 02:55, Palmer Dabbelt wrote:
> > I'm adding a bunch of subsystem maintainers just to check again. I
> > don't have any problem with it, just not really a RISC-V thing and don't
> > wan to make a mess. I've stashed it over at palmer/pcsoc-maintainers
> > for now.
> >
> > Sorry if I'm being overly pedantic about this one...
>
> I don't mind. Maybe this should go via Andrew next cycle or w/e?
> There's obviously no hurry etc
My turn to be overly pedantic :) IMHO there's no benefit in delaying
MAINTAINERS updates. There's zero risk, and delaying only means
people will miss out on bug reports and other things they should learn
about.
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <helgaas@kernel.org>
To: Conor.Dooley@microchip.com
Cc: palmer@rivosinc.com, gregkh@linuxfoundation.org, arnd@arndb.de,
akpm@linux-foundation.org, sboyd@kernel.org,
linux-pci@vger.kernel.org, mturquette@baylibre.com,
paul.walmsley@sifive.com, kw@linux.com,
linux-clk@vger.kernel.org, aou@eecs.berkeley.edu,
lorenzo.pieralisi@arm.com, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, Daire.McNamara@microchip.com,
Lewis.Hanly@microchip.com, Cyril.Jean@microchip.com,
robh@kernel.org
Subject: Re: [PATCH v4 1/1] MAINTAINERS: add polarfire rng, pci and clock drivers
Date: Thu, 2 Jun 2022 11:31:52 -0500 [thread overview]
Message-ID: <20220602163152.GA22276@bhelgaas> (raw)
In-Reply-To: <fffa1761-9636-f6bc-fff3-54b6a60f5c8d@microchip.com>
On Thu, Jun 02, 2022 at 04:39:08AM +0000, Conor.Dooley@microchip.com wrote:
> On 02/06/2022 02:55, Palmer Dabbelt wrote:
> > I'm adding a bunch of subsystem maintainers just to check again. I
> > don't have any problem with it, just not really a RISC-V thing and don't
> > wan to make a mess. I've stashed it over at palmer/pcsoc-maintainers
> > for now.
> >
> > Sorry if I'm being overly pedantic about this one...
>
> I don't mind. Maybe this should go via Andrew next cycle or w/e?
> There's obviously no hurry etc
My turn to be overly pedantic :) IMHO there's no benefit in delaying
MAINTAINERS updates. There's zero risk, and delaying only means
people will miss out on bug reports and other things they should learn
about.
Bjorn
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-06-02 16:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 10:55 [PATCH v4 0/1] polarfire soc kconfig/maintainers updates Conor Dooley
2022-05-05 10:55 ` Conor Dooley
2022-05-05 10:55 ` [PATCH v4 1/1] MAINTAINERS: add polarfire rng, pci and clock drivers Conor Dooley
2022-05-05 10:55 ` Conor Dooley
2022-05-23 11:42 ` Conor.Dooley
2022-05-23 11:42 ` Conor.Dooley
2022-05-23 19:52 ` Palmer Dabbelt
2022-05-23 19:52 ` Palmer Dabbelt
2022-05-23 20:00 ` Conor.Dooley
2022-05-23 20:00 ` Conor.Dooley
2022-06-02 1:55 ` Palmer Dabbelt
2022-06-02 1:55 ` Palmer Dabbelt
2022-06-02 4:39 ` Conor.Dooley
2022-06-02 4:39 ` Conor.Dooley
2022-06-02 16:31 ` Bjorn Helgaas [this message]
2022-06-02 16:31 ` Bjorn Helgaas
2022-06-02 22:05 ` Palmer Dabbelt
2022-06-02 22:05 ` Palmer Dabbelt
2022-06-02 16:03 ` Bjorn Helgaas
2022-06-02 16:03 ` Bjorn Helgaas
2022-06-09 22:43 ` Stephen Boyd
2022-06-09 22:43 ` Stephen Boyd
2022-06-09 22:53 ` Conor.Dooley
2022-06-09 22:53 ` 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=20220602163152.GA22276@bhelgaas \
--to=helgaas@kernel.org \
--cc=Conor.Dooley@microchip.com \
--cc=Cyril.Jean@microchip.com \
--cc=Daire.McNamara@microchip.com \
--cc=Lewis.Hanly@microchip.com \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--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@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=sboyd@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 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.