[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120321095317.0c142913@pyramind.ukuu.org.uk>
Date: Wed, 21 Mar 2012 09:53:17 +0000
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Greg KH <greg@...ah.com>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Alan Cox <alan@...ux.intel.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: linux-next: build failure after merge of the tip tree
On Wed, 21 Mar 2012 09:00:38 +1100
Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> On Thu, 8 Mar 2012 10:00:48 -0800 Greg KH <greg@...ah.com> wrote:
> >
> > On Thu, Mar 08, 2012 at 03:21:10PM +1100, Stephen Rothwell wrote:
> > >
> > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> > > failed like this:
> > >
> > > drivers/staging/sep/sep_driver.c:55:32: fatal error: linux/rar_register.h: No such file or directory
> > >
> > > Caused by commit 33e9970add94 ("x86/mid: Kill off Moorestown").
> > >
> > > Following previous instructions, I have disabled the staging tree driver
> > > using this patch (pending a fix in the tip tree):
> >
> > Looks good to me. Alan, care to send me an update that fixes this
> > driver for real?
>
> Was this ever fixed?
I thought it was but apparently it got lost or I dropped the ball. I'll
sort it once git.kernel.org is back and I can pull a currentish -next
tree.
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists