From: Greg KH <greg@kroah.com>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
wangchen@cn.fujitsu.com
Subject: Re: linux-next: manual merge of the staging tree
Date: Tue, 9 Dec 2008 07:40:53 -0800 [thread overview]
Message-ID: <20081209154053.GA25934@kroah.com> (raw)
In-Reply-To: <20081208.235914.264894795.davem@davemloft.net>
On Mon, Dec 08, 2008 at 11:59:14PM -0800, David Miller wrote:
> From: Greg KH <greg@kroah.com>
> Date: Mon, 8 Dec 2008 19:53:18 -0800
>
> > On Mon, Dec 08, 2008 at 12:35:57PM -0800, David Miller wrote:
> > > Because I have to do allmodconfig test builds _too_, and the build
> > > will fail for me if I do these reverts which really would suck.
> >
> > Ok, that's fine, as long as stephen can keep this patch in his tree,
> > I'll apply it to mine when you merge with Linus, as the staging tree
> > will probably be one of the last things before the next -rc1 window
> > closes.
>
> BTW, there is something else we can do.
>
> I can pull staging net driver changes into net-next-2.6
>
> We can either do it as a one-time thing to alleviate this
> merge hassle, or we can try and make it a more ongoing
> merge mechanism.
I doubt you really want to do this, as there are some pretty big
wireless driver additions in the staging tree right now, some under very
heavy development.
I have no problem with this kind of merge issues, I'll fix it up on my
end, don't worry about it.
thanks,
greg k-h
next prev parent reply other threads:[~2008-12-09 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 9:34 linux-next: manual merge of the staging tree Stephen Rothwell
2008-12-08 15:17 ` Greg KH
2008-12-08 20:35 ` David Miller
2008-12-09 3:53 ` Greg KH
2008-12-09 7:59 ` David Miller
2008-12-09 15:40 ` Greg KH [this message]
2008-12-09 21:42 ` David Miller
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=20081209154053.GA25934@kroah.com \
--to=greg@kroah.com \
--cc=davem@davemloft.net \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=wangchen@cn.fujitsu.com \
/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.