From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Steven Rostedt <srostedt@redhat.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (tty tree related)
Date: Thu, 13 Dec 2012 15:38:35 -0800 [thread overview]
Message-ID: <20121213233835.GA515@kroah.com> (raw)
In-Reply-To: <20121214103256.ce307015fd09961ad82346f9@canb.auug.org.au>
On Fri, Dec 14, 2012 at 10:32:56AM +1100, Stephen Rothwell wrote:
> Hi Steve, Greg,
>
> On Tue, 27 Nov 2012 10:05:30 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Mon, 26 Nov 2012 09:35:12 -0500 Steven Rostedt <srostedt@redhat.com> wrote:
> > >
> > > On Tue, 2012-11-27 at 00:49 +1100, Stephen Rothwell wrote:
> > > >
> > > > After merging the final tree, today's linux-next build (powerpc
> > > > allyesconfig) failed like this:
> > > >
> > > > In file included from drivers/staging/sb105x/sb_pci_mp.c:1:0:
> > > > drivers/staging/sb105x/sb_pci_mp.h:22:25: fatal error: asm/segment.h: No such file or directory
> > >
> > > I haven't tested this with any other arch than x86. That said, what
> > > about this instead:
> > >
> > > > Caused by commit 68a81291ff66 ("staging: Add SystemBase Multi-2/PCI
> > > > driver").
> > > >
> > > > I have disabled this driver with this patch:
> > > >
> > > > From: Stephen Rothwell <sfr@canb.auug.org.au>
> > > > Date: Tue, 27 Nov 2012 00:45:07 +1100
> > > > Subject: [PATCH] disable the SB105X driver
> > > >
> > > > Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> > > > ---
> > > > drivers/staging/sb105x/Kconfig | 1 +
> > > > 1 file changed, 1 insertion(+)
> > > >
> > > > diff --git a/drivers/staging/sb105x/Kconfig b/drivers/staging/sb105x/Kconfig
> > > > index ac87c5e..c957e32 100644
> > > > --- a/drivers/staging/sb105x/Kconfig
> > > > +++ b/drivers/staging/sb105x/Kconfig
> > > > @@ -2,6 +2,7 @@ config SB105X
> > > > tristate "SystemBase PCI Multiport UART"
> > > > select SERIAL_CORE
> > > > depends on PCI
> > > > + depends on BROKEN
> > >
> > > depends on X86
> > >
> > > You can add my SOB if you want. I don't care either way.
> >
> > Please just send a (tested) patch to Greg.
>
> This now breaks Linus' tree .....
Ugh, can someone send me a patch to forward to Linus to fix this please?
Steven, how about fixing the problem properly?
thanks,
greg k-h
next prev parent reply other threads:[~2012-12-13 23:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 13:49 linux-next: build failure after merge of the final tree (tty tree related) Stephen Rothwell
2012-11-26 14:35 ` Steven Rostedt
2012-11-26 23:05 ` Stephen Rothwell
2012-12-13 23:32 ` Stephen Rothwell
2012-12-13 23:38 ` Greg KH [this message]
2012-12-14 0:11 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2013-10-28 14:33 Stephen Rothwell
2013-10-28 14:49 ` Michal Simek
2013-10-28 16:05 ` Sören Brinkmann
2013-10-28 16:33 ` Greg KH
2013-10-29 7:04 ` Stephen Rothwell
2013-09-27 8:21 Stephen Rothwell
2013-09-28 1:04 ` Greg KH
2013-04-02 7:57 Stephen Rothwell
2012-09-24 14:36 Stephen Rothwell
2012-09-25 22:41 ` Greg KH
2012-07-20 5:02 Stephen Rothwell
2012-07-25 22:47 ` Greg KH
2012-07-26 0:23 ` Alan Cox
2012-07-25 22:52 ` Stephen Rothwell
2011-08-25 6:18 Stephen Rothwell
2011-08-25 14:08 ` Greg KH
2011-08-25 14:28 ` Timur Tabi
2011-08-25 15:22 ` Timur Tabi
2011-08-25 15:51 ` Stephen Rothwell
2011-08-25 16:09 ` Arnaud Lacombe
2011-08-26 0:39 ` Stephen Rothwell
2011-08-26 15:47 ` Arnaud Lacombe
2011-09-11 4:23 ` Stephen Rothwell
2011-09-11 9:05 ` Geert Uytterhoeven
2010-12-17 6:11 Stephen Rothwell
2010-12-17 7:04 ` Greg KH
2010-12-17 10:16 ` Thomas Gleixner
2011-01-06 3:27 ` Stephen Rothwell
2011-01-06 18:45 ` Greg KH
2010-11-12 1:57 Stephen Rothwell
2010-11-12 10:44 ` Alan Cox
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=20121213233835.GA515@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=srostedt@redhat.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).