From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [ANNOUNCE] kvm-kmod-2.6.31.5 Date: Wed, 28 Oct 2009 13:41:28 +0100 Message-ID: <4AE83BF8.9060801@siemens.com> References: <4AE5DBB5.9050306@siemens.com> <90D306BE6EBC8D428A824FBBA7A3113D012F07D55A@ronja.maurer-it.com> <4AE83131.6020306@siemens.com> <90D306BE6EBC8D428A824FBBA7A3113D012F07D55C@ronja.maurer-it.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: kvm To: Dietmar Maurer Return-path: Received: from goliath.siemens.de ([192.35.17.28]:19017 "EHLO goliath.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751040AbZJ1Ml1 (ORCPT ); Wed, 28 Oct 2009 08:41:27 -0400 In-Reply-To: <90D306BE6EBC8D428A824FBBA7A3113D012F07D55C@ronja.maurer-it.com> Sender: kvm-owner@vger.kernel.org List-ID: Dietmar Maurer wrote: >>> So I can simply skip 'make sync'? >> The release tarball contains all required sources (as described, they >> were obtained from 2.6.31.5). So you do have to sync, > > So I need to run 'make sync'? Ouch. Of course I meant "you do *not* have to sync". Practically, there is no reason to re-sync when you have the release tarball in hands. 'make sync' is a developer tool when working with the git version of kvm-kmod and/or dragging in brand new kvm kernel sources. Sorry for the confusion. Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux