From: Laszlo Ersek <lersek@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Gerd Hoffmann <kraxel@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/1] nvme: generate OpenFirmware device path in the "bootorder" fw_cfg file
Date: Tue, 2 Feb 2016 16:11:36 +0100 [thread overview]
Message-ID: <56B0C728.6010901@redhat.com> (raw)
In-Reply-To: <CAFEAcA8zA+35w-N3dVemgq9u3hDxS7RggeZKoZ8NwyTAiM3bLw@mail.gmail.com>
On 02/02/16 15:54, Peter Maydell wrote:
> On 2 February 2016 at 12:56, Gerd Hoffmann <kraxel@redhat.com> wrote:
>> Hi,
>>
>> Here comes fwcfg patch queue, a bit shorter than planned as I've ran
>> into issues while verifying linuxboot_dma fw_cfg patches.
>>
>> please pull,
>> Gerd
>>
>> The following changes since commit 10ae9d76388e3f4a31f6a1475b5e2d1f28404a10:
>>
>> Merge remote-tracking branch 'remotes/dgibson/tags/ppc-for-2.6-20160201' into staging (2016-02-02 09:13:10 +0000)
>>
>> are available in the git repository at:
>>
>>
>> git://git.kraxel.org/qemu tags/pull-fwcfg-20160202-1
>>
>> for you to fetch changes up to a907ec52cc1aefc820768b6e341b56f8f3caaca7:
>>
>> nvme: generate OpenFirmware device path in the "bootorder" fw_cfg file (2016-02-02 12:45:01 +0100)
>>
>> ----------------------------------------------------------------
>> nvme: generate OpenFirmware device path in the "bootorder" fw_cfg file
>>
>> ----------------------------------------------------------------
>
> Applied, thanks.
>
> -- PMM
>
\o/
Thank you both!
Laszlo
prev parent reply other threads:[~2016-02-02 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 12:56 [Qemu-devel] [PULL 0/1] nvme: generate OpenFirmware device path in the "bootorder" fw_cfg file Gerd Hoffmann
2016-02-02 12:56 ` [Qemu-devel] [PULL 1/1] " Gerd Hoffmann
2016-02-02 14:54 ` [Qemu-devel] [PULL 0/1] " Peter Maydell
2016-02-02 15:11 ` Laszlo Ersek [this message]
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=56B0C728.6010901@redhat.com \
--to=lersek@redhat.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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.