linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for December 2 (staging)
Date: Tue, 2 Dec 2008 11:29:52 -0800	[thread overview]
Message-ID: <20081202192952.GA2329@kroah.com> (raw)
In-Reply-To: <49357AD0.7090005@oracle.com>

On Tue, Dec 02, 2008 at 10:13:36AM -0800, Randy Dunlap wrote:
> Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20081201:
> > 
> > Today's tree fails the powerpc allyesconfig build.
> 
> Greg,
> FYI, the staging drivers still have lots of errors (as reported
> over 1 week ago; yes, I know, holiday time), but I've stopped reporting
> on them until I see some reason to think that fixes have been made.

I've fixed the errors that I can in my tree.  The majority of the errors
you are seeing are ones that are caused by api changes in other trees
that I can't fix up now in -staging until those changes go into Linus's
tree.

Which is fine, I'll fix them up when I push them to Linus, so you don't
have to worry about them.

Some of the other warnings are just due to horrible code, like the
drivers/staging/otus/ driver that has some looney macros that cause lots
of build warnings.  Those will take more work and I'm hoping that the
community of developers that have been helping out with the staging tree
will help there.

thanks,

greg k-h

  reply	other threads:[~2008-12-02 19:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02  6:31 linux-next: Tree for December 2 Stephen Rothwell
2008-12-02 17:57 ` linux-next: Tree for December 2 (mfd) Randy Dunlap
2008-12-03 14:20   ` Kamalesh Babulal
2008-12-02 18:13 ` linux-next: Tree for December 2 (staging) Randy Dunlap
2008-12-02 19:29   ` Greg KH [this message]
2008-12-03 21:19     ` Randy Dunlap
2008-12-04  4:38       ` 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=20081202192952.GA2329@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    /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).