From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] hw/microblaze: pass random seed to fdt
Date: Wed, 27 Jul 2022 13:51:12 +0200 [thread overview]
Message-ID: <YuEmsNkrwldSFYnf@zx2c4.com> (raw)
In-Reply-To: <0c5d679f-367f-080d-7c46-137383fd054c@linaro.org>
Hi Richard,
On Tue, Jul 26, 2022 at 08:13:09PM -0700, Richard Henderson wrote:
> On 7/26/22 18:49, Jason A. Donenfeld wrote:
> > Hi Edgar,
> >
> > On Thu, Jul 21, 2022 at 8:43 PM Edgar E. Iglesias
> > <edgar.iglesias@gmail.com> wrote:
> >> Ah OK, Paolo, it would be great if you would take this via your tree!
> >
> > It looks like Paolo never did this. So you might want to queue this
> > somewhere, or bug him to take it, or something. I don't know how this
> > works with 7.1-rc0 just being tagged, but I assume this means this has
> > to wait until 7.2
>
> Yes, it has missed the window by over a week now: soft freeze.
> You really should have kept all of these in one thread.
Shoulda woulda coulda. It doesn't really matter to me much when the
microblaze one goes in, just that it can exist in some maintainer tree.
I'd like to be able to remove this from my "pending patch list" that I
have to monitor lest things be forgotten.
Jason
next prev parent reply other threads:[~2022-07-27 11:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 12:23 [PATCH] hw/microblaze: pass random seed to fdt Jason A. Donenfeld
2022-07-20 7:13 ` Edgar E. Iglesias
2022-07-21 16:43 ` Jason A. Donenfeld
2022-07-21 18:43 ` Edgar E. Iglesias
2022-07-27 1:49 ` Jason A. Donenfeld
2022-07-27 3:13 ` Richard Henderson
2022-07-27 11:51 ` Jason A. Donenfeld [this message]
2022-09-08 9:40 ` [PATCH RESEND] " Jason A. Donenfeld
2022-09-21 10:32 ` Jason A. Donenfeld
2022-09-21 20:27 ` Edgar E. Iglesias
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=YuEmsNkrwldSFYnf@zx2c4.com \
--to=jason@zx2c4.com \
--cc=edgar.iglesias@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).