From: Andrew Morton <akpm@linux-foundation.org>
To: Yixun Lan <yixun.lan@gmail.com>
Cc: Jiuyang Liu <liu@jiuyang.me>,
Andrew Waterman <waterman@eecs.berkeley.edu>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Atish Patra <atish.patra@wdc.com>,
Anup Patel <anup.patel@wdc.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Mike Rapoport <rppt@kernel.org>,
Greentime Hu <greentime.hu@sifive.com>,
Zong Li <zong.li@sifive.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Bug Fix for last patch
Date: Mon, 15 Mar 2021 20:40:28 -0700 [thread overview]
Message-ID: <20210315204028.95e8879c70581a3a7bee6a5d@linux-foundation.org> (raw)
In-Reply-To: <CALecT5iDxuzRPvPg8w=WmLT9XtWxOieDN=iRoY0nAdyhdLV+SQ@mail.gmail.com>
On Tue, 16 Mar 2021 03:15:05 +0000 Yixun Lan <yixun.lan@gmail.com> wrote:
> This patch title is too obscure to parse, it should clearly reflect
> what's the changes doing here
Yes please ;) Otherwise Andrew has to madly grep around to try to figure out
what was Jiuyang Liu's "last patch"!
next prev parent reply other threads:[~2021-03-16 3:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 6:22 [PATCH] Insert SFENCE.VMA in function set_pte_at for RISCV Jiuyang
2021-03-16 1:53 ` [PATCH 2/2] Bug Fix for last patch Jiuyang Liu
2021-03-16 3:15 ` Yixun Lan
2021-03-16 3:40 ` Andrew Morton [this message]
2021-03-16 3:46 ` [PATCH] Insert SFENCE.VMA in function set_pte_at for RISCV Jiuyang Liu
2021-03-16 5:05 ` Anup Patel
2021-03-16 6:56 ` Jiuyang Liu
2021-03-16 7:32 ` Anup Patel
2021-03-16 8:29 ` Andrew Waterman
2021-03-16 8:40 ` Anup Patel
2021-03-16 12:05 ` Alex Ghiti
2021-03-16 22:03 ` Andrew Waterman
2021-03-18 2:10 ` Jiuyang Liu
2021-03-19 7:14 ` Alex Ghiti
2021-03-30 23:35 ` Palmer Dabbelt
2021-03-17 4:17 ` 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=20210315204028.95e8879c70581a3a7bee6a5d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=anup.patel@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=greentime.hu@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=liu@jiuyang.me \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rppt@kernel.org \
--cc=wangkefeng.wang@huawei.com \
--cc=waterman@eecs.berkeley.edu \
--cc=yixun.lan@gmail.com \
--cc=zong.li@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).