linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Alan Kao <alankao@andestech.com>
Cc: linux-riscv@lists.infradead.org, palmer@sifive.com,
	Vincent Chen <deanbo422@gmail.com>,
	linux-kernel@vger.kernel.org,
	Greentime Hu <greentime@andestech.com>
Subject: Re: [PATCH] riscv: fix accessing 8-byte variable from RV32
Date: Fri, 22 Mar 2019 06:34:02 -0700	[thread overview]
Message-ID: <20190322133402.GC32464@infradead.org> (raw)
In-Reply-To: <1553236624-31275-1-git-send-email-alankao@andestech.com>

Looks good,

Reviewed-by: Christoph Hellwig <hch@lst.de>

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      reply	other threads:[~2019-03-22 13:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22  6:37 [PATCH] riscv: fix accessing 8-byte variable from RV32 Alan Kao
2019-03-22 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=20190322133402.GC32464@infradead.org \
    --to=hch@infradead.org \
    --cc=alankao@andestech.com \
    --cc=deanbo422@gmail.com \
    --cc=greentime@andestech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@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).