From: Randy Dunlap <randy.dunlap@oracle.com>
To: Greg KH <gregkh@suse.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Rusty Russell <rusty@rustcorp.com.au>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for November 23
Date: Mon, 23 Nov 2009 15:42:10 -0800 [thread overview]
Message-ID: <4B0B1DD2.9000404@oracle.com> (raw)
In-Reply-To: <20091123233843.GA13464@suse.de>
Greg KH wrote:
> On Tue, Nov 24, 2009 at 10:33:18AM +1100, Stephen Rothwell wrote:
>> Hi Rusty,
>>
>> On Tue, 24 Nov 2009 09:24:54 +1030 Rusty Russell <rusty@rustcorp.com.au> wrote:
>>> And I guess linux-next doesn't build staging?
>> Correct - it breaks to much and too often :-)
>
> Yes, remember, it's crap, you don't want to build it :)
that's certainly one way to look at it, but I do spend time/effort
trying to get it to build, then send patches that either get dropped
or sit in a queue or ignored for a long time by their driver writer,
so you are just reinforcing the negativism associated with staging.
I don't think that's what you should be doing.
--
~Randy
next prev parent reply other threads:[~2009-11-23 23:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 7:52 linux-next: Tree for November 23 Stephen Rothwell
2009-11-23 13:04 ` Michal Simek
2009-11-23 13:19 ` Ralf Baechle
2009-11-23 13:43 ` Michal Simek
2009-11-23 19:15 ` Randy Dunlap
2009-11-23 22:54 ` Rusty Russell
2009-11-23 23:04 ` Randy Dunlap
2009-11-23 23:36 ` Stephen Rothwell
2009-11-23 23:37 ` Randy Dunlap
2009-11-23 23:43 ` Greg KH
2009-11-23 23:44 ` Randy Dunlap
2009-11-23 23:33 ` Stephen Rothwell
2009-11-23 23:34 ` Randy Dunlap
2009-11-23 23:39 ` Greg KH
2009-11-23 23:43 ` Randy Dunlap
2009-11-23 23:38 ` Greg KH
2009-11-23 23:42 ` Randy Dunlap [this message]
2009-11-24 2:34 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2010-11-23 3:06 Stephen Rothwell
2010-11-23 15:43 ` Zimny Lech
2010-11-23 17:15 ` Randy Dunlap
2010-11-23 19:03 ` Zimny Lech
2010-11-23 19:04 ` Zimny Lech
2010-11-23 15:45 ` Zimny Lech
2010-11-23 16:32 ` Anca Emanuel
2010-11-23 17:11 ` Anca Emanuel
2010-11-25 5:58 ` Stephen Rothwell
2010-11-24 9:24 ` Zimny Lech
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=4B0B1DD2.9000404@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.