From: Igor Mammedov <imammedo@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: rvkagan@yandex-team.ru, vkuznets@redhat.com,
mail@maciej.szmigiero.name, Jon Doron <arilou@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/3] hyperv: vmbus: ACPI various corrections
Date: Tue, 23 Jun 2020 16:57:41 +0200 [thread overview]
Message-ID: <20200623165741.5acc1dc6@redhat.com> (raw)
In-Reply-To: <e467716d-19cb-ffec-b464-494e975463e3@redhat.com>
On Tue, 23 Jun 2020 12:02:40 +0200
Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 17/06/20 18:09, Jon Doron wrote:
> > After doing further tests and looking at the latest HyperV ACPI DSDT.
> > Do minor fix to our VMBus ACPI entry.
> >
> > v2:
> > Renamed irq0 to irq now that there is a single IRQ required
> >
> > Jon Doron (3):
> > hyperv: vmbus: Remove the 2nd IRQ
> > i386: acpi: vmbus: Add _ADR definition
> > acpi: i386: Move VMBus DSDT entry to SB
> >
> > dtc | 2 +-
> > hw/hyperv/vmbus.c | 3 +--
> > hw/i386/acpi-build.c | 17 +++++++++--------
> > include/hw/hyperv/vmbus-bridge.h | 3 +--
> > 4 files changed, 12 insertions(+), 13 deletions(-)
> >
>
> Queued, thanks.
>
> Paolo
>
>
Paolo, there is a newer vesion on list
and I don't think _ADR patch should be applied at all
next prev parent reply other threads:[~2020-06-23 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 16:09 [PATCH v2 0/3] hyperv: vmbus: ACPI various corrections Jon Doron
2020-06-17 16:09 ` [PATCH v2 1/3] hyperv: vmbus: Remove the 2nd IRQ Jon Doron
2020-06-17 17:28 ` Philippe Mathieu-Daudé
2020-06-23 14:47 ` Igor Mammedov
2020-06-17 16:09 ` [PATCH v2 2/3] i386: acpi: vmbus: Add _ADR definition Jon Doron
2020-06-17 16:09 ` [PATCH v2 3/3] acpi: i386: Move VMBus DSDT entry to SB Jon Doron
2020-06-17 16:35 ` [PATCH v2 0/3] hyperv: vmbus: ACPI various corrections no-reply
2020-06-23 10:02 ` Paolo Bonzini
2020-06-23 14:57 ` Igor Mammedov [this message]
2020-06-23 15:44 ` Paolo Bonzini
2020-06-24 13:54 ` Igor Mammedov
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=20200623165741.5acc1dc6@redhat.com \
--to=imammedo@redhat.com \
--cc=arilou@gmail.com \
--cc=mail@maciej.szmigiero.name \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rvkagan@yandex-team.ru \
--cc=vkuznets@redhat.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).