From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Bin Meng <bmeng.cn@gmail.com>, Alistair Francis <alistair23@gmail.com>
Cc: "open list:RISC-V" <qemu-riscv@nongnu.org>,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
Palmer Dabbelt <palmerdabbelt@google.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Alistair Francis <Alistair.Francis@wdc.com>
Subject: Re: [PATCH] roms: opensbi: Upgrade from v0.6 to v0.7
Date: Wed, 22 Apr 2020 10:15:08 +0200 [thread overview]
Message-ID: <bd7da39b-4ece-7e72-a0a0-1d401c3b8c34@redhat.com> (raw)
In-Reply-To: <CAEUhbmWsNmTTTFz66M4sK-pEtEMOhfoYzCHYVyEF4AJ2X02twA@mail.gmail.com>
On 4/22/20 3:30 AM, Bin Meng wrote:
> Hi Alistair,
>
> On Tue, Apr 21, 2020 at 9:34 AM Bin Meng <bmeng.cn@gmail.com> wrote:
>>
>> Hi Alistair,
>>
>> On Tue, Apr 21, 2020 at 2:41 AM Alistair Francis <alistair23@gmail.com> wrote:
>>>
>>> On Mon, Apr 20, 2020 at 6:25 AM Bin Meng <bmeng.cn@gmail.com> wrote:
>>>>
>>>> Upgrade OpenSBI from v0.6 to v0.7 and the pre-built bios images.
>>>>
>>>> The v0.7 release includes the following commits:
>>>>
>>>> f64f4b9 lib: Add a new platform feature to bringup secondary harts
>>>> b677a9b lib: Implement hart hotplug
>>>> 5b48240 lib: Add possible hart status values
>>>> e3f69fc lib: Implement Hart State Management (HSM) SBI extension
>>>> 6704216 lib: Check MSIP bit after returning from WFI
[...]
>>>> 6c7922e lib: Support vector extension
>>>> 615587c docs: Update README about supported SBI versions
>>>> 66d0184 lib: Allow overriding SBI implementation ID
>>>> 9f1b72c include: Bump-up version to 0.7
The git-short-log in the commit message is very appreciated, thanks.
>>>>
>>>> Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
>>>
>>> Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
>>>
>>> Can you share a git branch with this patch? From memory these binary
>>> patches don't apply well from emails.
Indeed. These patches are good candidate to use the 'git-format-patch
--no-binary' option with a link to a git repository to fetch the full
commit:
--no-binary
Do not output contents of changes in binary files,
instead display a notice that those files changed.
Patches generated using this option cannot be applied
properly, but they are still useful for code review.
>>
>> Sure. Please grab the bits from http://github.com/lbmeng/qemu opensbi branch.
>>
>> You can also use patchwork to help with your custodian work.
>> http://patchwork.ozlabs.org/project/qemu-devel/patch/1587389038-1549-1-git-send-email-bmeng.cn@gmail.com/
>>
>> Click on the "mbox" button to download the patch and apply it.
>
> Will this be 5.0, or 5.1?
Unlikely 5.1, too late.
>
> Regards,
> Bin
>
next prev parent reply other threads:[~2020-04-22 8:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 13:23 [PATCH] roms: opensbi: Upgrade from v0.6 to v0.7 Bin Meng
2020-04-20 18:33 ` Alistair Francis
2020-04-21 1:34 ` Bin Meng
2020-04-22 1:30 ` Bin Meng
2020-04-22 8:15 ` Philippe Mathieu-Daudé [this message]
2020-04-22 9:50 ` Bin Meng
2020-04-22 10:04 ` Philippe Mathieu-Daudé
2020-04-22 13:19 ` Bin Meng
2020-04-22 17:36 ` Alistair Francis
2020-04-22 17:35 ` Alistair Francis
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=bd7da39b-4ece-7e72-a0a0-1d401c3b8c34@redhat.com \
--to=philmd@redhat.com \
--cc=Alistair.Francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=bmeng.cn@gmail.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=palmerdabbelt@google.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
/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).