linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: brudley@broadcom.com, henryp@broadcom.com, rvossen@broadcom.com,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: build failure after merge of the final tree (staging related)
Date: Mon, 27 Jun 2011 14:45:47 -0700	[thread overview]
Message-ID: <20110627214547.GA10889@kroah.com> (raw)
In-Reply-To: <20110624100005.f9f59ddf.sfr@canb.auug.org.au>

On Fri, Jun 24, 2011 at 10:00:05AM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> On Thu, 23 Jun 2011 14:51:15 -0700 Greg KH <greg@kroah.com> wrote:
> >
> > Sorry, I'm away from home, with a very spotty internet connection, on
> > vacation, so it's hard to get this done at the moment.  I'll get to it
> > on the 27th when I return.
> 
> I can understand vacation as well :-)
> 
> Thanks.  I will use Ralf's (arch restricting) patch until you come up
> with something better.

That's good, but it doesn't fix the root problem here.  I've now fixed
this up in the staging-linus branch.

You shouldn't have any more build breakages in the drivers/staging/*
tree now as I am pretty sure I've fixed all reported issues.  If not,
please let me know.

thanks,

greg k-h

  reply	other threads:[~2011-06-27 21:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09  7:27 linux-next: build failure after merge of the final tree (staging related) Stephen Rothwell
2011-06-09 18:41 ` Greg KH
2011-06-09 19:22   ` Greg KH
2011-06-10  6:05     ` Stephen Rothwell
2011-06-10  6:09       ` Stephen Rothwell
2011-06-10 22:34         ` Greg KH
2011-06-15  4:21           ` Stephen Rothwell
2011-06-16 19:14             ` Greg KH
2011-06-23  0:35               ` Stephen Rothwell
2011-06-23 21:51                 ` Greg KH
2011-06-24  0:00                   ` Stephen Rothwell
2011-06-27 21:45                     ` Greg KH [this message]
2011-06-28  0:16                       ` Stephen Rothwell
2011-06-15 12:05       ` Geert Uytterhoeven
2011-06-15 15:47         ` Greg KH
2011-06-15 14:35       ` [PATCH] arch/tile: remove useless set_fixmap_nocache() macro Chris Metcalf
2011-06-09 19:52   ` linux-next: build failure after merge of the final tree (staging related) Henry Ptasinski
2011-06-09 20:19     ` Greg KH

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=20110627214547.GA10889@kroah.com \
    --to=greg@kroah.com \
    --cc=brudley@broadcom.com \
    --cc=henryp@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rvossen@broadcom.com \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    /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).