From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 0/9] pci, virtio, vhost: fixes
Date: Thu, 18 May 2017 00:40:01 +0300 [thread overview]
Message-ID: <20170518003940-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20170515160256-mutt-send-email-mst@kernel.org>
On Mon, May 15, 2017 at 04:04:33PM +0300, Michael S. Tsirkin wrote:
> On Mon, May 15, 2017 at 01:58:40PM +0100, Stefan Hajnoczi wrote:
> > On Wed, May 10, 2017 at 10:07:58PM +0300, Michael S. Tsirkin wrote:
> > > The following changes since commit 76d20ea0f1b26ebd5da2f5fb2fdf3250cde887bb:
> > >
> > > Merge remote-tracking branch 'armbru/tags/pull-qapi-2017-05-04-v3' into staging (2017-05-09 15:49:14 -0400)
> > >
> > > are available in the git repository at:
> > >
> > > git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_upstream
> > >
> > > for you to fetch changes up to 8b12e48950a3d59188489b2ff6c5ad9cc09e9866:
> > >
> > > acpi-defs: clean up open brace usage (2017-05-10 22:04:23 +0300)
> > >
> > > ----------------------------------------------------------------
> > > pci, virtio, vhost: fixes
> > >
> > > A bunch of fixes that missed the release.
> > >
> > > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> >
> > Please resend with the checkpatch.pl issue fixed.
>
>
> There's no issue - new patch followed surrounding code which
> was not refactored to match checkpatch.
> Last patch of the series refactors all of that file to match.
>
> We do not need to worry abut bisect for checkpatch issues IMHO.
Ping - is this going to get merged? I'm preparing the next pull request
meanwhile ...
> --
> MST
next prev parent reply other threads:[~2017-05-17 21:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 19:07 [Qemu-devel] [PULL 0/9] pci, virtio, vhost: fixes Michael S. Tsirkin
2017-05-10 19:07 ` [Qemu-devel] [PULL 1/9] hw/acpi-defs: replace leading X with x_ in FADT field names Michael S. Tsirkin
2017-05-10 19:08 ` [Qemu-devel] [PULL 2/9] hw/arm/virt: generate 64-bit addressable ACPI objects Michael S. Tsirkin
2017-05-10 19:08 ` [Qemu-devel] [PULL 3/9] hw/virtio: fix vhost user fails to startup when MQ Michael S. Tsirkin
2017-05-10 19:08 ` [Qemu-devel] [PULL 4/9] libvhost-user: fix crash when rings aren't ready Michael S. Tsirkin
2017-05-10 19:08 ` [Qemu-devel] [PULL 5/9] pc/fwcfg: unbreak migration from qemu-2.5 and qemu-2.6 during firmware boot Michael S. Tsirkin
2017-05-10 19:08 ` [Qemu-devel] [PULL 6/9] pc: add 2.10 machine type Michael S. Tsirkin
2017-05-10 19:08 ` [Qemu-devel] [PULL 7/9] iommu: Don't crash if machine is not PC_MACHINE Michael S. Tsirkin
2017-05-10 19:08 ` [Qemu-devel] [PULL 8/9] ACPI: don't call acpi_pcihp_device_plug_cb on xen Michael S. Tsirkin
2017-05-10 19:08 ` [Qemu-devel] [PULL 9/9] acpi-defs: clean up open brace usage Michael S. Tsirkin
2017-05-10 19:48 ` [Qemu-devel] [PULL 0/9] pci, virtio, vhost: fixes no-reply
2017-05-15 12:58 ` Stefan Hajnoczi
2017-05-15 13:04 ` Michael S. Tsirkin
2017-05-17 21:40 ` Michael S. Tsirkin [this message]
2017-05-18 9:02 ` Stefan Hajnoczi
2017-05-18 9:02 ` Stefan Hajnoczi
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=20170518003940-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).