From: Bin Meng <bmeng.cn@gmail.com>
To: Rahul Pathak <rpathak@ventanamicro.com>
Cc: "Alistair Francis" <alistair23@gmail.com>,
"open list:RISC-V" <qemu-riscv@nongnu.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Alistair Francis" <alistair.francis@wdc.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Anup Patel" <apatel@ventanamicro.com>,
"Rahul Pathak" <rpathakmailbox@gmail.com>,
"Víctor Colombo" <victor.colombo@eldorado.org.br>
Subject: Re: [PATCH v2] target/riscv: fix user-mode build issue because mhartid
Date: Wed, 29 Jun 2022 11:52:54 +0800 [thread overview]
Message-ID: <CAEUhbmV45wwZx72y6D2Vcn0VcwtfCRvma574inuCCYw48gCfCg@mail.gmail.com> (raw)
In-Reply-To: <CA+Oz1=Yi42RtJ6CphL0d8KYjeZhDu7H101JY59rL0fO+4oq9zQ@mail.gmail.com>
Hi Rahul,
On Wed, Jun 29, 2022 at 10:07 AM Rahul Pathak <rpathak@ventanamicro.com> wrote:
>
> Hi Alistair
>
> My fix patch needs to be dropped since Anup took care of this issue
> in his yesterdays series update in this patch -
> [PATCH v8 4/4] target/riscv: Force disable extensions if priv spec
> version does not match
I don't understand. Each patch should keep bisectability.
This sounds like to me, that
[PATCH v8 4/4] target/riscv: Force disable extensions if priv spec
version does not match
has an issue that it does 2 things: one is to fix this bug, and the
other one is to force disable extensions.
Which is not right.
Regards,
Bin
next prev parent reply other threads:[~2022-06-29 3:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 16:40 [PATCH v2] target/riscv: fix user-mode build issue because mhartid Rahul Pathak
2022-06-29 2:01 ` Alistair Francis
2022-06-29 2:07 ` Rahul Pathak
2022-06-29 3:52 ` Bin Meng [this message]
2022-06-29 4:30 ` Anup Patel
2022-06-27 16:49 Rahul Pathak
2022-06-27 17:01 ` Rahul Pathak
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=CAEUhbmV45wwZx72y6D2Vcn0VcwtfCRvma574inuCCYw48gCfCg@mail.gmail.com \
--to=bmeng.cn@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=apatel@ventanamicro.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=rpathak@ventanamicro.com \
--cc=rpathakmailbox@gmail.com \
--cc=victor.colombo@eldorado.org.br \
/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.