From: Greg KH <greg@kroah.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Philipp Zabel <philipp.zabel@gmail.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: Linus' tree build breakage
Date: Tue, 22 Apr 2008 15:30:16 -0700 [thread overview]
Message-ID: <20080422223016.GD7792@kroah.com> (raw)
In-Reply-To: <20080422073622.GB22955@flint.arm.linux.org.uk>
On Tue, Apr 22, 2008 at 08:36:22AM +0100, Russell King wrote:
> On Tue, Apr 22, 2008 at 10:31:11AM +1000, Stephen Rothwell wrote:
> > Russell, this is why I would have liked you to participate in the
> > linux-next tree ...
>
> linux-next will not give me anything which -mm isn't giving me. As I
> said in the discussion, linux-next value is _very_ small for me.
But it would help all of the rest of us out immensely. From what I can
tell (please correct me if I'm wrong), the linux-arm tree isn't
publicly seen by anyone else so they know exactly what they need to
rebase off of to submit patches for to you. Getting your stuff into
linux-next would provide a public place for others to base off of,
making it easier for them to send patches to you ensuring that they
apply properly.
Which in the end, will help others be able to contribute easier, and
help you by getting patches you do not need to rebase yourself.
thanks,
greg k-h
prev parent reply other threads:[~2008-04-22 22:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 0:31 linux-next: Linus' tree build breakage Stephen Rothwell
2008-04-22 7:36 ` Russell King
2008-04-22 7:43 ` David Miller
2008-04-22 13:58 ` Andrew Morton
2008-04-22 15:04 ` Stephen Rothwell
2008-04-22 22:30 ` Greg KH [this message]
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=20080422223016.GD7792@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=philipp.zabel@gmail.com \
--cc=rmk+lkml@arm.linux.org.uk \
--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