devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <atishp@atishpatra.org>
Cc: <devicetree@vger.kernel.org>, <damien.lemoal@wdc.com>,
	<aou@eecs.berkeley.edu>, <Cyril.Jean@microchip.com>,
	<david.abdurachmanov@gmail.com>, <Daire.McNamara@microchip.com>,
	<jassisinghbrar@gmail.com>, <atish.patra@wdc.com>,
	<anup.patel@wdc.com>, <robh+dt@kernel.org>, <palmer@dabbelt.com>,
	<paul.walmsley@sifive.com>, <Lewis.Hanly@microchip.com>,
	<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v2 5/5] MAINTAINERS: add microchip polarfire soc support
Date: Wed, 2 Dec 2020 09:13:29 +0000	[thread overview]
Message-ID: <1cb10c03-d5fd-c6bc-62fa-7eb854a31cba@microchip.com> (raw)
In-Reply-To: <CAOnJCUL3qELbuDAAgyGB8jMP3x6WB1qhubd3UZNKqE5zs1B2wg@mail.gmail.com>

On 01/12/2020 18:06, Atish Patra wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Tue, Dec 1, 2020 at 3:03 AM <conor.dooley@microchip.com> wrote:
>> From: Conor Dooley <conor.dooley@microchip.com>
>>
>> Add Cyril Jean and Lewis Hanly as maintainers for the Microchip SoC
>> directory
>>
>> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> I think this patch will make more sense in my basic SoC support patch.
> Can I include this patch in my series as is?

Eh sure, I don't mind.

Should it be split and I add the mailbox entry in my series & you do the rest?

>
>> ---
>>  MAINTAINERS | 9 +++++++++
>>  1 file changed, 9 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 2daa6ee673f7..2241bdac4816 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -14989,6 +14989,15 @@ F:     arch/riscv/
>>  N:     riscv
>>  K:     riscv
>>
>> +RISC-V/MICROCHIP POLARFIRE SOC SUPPORT
>> +M:     Lewis Hanly <lewis.hanly@microchip.com>
>> +M:     Cyril Jean <cyril.jean@microchip.com>
>> +L:     linux-riscv@lists.infradead.org
>> +S:     Supported
>> +F:     drivers/mailbox/mailbox-mpfs.c
>> +F:     drivers/soc/microchip/
>> +F:     include/soc/microchip/mpfs.h
>> +
>>  RNBD BLOCK DRIVERS
>>  M:     Danil Kipnis <danil.kipnis@cloud.ionos.com>
>>  M:     Jack Wang <jinpu.wang@cloud.ionos.com>
>> --
>> 2.17.1
>>
>>
>> _______________________________________________
>> linux-riscv mailing list
>> linux-riscv@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-riscv
>
>
> --
> Regards,
> Atish
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv



  reply	other threads:[~2020-12-02  9:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-01 11:03 [PATCH v2 5/5] MAINTAINERS: add microchip polarfire soc support conor.dooley
2020-12-01 18:06 ` Atish Patra
2020-12-02  9:13   ` Conor.Dooley [this message]
2020-12-02 18:44     ` Atish Patra

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=1cb10c03-d5fd-c6bc-62fa-7eb854a31cba@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=Cyril.Jean@microchip.com \
    --cc=Daire.McNamara@microchip.com \
    --cc=Lewis.Hanly@microchip.com \
    --cc=anup.patel@wdc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=atish.patra@wdc.com \
    --cc=atishp@atishpatra.org \
    --cc=damien.lemoal@wdc.com \
    --cc=david.abdurachmanov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@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).