From: Christoph Hellwig <hch@infradead.org>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: patches@groups.riscv.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Update the RISC-V MAINTAINERS file
Date: Thu, 25 Jan 2018 23:10:31 -0800 [thread overview]
Message-ID: <20180126071031.GA14660@infradead.org> (raw)
In-Reply-To: <20180125162315.27614-1-palmer@sifive.com>
On Thu, Jan 25, 2018 at 08:23:15AM -0800, Palmer Dabbelt wrote:
> Now that we're upstream in Linux we've been able to make some
> infrastructure changes so our port works a bit more like other ports.
> Specifically:
>
> * We now have a mailing list specific to the RISC-V Linux port, hosted
> at lists.infreadead.org.
> * We now have a kernel.org git tree where work on our port is
> coordinated.
>
> This patch changes the RISC-V maintainers entry to reflect these new
> bits of infrastructure.
>
> Signed-off-by: Palmer Dabbelt <palmer@sifive.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
prev parent reply other threads:[~2018-01-26 7:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 16:23 Palmer Dabbelt
2018-01-26 7:10 ` Christoph Hellwig [this message]
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=20180126071031.GA14660@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=patches@groups.riscv.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
all inboxes | Powered by JetHome®