From: Christoph Hellwig <hch@lst.de>
To: Changbin Du <changbin.du@gmail.com>
Cc: Albert Ou <aou@eecs.berkeley.edu>,
linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH] riscv: uaccess: fix __put_kernel_nofault()
Date: Tue, 3 Nov 2020 09:50:23 +0100 [thread overview]
Message-ID: <20201103085023.GA14092@lst.de> (raw)
In-Reply-To: <20201102073052.199638-1-changbin.du@gmail.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
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Changbin Du <changbin.du@gmail.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Andrew Morton <akpm@linux-foundation.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] riscv: uaccess: fix __put_kernel_nofault()
Date: Tue, 3 Nov 2020 09:50:23 +0100 [thread overview]
Message-ID: <20201103085023.GA14092@lst.de> (raw)
In-Reply-To: <20201102073052.199638-1-changbin.du@gmail.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2020-11-03 8:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 7:30 [PATCH] riscv: uaccess: fix __put_kernel_nofault() Changbin Du
2020-11-02 7:30 ` Changbin Du
2020-11-03 8:50 ` Christoph Hellwig [this message]
2020-11-03 8:50 ` Christoph Hellwig
2020-11-06 6:51 ` Anup Patel
2020-11-06 6:51 ` Anup Patel
2020-11-06 7:45 ` Palmer Dabbelt
2020-11-06 7: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=20201103085023.GA14092@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=changbin.du@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.