From: Alistair Francis <alistair23@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Bin Meng <bmeng.cn@gmail.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [PATCH] hw/riscv: virt: pass random seed to fdt
Date: Thu, 16 Jun 2022 22:17:40 +1000 [thread overview]
Message-ID: <CAKmqyKPRd-aA=R3d+naV4YC=9KqRLvGBwkyqDGvs91AzOCOsHQ@mail.gmail.com> (raw)
In-Reply-To: <Yqr/jN1bnEmDVIKm@zx2c4.com>
On Thu, Jun 16, 2022 at 8:01 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> Hi Alistair,
>
> On Thu, Jun 16, 2022 at 12:32:36PM +1000, Alistair Francis wrote:
> > Applied to riscv-to-apply.next with the full stop removed
>
> Great, thanks. Just wondering: am I looking in the right repo? I don't
> see it here: https://github.com/alistair23/qemu/commits/riscv-to-apply.next
That's the right repo, I just have to push the latest updates. You
should see it there tomorrow
Alistair
>
> Jason
next prev parent reply other threads:[~2022-06-16 12:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 11:58 [PATCH] hw/riscv: virt: pass random seed to fdt Jason A. Donenfeld
2022-06-15 4:05 ` Bin Meng
2022-06-16 2:32 ` Alistair Francis
2022-06-16 10:01 ` Jason A. Donenfeld
2022-06-16 12:17 ` Alistair Francis [this message]
2022-06-29 2:09 ` Alistair Francis
2022-07-05 1:09 ` Jason A. Donenfeld
2022-07-07 1:04 ` Jason A. Donenfeld
2022-07-08 7:59 ` Alistair Francis
2022-07-08 9:56 ` Jason A. Donenfeld
2022-07-11 0:25 ` Alistair Francis
2022-07-11 0:27 ` Jason A. Donenfeld
2022-07-11 3:36 ` Alistair Francis
2022-07-11 16:45 ` Jason A. Donenfeld
2022-07-13 17:29 ` Jason A. Donenfeld
2022-07-18 22:39 ` 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='CAKmqyKPRd-aA=R3d+naV4YC=9KqRLvGBwkyqDGvs91AzOCOsHQ@mail.gmail.com' \
--to=alistair23@gmail.com \
--cc=Jason@zx2c4.com \
--cc=alistair.francis@wdc.com \
--cc=bmeng.cn@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).