All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Trevor Woerner <twoerner@gmail.com>,
	palmer@dabbelt.com, Jernej Skrabec <jernej.skrabec@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	linux-riscv@lists.infradead.org, Chen-Yu Tsai <wens@csie.org>,
	Samuel Holland <samuel@sholland.org>,
	linux-sunxi@lists.linux.dev
Subject: Re: [PATCH] MAINTAINERS: update Allwinner sunXi SoC support entry
Date: Wed, 8 Feb 2023 16:28:39 +0000	[thread overview]
Message-ID: <Y+PNt8JObYK5WZKb@spud> (raw)
In-Reply-To: <20230208142841.19597-1-twoerner@gmail.com>


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

On Wed, Feb 08, 2023 at 09:28:41AM -0500, Trevor Woerner wrote:
> Update the information in the "Allwinner sunXi SoC support" block:
> - include more RISC-V information
> - move the block to keep it in alphabetical order
> - "L" before "T" (as reported by checkpatch.pl)
> 
> Signed-off-by: Trevor Woerner <twoerner@gmail.com>

> -ARM/Allwinner sunXi SoC support
> -L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> -L:	linux-sunxi@lists.linux.dev

> +ARM/RISC-V/Allwinner sunXi SoC support
> +L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> +L:	linux-riscv@lists.infradead.org
> +L:	linux-sunxi@lists.linux.dev

IIRC having the arm list is needed here because the arch/arm{,64}
entries specifically exclude the dts subdir. RISC-V doesn't do that
though, so adding the list here is mostly redundant.

Not that it matters for this patch, but might be worth doing for the
RISC-V entry at some point.

Also Trevor, I was about to send the above but noticed that your CC list
is a bit odd, changing the maintainers entry without CCing any of the
maintainers listed in it!
I assume you ran get_maintainer.pl & there was a regex match for riscv
in it, so only got Palmer & co.
I've added the sunxi folk to CC & depending on workflow they may ask you
to resend this.

FWIW if you lot use b4, the msg-id is:
20230208142841.19597-1-twoerner@gmail.com

Cheers,
Conor.


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 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

WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: Trevor Woerner <twoerner@gmail.com>,
	palmer@dabbelt.com, Jernej Skrabec <jernej.skrabec@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	linux-riscv@lists.infradead.org, Chen-Yu Tsai <wens@csie.org>,
	Samuel Holland <samuel@sholland.org>,
	linux-sunxi@lists.linux.dev
Subject: Re: [PATCH] MAINTAINERS: update Allwinner sunXi SoC support entry
Date: Wed, 8 Feb 2023 16:28:39 +0000	[thread overview]
Message-ID: <Y+PNt8JObYK5WZKb@spud> (raw)
In-Reply-To: <20230208142841.19597-1-twoerner@gmail.com>

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

On Wed, Feb 08, 2023 at 09:28:41AM -0500, Trevor Woerner wrote:
> Update the information in the "Allwinner sunXi SoC support" block:
> - include more RISC-V information
> - move the block to keep it in alphabetical order
> - "L" before "T" (as reported by checkpatch.pl)
> 
> Signed-off-by: Trevor Woerner <twoerner@gmail.com>

> -ARM/Allwinner sunXi SoC support
> -L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> -L:	linux-sunxi@lists.linux.dev

> +ARM/RISC-V/Allwinner sunXi SoC support
> +L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> +L:	linux-riscv@lists.infradead.org
> +L:	linux-sunxi@lists.linux.dev

IIRC having the arm list is needed here because the arch/arm{,64}
entries specifically exclude the dts subdir. RISC-V doesn't do that
though, so adding the list here is mostly redundant.

Not that it matters for this patch, but might be worth doing for the
RISC-V entry at some point.

Also Trevor, I was about to send the above but noticed that your CC list
is a bit odd, changing the maintainers entry without CCing any of the
maintainers listed in it!
I assume you ran get_maintainer.pl & there was a regex match for riscv
in it, so only got Palmer & co.
I've added the sunxi folk to CC & depending on workflow they may ask you
to resend this.

FWIW if you lot use b4, the msg-id is:
20230208142841.19597-1-twoerner@gmail.com

Cheers,
Conor.


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

  parent reply	other threads:[~2023-02-08 16:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 14:28 [PATCH] MAINTAINERS: update Allwinner sunXi SoC support entry Trevor Woerner
2023-02-08 14:28 ` Trevor Woerner
2023-02-08 14:49 ` Palmer Dabbelt
2023-02-08 14:49   ` Palmer Dabbelt
2023-02-08 16:28 ` Conor Dooley [this message]
2023-02-08 16:28   ` 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=Y+PNt8JObYK5WZKb@spud \
    --to=conor@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=samuel@sholland.org \
    --cc=twoerner@gmail.com \
    --cc=wens@csie.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.