linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hch@infradead.org (Christoph Hellwig)
To: linux-riscv@lists.infradead.org
Subject: [sw-dev] Re: [PULL RFC] RISC-V Updates for the 4.19 Merge Window
Date: Tue, 14 Aug 2018 06:34:50 -0700	[thread overview]
Message-ID: <20180814133450.GA28080@infradead.org> (raw)
In-Reply-To: <20180814054555.j2riqqiqu5j7ktwr@excalibur.cnev.de>

On Tue, Aug 14, 2018 at 07:45:55AM +0200, Karsten Merker wrote:
> Hello Palmer,
> 
> I think it is easier and faster if you do that.

Rob also had the same comments plus a few more:

http://lists.infradead.org/pipermail/linux-riscv/2018-August/001139.html

I'm on vacation at the moment and a little slow to respond, so if
Palmer could handle these it would be great.

      reply	other threads:[~2018-08-14 13:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 20:12 [PULL RFC] RISC-V Updates for the 4.19 Merge Window Palmer Dabbelt
2018-08-13 20:52 ` Karsten Merker
2018-08-13 23:14   ` [sw-dev] " Palmer Dabbelt
2018-08-14  5:45     ` Karsten Merker
2018-08-14 13:34       ` 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=20180814133450.GA28080@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;
as well as URLs for NNTP newsgroup(s).