From: hch@infradead.org (Christoph Hellwig)
To: linux-riscv@lists.infradead.org
Subject: upstream status?
Date: Tue, 6 Mar 2018 21:43:32 -0800 [thread overview]
Message-ID: <20180307054332.GA30431@infradead.org> (raw)
In-Reply-To: <mhng-19826e89-fd2a-4d4e-9847-2dcbd5b542bc@palmer-si-x1c4>
On Tue, Mar 06, 2018 at 04:43:33PM -0800, Palmer Dabbelt wrote:
> Ah, I need lots of help! Right now the biggest blocker is getting our
> first-level interrupt stuff sorted out.
Ok. Any list of pending issues?
> Are you going to be at ELC next week? Maybe we could chat there?
Just got back to Europe from the West Coast yesterday, so no..
next prev parent reply other threads:[~2018-03-07 5:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 15:58 upstream status? Christoph Hellwig
2018-03-07 0:43 ` Palmer Dabbelt
2018-03-07 5:43 ` Christoph Hellwig [this message]
2018-03-07 5:45 ` 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=20180307054332.GA30431@infradead.org \
--to=hch@infradead.org \
--cc=linux-riscv@lists.infradead.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