From: Alex Williamson <alex.williamson@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Peter Maydell <peter.maydell@linaro.org>,
kvm-devel <kvm@vger.kernel.org>, Gleb Natapov <gleb@redhat.com>,
QEMU Trivial <qemu-trivial@nongnu.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Michael Tokarev <mjt@tls.msk.ru>,
QEMU Developers <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] linux-headers: update to 3.11
Date: Tue, 03 Sep 2013 09:58:32 -0600 [thread overview]
Message-ID: <1378223912.3246.36.camel@ul30vt.home> (raw)
In-Reply-To: <5226048E.2090004@ozlabs.ru>
On Wed, 2013-09-04 at 01:47 +1000, Alexey Kardashevskiy wrote:
> On 09/04/2013 01:34 AM, Peter Maydell wrote:
> > On 3 September 2013 16:28, Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
> >> On 09/03/2013 08:42 PM, Jan Kiszka wrote:
> >>> This shouldn't be routed through trivial in general as things broke too
> >>> often in this area.
> >>
> >>
> >> Sorry for my ignorance, but this is The Kernel, it is already there, broken
> >> or not, even if it is broken, qemu cannot stay isolated, no?
> >> This is a mechanical change, no more.
> >
> > The classic way for things to break is that a header
> > update accidentally reverts something (because a
> > previous update was from kvm-next and this one is
> > from mainline, for example). Accidental updates against
> > a kernel which is neither kvm-next nor mainline are
> > the other common "broken" version of a header update
> > patch.
>
> I can understand that but this update is a mainline kernel update and it is
> not an accidental one but very specific :-/
I was under the impression that we were only ever updating linux-headers
from mainline, never from kvm-next. Therefore any mainline tag should
be a reasonable re-base target. Thanks,
Alex
next prev parent reply other threads:[~2013-09-03 15:58 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 [this message]
2013-09-03 16:03 ` Peter Maydell
2013-09-03 16:12 ` Alex Williamson
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=1378223912.3246.36.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).