From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [xen:stable/for-linus-3.8 4/8] include/xen/interface/version.h:72:2: error: implicit declaration of function 'xen_domain' Date: Wed, 28 Nov 2012 22:08:38 -0500 Message-ID: <20121129030838.GA22724@phenom.dumpdata.com> References: <50b68452.Gqr1L/cRkHFh1xmK%fengguang.wu@intel.com> <20121128221510.GA29950@phenom.dumpdata.com> <20121129022125.GG5785@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20121129022125.GG5785@localhost> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Fengguang Wu Cc: "Liu, Jinsong" , xen-devel@lists.xensource.com, Jan Beulich List-Id: xen-devel@lists.xenproject.org On Thu, Nov 29, 2012 at 10:21:25AM +0800, Fengguang Wu wrote: > On Wed, Nov 28, 2012 at 05:15:10PM -0500, Konrad Rzeszutek Wilk wrote: > > On Thu, Nov 29, 2012 at 05:38:26AM +0800, kbuild test robot wrote: > > > tree: git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-linus-3.8 > > > head: 394b40f62d7ae18a1c48c13fc483b8193f8c3a98 > > > commit: 92e3229dcdc80ff0b6304f14c578d76e7e10e226 [4/8] xen/acpi: ACPI PAD driver > > > config: x86_64-randconfig-x701 (attached as .config) > > > > > > Note: the xen/stable/for-linus-3.8 HEAD 394b40f builds fine. > > > It only hurts bisectibility. > > > > > > All error/warnings: > > > > > > In file included from drivers/xen/features.c:15:0: > > > include/xen/interface/version.h: In function 'xen_running_on_version_or_later': > > > include/xen/interface/version.h:72:2: error: implicit declaration of function 'xen_domain' [-Werror=implicit-function-declaration] > > > cc1: some warnings being treated as errors > > > > Which are fixed a bit later by me. > > Yes, see the above note: "HEAD 394b40f builds fine. It only hurts bisectibility." > > It still creates a range of not-bisectable commits due to the build > error. So the report was sent out, hoping that the branch can be > rebased to remove the error completely. > > However if you've decided that this tree won't do rebase at all, Not that one. The 'devel' ones are OK, but the 'stable' are .. well stable - with warts and all :-) > please let me know and I'll ignore such interim errors on it in > future. I think this is OK. I don't mind seeing such errors. > > Thanks, > Fengguang