From: John Snow <jsnow@redhat.com>
To: Max Reitz <mreitz@redhat.com>, Alberto Garcia <berto@igalia.com>,
qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
qemu-stable@nongnu.org, qemu-block@nongnu.org,
Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH for-2.6 0/2] Fix regression with the default naming of throttling groups
Date: Tue, 26 Jul 2016 14:09:41 -0400 [thread overview]
Message-ID: <32cb75ec-51fc-9898-516e-95c28f602225@redhat.com> (raw)
In-Reply-To: <3e44ef27-7c67-c4ac-dc66-e29306421a73@redhat.com>
On 07/26/2016 11:34 AM, Max Reitz wrote:
> On 26.07.2016 14:52, Alberto Garcia wrote:
>> On Fri, Jul 08, 2016 at 05:05:12PM +0300, Alberto Garcia wrote:
>>> Hi,
>>>
>>> Stefan reported this, this is a regression caused by commit
>>> efaa7c4eeb7490c6f37f3.
>>>
>>> I sent a separate series for the git master, this is the backport
>>> for QEMU v2.6.0.
>>
>> ping
>
> We don't have a tree for 2.6.0, do we? I thought it only got pulled in
> when the stable release is being prepared.
>
> Max
>
Yeah, we don't really have a 2.6-stable tree except for the brief period
of time that Michael Roth is working actively on the release.
Usually CCing qemu-stable is good enough.
--js
prev parent reply other threads:[~2016-07-26 18:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 14:05 [Qemu-devel] [PATCH for-2.6 0/2] Fix regression with the default naming of throttling groups Alberto Garcia
2016-07-08 14:05 ` [Qemu-devel] [PATCH for-2.6 1/2] blockdev: " Alberto Garcia
2016-07-08 14:38 ` Max Reitz
2016-07-08 14:05 ` [Qemu-devel] [PATCH for-2.6 2/2] qemu-iotests: Test " Alberto Garcia
2016-07-08 14:39 ` Max Reitz
2016-07-08 16:29 ` [Qemu-devel] [PATCH for-2.6 0/2] Fix regression with the default " Stefan Hajnoczi
2016-07-26 12:52 ` Alberto Garcia
2016-07-26 15:34 ` Max Reitz
2016-07-26 18:09 ` John Snow [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=32cb75ec-51fc-9898-516e-95c28f602225@redhat.com \
--to=jsnow@redhat.com \
--cc=berto@igalia.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=stefanha@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).