From: Greg KH <greg@kroah.com>
To: "J.R. Mauro" <jrm8005@gmail.com>
Cc: 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: Thu, 13 Nov 2008 16:22:03 -0800 [thread overview]
Message-ID: <20081114002203.GA20272@kroah.com> (raw)
In-Reply-To: <3aaafc130811131613j1f4425deodcb3b3f9fd330653@mail.gmail.com>
On Thu, Nov 13, 2008 at 07:13:40PM -0500, J.R. Mauro wrote:
> On Thu, Nov 13, 2008 at 7:01 PM, Greg KH <greg@kroah.com> wrote:
> > On Fri, Nov 14, 2008 at 10:44:21AM +1100, Stephen Rothwell wrote:
> >> Hi Greg,
> >>
> >> On Wed, 12 Nov 2008 15:56:00 -0800 Greg KH <greg@kroah.com> wrote:
> >> >
> >> > I'm starting to get people sending me patches against -next for the
> >> > drivers/staging/ tree that don't apply as -next does not include my
> >> > quilt tree of staging patches.
> >> >
> >> > Can you please pick it up? You can put it at the end of your series,
> >> > and the 'make allmodconfig' option disables building anything in the
> >> > drivers/staging/ subdirectory, so it should not have any build or merge
> >> > conflicts with anything.
> >> >
> >> > It can be found at:
> >> > http://kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-05-staging/
> >> > and is a quilt tree.
> >> >
> >> > It will follow all the same rules as other trees, with patches only for
> >> > the next merge window (2.6.29 right now) in it.
> >>
> >> OK, I have added it starting today.
> >
> > Thank you very much, I appreciate it.
>
> Greg, will this suffice for having a git repo for staging, or are you
> still planning on a discrete staging repo?
For now, this is probably going to be sufficient for me, how about you?
thanks,
greg k-h
next prev parent reply other threads:[~2008-11-14 0:22 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 [this message]
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
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=20081114002203.GA20272@kroah.com \
--to=greg@kroah.com \
--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 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.