From: <Conor.Dooley@microchip.com>
To: <palmer@rivosinc.com>, <gregkh@linuxfoundation.org>,
<arnd@arndb.de>, <akpm@linux-foundation.org>
Cc: <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 04:39:08 +0000 [thread overview]
Message-ID: <fffa1761-9636-f6bc-fff3-54b6a60f5c8d@microchip.com> (raw)
In-Reply-To: <mhng-5c57560e-a00b-4fd8-95ee-5e2fc0dcd34c@palmer-ri-x1c9>
On 02/06/2022 02:55, Palmer Dabbelt wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Mon, 23 May 2022 13:00:01 PDT (-0700), Conor.Dooley@microchip.com wrote:
>> On 23/05/2022 20:52, Palmer Dabbelt wrote:
>>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>>
>>> On Mon, 23 May 2022 04:42:53 PDT (-0700), Conor.Dooley@microchip.com wrote:
>>>> On 05/05/2022 11:55, Conor Dooley wrote:
>>>>> 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.
>>>>>
>>>>> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
>>>>
>>>> Hey Palmer,
>>>> I know youre busy etc but just a reminder :)
>>>
>>> Sorry, I didn't realize this was aimed at the RISC-V tree. I'm fine
>>> taking it, but it seems like these should have gone in along with the
>>> drivers.
>>
>> Yeah, sorry. In hindsight it should've but that ship has sailed. I sent
>> the rng bundled this way b/c I didn't want to end up a conflict.
>> Obv. there's not a rush so I can always split it back out if needs be.
>
> 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
>
>>
>>>
>>> Arnd: maybe this is really an SOC tree sort of thing? No big deal
>>> either way on my end, just let me know.
>>>
>>>> Thanks,
>>>> Conor.
>>>>
>>>>> ---
>>>>> MAINTAINERS | 5 ++++-
>>>>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>>>> index fd768d43e048..d7602658b0a5 100644
>>>>> --- a/MAINTAINERS
>>>>> +++ b/MAINTAINERS
>>>>> @@ -16939,12 +16939,15 @@ N: riscv
>>>>> K: riscv
>>>>>
>>>>> RISC-V/MICROCHIP POLARFIRE SOC SUPPORT
>>>>> -M: Lewis Hanly <lewis.hanly@microchip.com>
>>>>> M: Conor Dooley <conor.dooley@microchip.com>
>>>>> +M: Daire McNamara <daire.mcnamara@microchip.com>
>>>>> L: linux-riscv@lists.infradead.org
>>>>> S: Supported
>>>>> F: arch/riscv/boot/dts/microchip/
>>>>> +F: drivers/char/hw_random/mpfs-rng.c
>>>>> +F: drivers/clk/microchip/clk-mpfs.c
>>>>> F: drivers/mailbox/mailbox-mpfs.c
>>>>> +F: drivers/pci/controller/pcie-microchip-host.c
>>>>> F: drivers/soc/microchip/
>>>>> F: include/soc/microchip/mpfs.h
>>>>>
>>>>
>>
>
>
> _______________________________________________
> 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 4:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d50f506c-92fd-39c2-d5d9-5eb9c60b1de6@microchip.com>
2022-06-02 1:55 ` [PATCH v4 1/1] MAINTAINERS: add polarfire rng, pci and clock drivers Palmer Dabbelt
2022-06-02 4:39 ` Conor.Dooley [this message]
2022-06-02 16:31 ` Bjorn Helgaas
2022-06-02 22:05 ` Palmer Dabbelt
2022-06-02 16:03 ` Bjorn Helgaas
2022-06-09 22:43 ` Stephen Boyd
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=fffa1761-9636-f6bc-fff3-54b6a60f5c8d@microchip.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox