All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Paolo Bonzini <pbonzini@redhat.com>
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>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] linux-headers: update to 3.11
Date: Wed, 18 Sep 2013 13:04:01 +1000	[thread overview]
Message-ID: <52391821.1050004@ozlabs.ru> (raw)
In-Reply-To: <52281F93.4070805@redhat.com>

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 :)


-- 
Alexey


WARNING: multiple messages have this Message-ID (diff)
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	QEMU Trivial <qemu-trivial@nongnu.org>,
	Michael Tokarev <mjt@tls.msk.ru>, Gleb Natapov <gleb@redhat.com>,
	kvm-devel <kvm@vger.kernel.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [Qemu-devel] [PATCH] linux-headers: update to 3.11
Date: Wed, 18 Sep 2013 13:04:01 +1000	[thread overview]
Message-ID: <52391821.1050004@ozlabs.ru> (raw)
In-Reply-To: <52281F93.4070805@redhat.com>

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 :)


-- 
Alexey

WARNING: multiple messages have this Message-ID (diff)
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Paolo Bonzini <pbonzini@redhat.com>
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>
Subject: Re: [Qemu-devel] [PATCH] linux-headers: update to 3.11
Date: Wed, 18 Sep 2013 13:04:01 +1000	[thread overview]
Message-ID: <52391821.1050004@ozlabs.ru> (raw)
In-Reply-To: <52281F93.4070805@redhat.com>

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 :)


-- 
Alexey

  reply	other threads:[~2013-09-18  3:04 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03  8:27 [Qemu-trivial] [PATCH] linux-headers: update to 3.11 Alexey Kardashevskiy
2013-09-03  8:27 ` [Qemu-devel] " Alexey Kardashevskiy
2013-09-03  9:29 ` [Qemu-trivial] " Peter Maydell
2013-09-03  9:29   ` Peter Maydell
2013-09-03  9:29   ` Peter Maydell
2013-09-03  9:32   ` [Qemu-trivial] " Alexey Kardashevskiy
2013-09-03  9:32     ` Alexey Kardashevskiy
2013-09-03  9:32     ` Alexey Kardashevskiy
2013-09-03 10:42     ` [Qemu-trivial] " Jan Kiszka
2013-09-03 10:42       ` Jan Kiszka
2013-09-03 10:42       ` Jan Kiszka
2013-09-03 15:28       ` [Qemu-trivial] " Alexey Kardashevskiy
2013-09-03 15:28         ` Alexey Kardashevskiy
2013-09-03 15:28         ` Alexey Kardashevskiy
2013-09-03 15:34         ` [Qemu-trivial] " Peter Maydell
2013-09-03 15:34           ` Peter Maydell
2013-09-03 15:34           ` Peter Maydell
2013-09-03 15:47           ` [Qemu-trivial] " Alexey Kardashevskiy
2013-09-03 15:47             ` Alexey Kardashevskiy
2013-09-03 15:47             ` Alexey Kardashevskiy
2013-09-03 15:55             ` [Qemu-trivial] " Peter Maydell
2013-09-03 15:55               ` Peter Maydell
2013-09-03 15:55               ` Peter Maydell
2013-09-03 15:58             ` [Qemu-trivial] " Alex Williamson
2013-09-03 15:58               ` Alex Williamson
2013-09-03 15:58               ` Alex Williamson
2013-09-03 16:03               ` [Qemu-trivial] " Peter Maydell
2013-09-03 16:03                 ` Peter Maydell
2013-09-03 16:03                 ` Peter Maydell
2013-09-03 16:12                 ` [Qemu-trivial] " Alex Williamson
2013-09-03 16:12                   ` Alex Williamson
2013-09-03 16:12                   ` Alex Williamson
2013-09-03 15:35         ` [Qemu-trivial] " Paolo Bonzini
2013-09-03 15:35           ` Paolo Bonzini
2013-09-03 15:35           ` Paolo Bonzini
2013-09-05  3:16           ` [Qemu-trivial] " Alexey Kardashevskiy
2013-09-05  3:16             ` Alexey Kardashevskiy
2013-09-05  3:16             ` Alexey Kardashevskiy
2013-09-05  6:07             ` [Qemu-trivial] " Paolo Bonzini
2013-09-05  6:07               ` Paolo Bonzini
2013-09-05  6:07               ` Paolo Bonzini
2013-09-18  3:04               ` Alexey Kardashevskiy [this message]
2013-09-18  3:04                 ` Alexey Kardashevskiy
2013-09-18  3:04                 ` Alexey Kardashevskiy
2013-09-18  4:51                 ` [Qemu-trivial] " Gleb Natapov
2013-09-18  4:51                   ` Gleb Natapov
2013-09-18  4:51                   ` Gleb Natapov
2013-09-12 16:31 ` [Qemu-trivial] " Paolo Bonzini
2013-09-12 16:31   ` [Qemu-devel] " 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=52391821.1050004@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=benh@kernel.crashing.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.