From: Palmer Dabbelt <palmer@sifive.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH] MAINTAINERS: change the arch/riscv git tree to the new shared tree
Date: Thu, 27 Jun 2019 17:30:35 -0700 (PDT) [thread overview]
Message-ID: <mhng-45bbc7fa-7b3e-4893-8a09-5e7449673254@palmer-si-x1e> (raw)
In-Reply-To: <20190627090116.GB23838@infradead.org>
On Thu, 27 Jun 2019 02:01:16 PDT (-0700), Christoph Hellwig wrote:
> On Thu, Jun 13, 2019 at 12:25:18AM -0700, Christoph Hellwig wrote:
>> On Thu, Jun 13, 2019 at 12:07:21AM -0700, Paul Walmsley wrote:
>> > Palmer, with Konstantin's gracious help, set up a shared kernel.org
>> > git tree for arch/riscv patches going forward. Change the MAINTAINERS
>> > file accordingly.
>> >
>> > Signed-off-by: Paul Walmsley <paul.walmsley@sifive.com>
>> > Cc: Palmer Dabbelt <palmer@sifive.com>
>>
>> Should you be added to the maintainers? Is Albert still around, as
>> I see a lot of people Ccing him, but never getting an answer?
>
> ping?
Odd. I significantly remember saying "let me just finish writing this patch
before we have lunch" at the last day of the workshop, but it looks like I
never sent it out and can't find the actual patch. I'm blaming this new
laptop, which is constantly blowing up on me :)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-06-28 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 7:07 [PATCH] MAINTAINERS: change the arch/riscv git tree to the new shared tree Paul Walmsley
2019-06-13 7:25 ` Christoph Hellwig
2019-06-27 9:01 ` Christoph Hellwig
2019-06-28 0:30 ` Palmer Dabbelt [this message]
2019-06-15 14:47 ` Palmer Dabbelt
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=mhng-45bbc7fa-7b3e-4893-8a09-5e7449673254@palmer-si-x1e \
--to=palmer@sifive.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=paul.walmsley@sifive.com \
/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).