From: Gerd Hoffmann <kraxel@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Feng Tian <feng.tian@intel.com>,
"open list:nvme" <qemu-block@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Keith Busch <keith.busch@intel.com>,
Gonglei <arei.gonglei@huawei.com>,
"vladislav.vovchenko@sk.com" <vladislav.vovchenko@sk.com>,
Kevin O'Connor <kevin@koconnor.net>
Subject: Re: [Qemu-devel] [PATCH] nvme: generate OpenFirmware device path in the "bootorder" fw_cfg file
Date: Tue, 02 Feb 2016 11:13:52 +0100 [thread overview]
Message-ID: <1454408032.9300.51.camel@redhat.com> (raw)
In-Reply-To: <56AF18EF.8070902@redhat.com>
On Mo, 2016-02-01 at 09:35 +0100, Laszlo Ersek wrote:
> Gerd,
>
> On 02/01/16 06:57, vladislav.vovchenko@sk.com wrote:
> >> -----Original Message-----
> >> From: Laszlo Ersek [mailto:lersek@redhat.com]
> >> Sent: 27 January 2016 02:21
> >> To: qemu-devel@nongnu.org
> >> Cc: Keith Busch; Kevin Wolf; open list:nvme; Gonglei; Vladislav Vovchenko
> >> SFS; Feng Tian; Gerd Hoffmann; Kevin O'Connor
> >> Subject: [PATCH] nvme: generate OpenFirmware device path in the
> >> "bootorder" fw_cfg file
>
> [snip]
>
> > Tested-by: Vladislav Vovchenko <vladislav.vovchenko@sk.com>
>
> Can you please pick up this patch? (You handled the precursor patch,
> commit 33739c712982.)
>
> This one has A-b's from Gonglei and Keith, and a T-b from Vladislav.
> (Thanks for those, guys!)
Yep. The fw_cfg dma linuxboot patch is ready too, so I'll go prepare a
fw_cfg pull requests with them.
cheers,
Gerd
prev parent reply other threads:[~2016-02-02 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 23:21 [Qemu-devel] [PATCH] nvme: generate OpenFirmware device path in the "bootorder" fw_cfg file Laszlo Ersek
2016-01-27 2:52 ` Gonglei (Arei)
2016-01-29 19:07 ` Keith Busch
2016-02-01 5:57 ` vladislav.vovchenko
2016-02-01 8:35 ` Laszlo Ersek
2016-02-02 10:13 ` Gerd Hoffmann [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=1454408032.9300.51.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=feng.tian@intel.com \
--cc=keith.busch@intel.com \
--cc=kevin@koconnor.net \
--cc=kwolf@redhat.com \
--cc=lersek@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vladislav.vovchenko@sk.com \
/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.