From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: Laszlo Ersek <lersek@redhat.com>,
qemu-devel@nongnu.org, Kevin O'Connor <kevin@koconnor.net>,
Roman Kagan <rkagan@virtuozzo.com>,
Marcel Apfelbaum <marcel@redhat.com>,
Igor Mammedov <imammedo@redhat.com>, John Snow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v8 0/4] i386: expose floppy-related objects in SSDT
Date: Wed, 2 Mar 2016 17:10:58 +0200 [thread overview]
Message-ID: <20160302171039-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <56D701F9.3000901@openvz.org>
On Wed, Mar 02, 2016 at 06:08:41PM +0300, Denis V. Lunev wrote:
> On 02/17/2016 09:25 PM, Roman Kagan wrote:
> >Windows on UEFI systems is only capable of detecting the presence and
> >the type of floppy drives via corresponding ACPI objects.
> >
> >Those objects are added in patch 4; the preceding ones pave the way to
> >it, by making the necessary data public and by moving the whole floppy
> >drive controller description into runtime-generated SSDT.
> >
> >Roman Kagan (4):
> > i386/acpi: make floppy controller object dynamic
> > i386: expose floppy drive CMOS type
> > fdc: add function to determine drive chs limits
> > i386: populate floppy drive information in DSDT
> >
> >Signed-off-by: Roman Kagan <rkagan@virtuozzo.com>
> >Cc: Igor Mammedov <imammedo@redhat.com>
> >Cc: "Michael S. Tsirkin" <mst@redhat.com>
> >Cc: Marcel Apfelbaum <marcel@redhat.com>
> >Cc: John Snow <jsnow@redhat.com>
> >Cc: Laszlo Ersek <lersek@redhat.com>
> >Cc: Kevin O'Connor <kevin@koconnor.net>
> >---
> >changes since v7:
> > - rebased to latest master
> > - use drive max c,h,s rather than the current diskette geometry
> >
> > hw/block/fdc.c | 23 +++++++++++++
> > hw/i386/acpi-build.c | 92 ++++++++++++++++++++++++++++++++++++--------------
> > hw/i386/pc.c | 2 +-
> > include/hw/block/fdc.h | 2 ++
> > include/hw/i386/pc.h | 1 +
> > 5 files changed, 94 insertions(+), 26 deletions(-)
> >
> Michael, we have obtained Reviwed-by: from John.
> Does this set is good to be accepted or your
> last comment is mandatory?
Pls do but you can make it a separate patch on top
if you prefer.
next prev parent reply other threads:[~2016-03-02 15:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 18:25 [Qemu-devel] [PATCH v8 0/4] i386: expose floppy-related objects in SSDT Roman Kagan
2016-02-17 18:25 ` [Qemu-devel] [PATCH v8 1/4] i386/acpi: make floppy controller object dynamic Roman Kagan
2016-02-17 18:25 ` [Qemu-devel] [PATCH v8 2/4] i386: expose floppy drive CMOS type Roman Kagan
2016-02-17 18:25 ` [Qemu-devel] [PATCH v8 3/4] fdc: add function to determine drive chs limits Roman Kagan
2016-02-17 20:15 ` Michael S. Tsirkin
2016-02-18 9:50 ` Roman Kagan
2016-02-18 10:01 ` Michael S. Tsirkin
2016-02-24 22:48 ` John Snow
2016-02-17 18:25 ` [Qemu-devel] [PATCH v8 4/4] i386: populate floppy drive information in DSDT Roman Kagan
2016-03-02 15:08 ` [Qemu-devel] [PATCH v8 0/4] i386: expose floppy-related objects in SSDT Denis V. Lunev
2016-03-02 15:10 ` Michael S. Tsirkin [this message]
2016-03-03 15:48 ` Roman Kagan
2016-03-03 18:29 ` Michael S. Tsirkin
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=20160302171039-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=den@openvz.org \
--cc=imammedo@redhat.com \
--cc=jsnow@redhat.com \
--cc=kevin@koconnor.net \
--cc=lersek@redhat.com \
--cc=marcel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.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 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).