All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: Alistair Francis <alistair.francis@wdc.com>
Cc: "open list:RISC-V" <qemu-riscv@nongnu.org>,
	Sagar Karandikar <sagark@eecs.berkeley.edu>,
	Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Alistair Francis <alistair23@gmail.com>
Subject: Re: [PATCH v1 1/1] MAINTAINERS: Update the RISC-V CPU Maintainers
Date: Wed, 7 Apr 2021 09:40:35 +0800	[thread overview]
Message-ID: <CAEUhbmVMcn63My=7RMVWAEgsqrX6=O5X+C-RyPRNaGSQB5BNtA@mail.gmail.com> (raw)
In-Reply-To: <6564ba829c40ad9aa7d28f43be69d8eb5cf4b56b.1617749142.git.alistair.francis@wdc.com>

On Wed, Apr 7, 2021 at 6:51 AM Alistair Francis
<alistair.francis@wdc.com> wrote:
>
> Update the RISC-V maintainers by removing Sagar and Bastian who haven't
> been involved recently.
>
> Also add Bin who has been helping with reviews.
>
> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
> ---
> I have run this by all of the people involved and they are all ok with
> the change.
>
>  MAINTAINERS | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
>

Acked-by: Bin Meng <bin.meng@windriver.com>


WARNING: multiple messages have this Message-ID (diff)
From: Bin Meng <bmeng.cn@gmail.com>
To: Alistair Francis <alistair.francis@wdc.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	"open list:RISC-V" <qemu-riscv@nongnu.org>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Sagar Karandikar <sagark@eecs.berkeley.edu>,
	 Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
	Alistair Francis <alistair23@gmail.com>
Subject: Re: [PATCH v1 1/1] MAINTAINERS: Update the RISC-V CPU Maintainers
Date: Wed, 7 Apr 2021 09:40:35 +0800	[thread overview]
Message-ID: <CAEUhbmVMcn63My=7RMVWAEgsqrX6=O5X+C-RyPRNaGSQB5BNtA@mail.gmail.com> (raw)
In-Reply-To: <6564ba829c40ad9aa7d28f43be69d8eb5cf4b56b.1617749142.git.alistair.francis@wdc.com>

On Wed, Apr 7, 2021 at 6:51 AM Alistair Francis
<alistair.francis@wdc.com> wrote:
>
> Update the RISC-V maintainers by removing Sagar and Bastian who haven't
> been involved recently.
>
> Also add Bin who has been helping with reviews.
>
> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
> ---
> I have run this by all of the people involved and they are all ok with
> the change.
>
>  MAINTAINERS | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
>

Acked-by: Bin Meng <bin.meng@windriver.com>


  reply	other threads:[~2021-04-07  1:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06 22:48 [PATCH v1 1/1] MAINTAINERS: Update the RISC-V CPU Maintainers Alistair Francis
2021-04-06 22:48 ` Alistair Francis
2021-04-07  1:40 ` Bin Meng [this message]
2021-04-07  1:40   ` Bin Meng
2021-04-07  8:14 ` Bastian Koppelmann
2021-04-07  8:14   ` Bastian Koppelmann
2021-04-07 12:15 ` Philippe Mathieu-Daudé
2021-04-07 12:15   ` Philippe Mathieu-Daudé
2021-04-07 14:23 ` Alistair Francis
2021-04-07 14:23   ` Alistair Francis

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='CAEUhbmVMcn63My=7RMVWAEgsqrX6=O5X+C-RyPRNaGSQB5BNtA@mail.gmail.com' \
    --to=bmeng.cn@gmail.com \
    --cc=alistair.francis@wdc.com \
    --cc=alistair23@gmail.com \
    --cc=kbastian@mail.uni-paderborn.de \
    --cc=palmer@dabbelt.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=sagark@eecs.berkeley.edu \
    /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.