qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	kvm-devel <kvm@vger.kernel.org>,
	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: Wed, 18 Sep 2013 07:51:49 +0300	[thread overview]
Message-ID: <20130918045149.GC5657@redhat.com> (raw)
In-Reply-To: <52391821.1050004@ozlabs.ru>

On Wed, Sep 18, 2013 at 01:04:01PM +1000, Alexey Kardashevskiy wrote:
> On 09/05/2013 04:07 PM, Paolo Bonzini wrote:
> > Il 05/09/2013 05:16, Alexey Kardashevskiy ha scritto:
> >>>>>> 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.
> >>>>
> >>>> It's a matter of keeping things bisectable.  If we can detect a
> >>>> breakage, we can first work around it, and then apply the header update.
> >>>>  And if we don't detect it, maintainers usually send pull requests when
> >>>> they have time to work on breakage caused by their patches.
> >>
> >> I can see the discussion but I do not see if anyone is going to pull this
> >> through any tree. Please, somebody, pull. Thanks.
> > 
> > It will go in through the KVM tree, probably sometime next week.
> 
> 
> It is pretty impressive how such a trivial patch is still on its way to the
> upstream :)
> 
It was applied long time ago
https://git.kernel.org/cgit/virt/kvm/qemu-kvm.git/commit/?h=uq/master&id=8c409e659bc1373fab49a277bb5dc71babb73551

Sync with qemu.git does not happen after every patch though. If you are
working on kvm parts using qemu-kvm.git uq/master branch will make sure
that you are working on most up to date kvm bits. If you work depends on
something that is not in qemu-kvm.git then let kvm maintainers know and
we will send pull request to Anthony earlier.

--
			Gleb.

  reply	other threads:[~2013-09-18  4:52 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
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 [this message]
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=20130918045149.GC5657@redhat.com \
    --to=gleb@redhat.com \
    --cc=aik@ozlabs.ru \
    --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).