qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Peter Crosthwaite <crosthwaitepeter@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
	Peter Crosthwaite <crosthwaite.peter@gmail.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Alistair Francis <alistair.francis@xilinx.com>
Subject: Re: [Qemu-devel] [RFC 0/3] ARM: Machine specific boot blobs
Date: Mon, 19 Oct 2015 17:49:40 +0100	[thread overview]
Message-ID: <CAFEAcA99M3CTowOR3OWjwxc3FWLvCZ+Qv06WNhYkgxmDQ-xHWA@mail.gmail.com> (raw)
In-Reply-To: <CAPokK=q6j2Tc2ASKTpxB16UU=F9D6t8LpC84XbWmYfnuyUw1_w@mail.gmail.com>

On 18 October 2015 at 17:25, Peter Crosthwaite
<crosthwaitepeter@gmail.com> wrote:
> Ping!
>
> Although a little featurish and RFCish, this does repair the boot of
> two ARM machines so it is very much a bugfix and we should consider
> for 2.5. Otherwise we go to release (again) with two broken machines.

The general idea looks ok to me, but sending a patchset out labelled
RFC when we hit softfreeze is a pretty good way to cause people to
ignore it :-)

Patch 1 looks OK I think; haven't looked too closely at the others.

How are you picking the firmware blob addresses ?

thanks
-- PMM

  reply	other threads:[~2015-10-19 16:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-10  3:13 [Qemu-devel] [RFC 0/3] ARM: Machine specific boot blobs Peter Crosthwaite
2015-10-10  3:13 ` [Qemu-devel] [RFC 1/3] arm: boot: Add board specific setup code API Peter Crosthwaite
2015-10-10  3:13 ` [Qemu-devel] [RFC 2/3] arm: highbank: Implement dummy monitor Peter Crosthwaite
2015-10-10  3:13 ` [Qemu-devel] [RFC 3/3] arm: xilinx_zynq: Add linux pre-boot Peter Crosthwaite
2015-10-18 16:25 ` [Qemu-devel] [RFC 0/3] ARM: Machine specific boot blobs Peter Crosthwaite
2015-10-19 16:49   ` Peter Maydell [this message]
2015-10-19 17:25     ` Peter Crosthwaite

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=CAFEAcA99M3CTowOR3OWjwxc3FWLvCZ+Qv06WNhYkgxmDQ-xHWA@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=alistair.francis@xilinx.com \
    --cc=crosthwaite.peter@gmail.com \
    --cc=crosthwaitepeter@gmail.com \
    --cc=linux@roeck-us.net \
    --cc=qemu-devel@nongnu.org \
    --cc=robh@kernel.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).