From: Alex Williamson <alex.williamson@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: kvm-devel <kvm@vger.kernel.org>, Gleb Natapov <gleb@redhat.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
Jan Kiszka <jan.kiszka@siemens.com>,
Michael Tokarev <mjt@tls.msk.ru>,
QEMU Developers <qemu-devel@nongnu.org>,
QEMU Trivial <qemu-trivial@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] linux-headers: update to 3.11
Date: Tue, 03 Sep 2013 10:12:40 -0600 [thread overview]
Message-ID: <1378224760.3246.45.camel@ul30vt.home> (raw)
In-Reply-To: <CAFEAcA_MN9jv3QnHGm1785kp2aqKgO1k-R_3QmR39094FbwsZQ@mail.gmail.com>
On Tue, 2013-09-03 at 17:03 +0100, Peter Maydell wrote:
> On 3 September 2013 16:58, Alex Williamson <alex.williamson@redhat.com> wrote:
> > I was under the impression that we were only ever updating linux-headers
> > from mainline, never from kvm-next.
>
> Looking at the git history, it's variable. Four of the
> last 10 updates were from somewhere other than mainline.
> In any case this is the kind of policy decision that
> means updates should go via the QEMU KVM maintainers :-)
Seems like every update except ppc has come from mainline. Personally,
I don't think it makes sense anymore. QEMU has scope beyond KVM and it
makes about as much sense to snapshot kvm.git as it does to snapshot my
vfio next branch or Michael's virtio queue. If we only pull from
mainline we never have to worry about regressing something that isn't
actually upstream yet. Thanks,
Alex
next prev parent reply other threads:[~2013-09-03 16:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 8:27 [Qemu-devel] [PATCH] linux-headers: update to 3.11 Alexey Kardashevskiy
2013-09-03 9:29 ` Peter Maydell
2013-09-03 9:32 ` Alexey Kardashevskiy
2013-09-03 10:42 ` Jan Kiszka
2013-09-03 15:28 ` Alexey Kardashevskiy
2013-09-03 15:34 ` Peter Maydell
2013-09-03 15:47 ` Alexey Kardashevskiy
2013-09-03 15:55 ` Peter Maydell
2013-09-03 15:58 ` Alex Williamson
2013-09-03 16:03 ` Peter Maydell
2013-09-03 16:12 ` Alex Williamson [this message]
2013-09-03 15:35 ` Paolo Bonzini
2013-09-05 3:16 ` Alexey Kardashevskiy
2013-09-05 6:07 ` Paolo Bonzini
2013-09-18 3:04 ` Alexey Kardashevskiy
2013-09-18 4:51 ` Gleb Natapov
2013-09-12 16:31 ` Paolo Bonzini
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=1378224760.3246.45.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=aik@ozlabs.ru \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
/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).