From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for June 11
Date: Wed, 11 Jun 2008 11:55:27 -0700 [thread overview]
Message-ID: <20080611185527.GB5516@kroah.com> (raw)
In-Reply-To: <20080611193840.08a35b14.sfr@canb.auug.org.au>
On Wed, Jun 11, 2008 at 07:38:40PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since next-20080610:
>
> Dropped trees (temporary): ldp (it is unfetchable - probably something to
> do with the new Staging tree), block (it just has too many conflicts and
> breaks the powerpc build).
Yes, I've dropped "ldp" from my 'gregkh' set of patches/trees, they
should be pulled in from the -staging tree, which would be great if you
could add to the end of the -next tree.
I've also removed some of the larger patches in the driver-core tree
that were causing you merge/build errors, they should be all resolved
now.
thanks,
greg k-h
next prev parent reply other threads:[~2008-06-11 18:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 9:38 linux-next: Tree for June 11 Stephen Rothwell
2008-06-11 14:32 ` [BUILD-FAILURE] linux-next: Tree for June 11 - on ia64 Kamalesh Babulal
2008-06-11 14:50 ` Sam Ravnborg
2008-06-11 16:46 ` Kamalesh Babulal
2008-06-11 23:10 ` Stephen Rothwell
2008-06-11 23:14 ` Stephen Rothwell
2008-06-11 18:55 ` Greg KH [this message]
2008-06-12 0:05 ` ldp/staging/driver-core (Was: Re: linux-next: Tree for June 11) Stephen Rothwell
2008-06-12 0:17 ` Greg KH
2008-06-12 0:17 ` linux-next: Tree for June 11 Kevin Winchester
-- strict thread matches above, loose matches on Subject: below --
2009-06-11 9:14 Stephen Rothwell
2010-06-11 4:17 Stephen Rothwell
2010-06-11 23:31 ` Andrew Morton
2010-06-15 9:26 ` Rusty Russell
2010-06-15 9:34 ` Andrew Morton
2010-06-23 22:53 ` Andrew Morton
2010-06-25 12:57 ` Rusty Russell
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=20080611185527.GB5516@kroah.com \
--to=greg@kroah.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;
as well as URLs for NNTP newsgroup(s).