qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] virtio: Notice when the system doesn't support MSIx at all
Date: Mon, 26 Oct 2015 13:08:42 +0200	[thread overview]
Message-ID: <20151026130644-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <562E04D4.8070502@ilande.co.uk>

On Mon, Oct 26, 2015 at 10:47:48AM +0000, Mark Cave-Ayland wrote:
> On 26/10/15 10:14, Peter Maydell wrote:
> 
> > On 26 October 2015 at 10:09, Mark Cave-Ayland
> > <mark.cave-ayland@ilande.co.uk> wrote:
> >> On 26/10/15 10:03, Michael S. Tsirkin wrote:
> >>> Pls address the issues if you want this applied.
> >>
> >> The patch came from Richard rather than myself - my only involvement has
> >> been to champion the patch since both myself and Peter have had reports
> >> of this message confusing users.
> > 
> > Isn't this patch already in master as commit 0d583647a7fc73f6 ?
> 
> Oh I think you're right! I had that thread tagged and hadn't seen a
> reply come through, but I guess Richard must have attached it to one of
> his recent pull requests.

I did. I don't do replies, I merge patches then change my mind and drop
them too many times to make "applied thanks" work.  As I send pulls
about once a week, and Cc contributors, you only need to watch these to
know whether stuff is merged.


> In that case apologies to all for the noise.
> 
> 
> ATB,
> 
> Mark.

  reply	other threads:[~2015-10-26 11:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 15:54 [Qemu-devel] virtio-pci msix error Richard Henderson
2015-05-19 19:16 ` Michael S. Tsirkin
2015-05-19 20:11   ` Peter Maydell
2015-05-19 20:29     ` [Qemu-devel] [PATCH] virtio: Notice when the system doesn't support MSIx at all Richard Henderson
2015-05-20  9:59       ` Michael S. Tsirkin
2015-05-20 15:10         ` Richard Henderson
2015-05-21 18:51           ` Mark Cave-Ayland
2015-07-03  8:22       ` Mark Cave-Ayland
2015-07-06 10:38         ` Peter Maydell
2015-09-27 14:40           ` Peter Maydell
2015-10-26  9:44             ` Mark Cave-Ayland
2015-10-26 10:03               ` Michael S. Tsirkin
2015-10-26 10:09                 ` Mark Cave-Ayland
2015-10-26 10:14                   ` Peter Maydell
2015-10-26 10:29                     ` Michael S. Tsirkin
2015-10-26 10:47                     ` Mark Cave-Ayland
2015-10-26 11:08                       ` Michael S. Tsirkin [this message]
2015-05-20  9:58     ` [Qemu-devel] virtio-pci msix error Michael S. Tsirkin
2015-05-20 10:41       ` Peter Maydell
2015-05-20 11:55         ` Fam Zheng
2015-05-20 12:10           ` Peter Maydell
2015-06-13 15:06             ` Mark Cave-Ayland
2015-07-03  8:13               ` Mark Cave-Ayland
2015-07-03  8:16                 ` Peter Maydell
2015-07-03  8:19                   ` Mark Cave-Ayland

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=20151026130644-mutt-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).