linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	xen-devel@lists.xensource.com,
	LKML <linux-kernel@vger.kernel.org>,
	virtualization@lists.linux-foundation.org,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-next@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Ingo Molnar <mingo@elte.hu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Xen-devel] Re: linux-next: Tree for July 25 (xen)
Date: Thu, 4 Aug 2011 18:30:18 -0400	[thread overview]
Message-ID: <20110804223018.GA4370@dumpdata.com> (raw)
In-Reply-To: <20110804131516.c4da6595.rdunlap@xenotime.net>

> > >  arch/x86/xen/trace.c:44:2: error: array index in initializer not of integer type
> > >  arch/x86/xen/trace.c:44:2: error: (near initialization for ‘xen_hypercall_names’)
> > >  arch/x86/xen/trace.c:45:1: error: ‘__HYPERVISOR_arch_4’ undeclared here (not in a function)
> > >  arch/x86/xen/trace.c:45:2: error: array index in initializer not of integer type
> > >  arch/x86/xen/trace.c:45:2: error: (near initialization for ‘xen_hypercall_names’)
> > 
> > Oh, that I haven't seen. Can you send me the .config for that please.
> 
> You can't be trying very hard then.  I see lots of these (but no,

Hm, It is not obvious to me what is causing that compile failure. Any ideas?

> I haven't reported them.  One can grow weary of reporting xen bugs.)
> 
> 
> > > even after:
> > > 
> > >  b3c4b9825075: xen/tracing: fix compile errors when tracing is disabled.
> > > 
> > > Btw., that the heck is going on with the commit that introduced the 
> > > build failure:
> > > 
> > >  commit bd9ddc875b6659f9f74dcfd285c472bc58041abd
> > >  Author:     Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> > >  AuthorDate: Mon Jun 20 17:52:13 2011 -0700
> > >  Commit:     Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> > >  CommitDate: Mon Jul 18 15:43:46 2011 -0700
> > > 
> > > It was apparently rebased shortly before the merge window and sent to 
> > 
> > Well, the rebase I get - it was done on top of the merge that introduced
> > the new functionality.
> > 
> > > Linus 3 days later, with little to no linux-next testing ...
> > 
> > <Hmm> It did fix the compile problem.. albeit it created another one.
> > > 
> > > I'm absolutely unhappy about how the Xen tree is being run. It's 
> > > using a sloppy, crappy workflow and it is producing crap.
> > 
> > Do you have a manual of how you guys run your workflow?
> 
> I just run 30-50 randconfigs per night (cron job).

Ok, do you have an mailing list where you send the output too?

  reply	other threads:[~2011-08-04 22:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25  6:25 linux-next: Tree for July 25 Stephen Rothwell
2011-07-25 16:19 ` [PATCH -next] watchdog: fix it8712f_wdt build errors Randy Dunlap
2011-07-25 19:02   ` Wim Van Sebroeck
2011-07-25 18:01 ` [PATCH -next] kvm: fix TASK_DELAY_ACCT kconfig warning Randy Dunlap
2011-07-27 11:19   ` Avi Kivity
2011-07-25 21:46 ` linux-next: Tree for July 25 (xen) Randy Dunlap
2011-08-04 19:35   ` Ingo Molnar
2011-08-04 19:55     ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-08-04 20:15       ` Randy Dunlap
2011-08-04 22:30         ` Konrad Rzeszutek Wilk [this message]
2011-08-04 23:22           ` [Xen-devel] " Randy Dunlap
2011-08-04 22:32         ` Konrad Rzeszutek Wilk
2011-08-04 22:40           ` Konrad Rzeszutek Wilk
2011-08-04 23:24             ` Randy Dunlap
2011-08-04 23:53             ` Randy Dunlap
2011-08-05  8:05               ` Ingo Molnar
2011-08-05 21:14                 ` Ingo Molnar
2011-08-06  1:58                   ` Konrad Rzeszutek Wilk
2011-08-06  7:04                     ` Stephen Rothwell
2011-08-06 18:22                     ` Jeremy Fitzhardinge
2011-08-08 13:01                       ` Steven Rostedt
2011-08-10 16:49                         ` Jeremy Fitzhardinge

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=20110804223018.GA4370@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=jeremy.fitzhardinge@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rdunlap@xenotime.net \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xen-devel@lists.xensource.com \
    /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).