public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "J.R. Mauro" <jrm8005@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Can you add the staging tree to -next?
Date: Fri, 14 Nov 2008 15:06:37 -0800	[thread overview]
Message-ID: <20081114230637.GA1415@kroah.com> (raw)
In-Reply-To: <3aaafc130811141428ta97f929va8c62cbcdbc731f7@mail.gmail.com>

On Fri, Nov 14, 2008 at 05:28:17PM -0500, J.R. Mauro wrote:
> There also seem to be a lot of build errors that no one hacking on
> staging has seen before being threshed out by all the randconfig tests
> done on -next, which will help a lot if we want the staging drivers to
> actually go anywhere.

In looking at these in some detail, the majority of them are due to api
changes in other trees, so these changes will have to be done during the
-rc1 merge window, which shouldn't be that big of an issue.

But yes, there are some kconfig dependancies as well, Randy is really
good at finding them :)  If you want to send me patches to fix these,
I'd appreciate it.

thanks,

greg k-h

  reply	other threads:[~2008-11-14 23:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 23:56 Can you add the staging tree to -next? Greg KH
2008-11-13 23:44 ` Stephen Rothwell
2008-11-14  0:01   ` Greg KH
2008-11-14  0:13     ` J.R. Mauro
2008-11-14  0:22       ` Greg KH
2008-11-14  0:25         ` J.R. Mauro
2008-11-14  7:42 ` Geert Uytterhoeven
2008-11-14  7:50   ` Stephen Rothwell
2008-11-14 14:16     ` Geert Uytterhoeven
2008-11-14 17:32   ` Greg KH
2008-11-14 22:28     ` J.R. Mauro
2008-11-14 23:06       ` Greg KH [this message]
2008-11-14 23:43         ` J.R. Mauro
2008-11-18 18:36     ` Stefan Richter

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=20081114230637.GA1415@kroah.com \
    --to=greg@kroah.com \
    --cc=geert@linux-m68k.org \
    --cc=jrm8005@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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