From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1VGspi-0000Uh-6L for mharc-qemu-trivial@gnu.org; Tue, 03 Sep 2013 11:47:58 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47890) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VGspa-0000Jt-Co for qemu-trivial@nongnu.org; Tue, 03 Sep 2013 11:47:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VGspR-0000b8-22 for qemu-trivial@nongnu.org; Tue, 03 Sep 2013 11:47:50 -0400 Received: from mail-pb0-f42.google.com ([209.85.160.42]:59462) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VGspQ-0000as-RU for qemu-trivial@nongnu.org; Tue, 03 Sep 2013 11:47:40 -0400 Received: by mail-pb0-f42.google.com with SMTP id un15so6185699pbc.1 for ; Tue, 03 Sep 2013 08:47:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=p85ACiKA9jCOy8jt0p6Ot+A6Q4U+soXj8zBTz2RW2g0=; b=l9Bhzuu5a8uILLFbUEYdT90xqZtR+xZOuyqD76akEQewZn5I0cm5gcC2RcwTpD+iCw 7ASVifzKmUrKD54/gNI13zzyMu8+PspJ4wRLMs7cHizWxl7g+pVPoxY8qB7Gev9mlL/a bgoOzGL37DGBeeIhRvd1FBUtdX4oXiQLGxxE5Xieh13VR7Abblrt6jLajajheazTl0GC yxRard1kdrkPPjw54Hu3MHPuRf30xezVjExECTo0uyKxQlesh5ggHnOF/Ds48P3NL10A fE/O01Liym6XwB/YXOo3XG1EC5RVcm0gNvA9pDOs6zPcHV0NZIx1vTTaOSUf+nQdYuac m3GA== X-Gm-Message-State: ALoCoQkIxAzKfgqj/bkIxj8KfLF40MaLknTdUzviDDlH1Iu4ykLWcio5lY6/KxzpYaxD606/cHui X-Received: by 10.66.26.194 with SMTP id n2mr9488303pag.151.1378223259931; Tue, 03 Sep 2013 08:47:39 -0700 (PDT) Received: from aik.ozlabs.ibm.com (60-242-102-4.tpgi.com.au. [60.242.102.4]) by mx.google.com with ESMTPSA id xn12sm24827543pac.12.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 03 Sep 2013 08:47:39 -0700 (PDT) Message-ID: <5226048E.2090004@ozlabs.ru> Date: Wed, 04 Sep 2013 01:47:26 +1000 From: Alexey Kardashevskiy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Peter Maydell References: <1378196857-27541-1-git-send-email-aik@ozlabs.ru> <5225AC9A.2090601@ozlabs.ru> <5225BD32.8030001@siemens.com> <52260025.3050704@ozlabs.ru> In-Reply-To: Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 209.85.160.42 Cc: kvm-devel , Gleb Natapov , QEMU Trivial , Jan Kiszka , Michael Tokarev , QEMU Developers , Paolo Bonzini Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] linux-headers: update to 3.11 X-BeenThere: qemu-trivial@nongnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Sep 2013 15:47:56 -0000 On 09/04/2013 01:34 AM, Peter Maydell wrote: > On 3 September 2013 16:28, Alexey Kardashevskiy 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 :-/ -- Alexey From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexey Kardashevskiy Subject: Re: [Qemu-devel] [PATCH] linux-headers: update to 3.11 Date: Wed, 04 Sep 2013 01:47:26 +1000 Message-ID: <5226048E.2090004@ozlabs.ru> References: <1378196857-27541-1-git-send-email-aik@ozlabs.ru> <5225AC9A.2090601@ozlabs.ru> <5225BD32.8030001@siemens.com> <52260025.3050704@ozlabs.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , QEMU Developers , QEMU Trivial , Michael Tokarev , Gleb Natapov , Paolo Bonzini , kvm-devel To: Peter Maydell Return-path: Received: from mail-pb0-f54.google.com ([209.85.160.54]:64857 "EHLO mail-pb0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755386Ab3ICPrk (ORCPT ); Tue, 3 Sep 2013 11:47:40 -0400 Received: by mail-pb0-f54.google.com with SMTP id ro12so6138924pbb.41 for ; Tue, 03 Sep 2013 08:47:40 -0700 (PDT) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 09/04/2013 01:34 AM, Peter Maydell wrote: > On 3 September 2013 16:28, Alexey Kardashevskiy 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 :-/ -- Alexey From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47869) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VGspX-0000FZ-6A for qemu-devel@nongnu.org; Tue, 03 Sep 2013 11:47:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VGspR-0000b3-0s for qemu-devel@nongnu.org; Tue, 03 Sep 2013 11:47:47 -0400 Received: from mail-pb0-f49.google.com ([209.85.160.49]:57381) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VGspQ-0000at-Pl for qemu-devel@nongnu.org; Tue, 03 Sep 2013 11:47:40 -0400 Received: by mail-pb0-f49.google.com with SMTP id xb4so6125895pbc.36 for ; Tue, 03 Sep 2013 08:47:40 -0700 (PDT) Message-ID: <5226048E.2090004@ozlabs.ru> Date: Wed, 04 Sep 2013 01:47:26 +1000 From: Alexey Kardashevskiy MIME-Version: 1.0 References: <1378196857-27541-1-git-send-email-aik@ozlabs.ru> <5225AC9A.2090601@ozlabs.ru> <5225BD32.8030001@siemens.com> <52260025.3050704@ozlabs.ru> In-Reply-To: Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] linux-headers: update to 3.11 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: kvm-devel , Gleb Natapov , QEMU Trivial , Jan Kiszka , Michael Tokarev , QEMU Developers , Paolo Bonzini On 09/04/2013 01:34 AM, Peter Maydell wrote: > On 3 September 2013 16:28, Alexey Kardashevskiy 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 :-/ -- Alexey