From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>
Cc: akpm@linux-foundation.org, greg@kroah.com,
jbarnes@virtuousgeek.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: gregkh-02-pci tree is now gone
Date: Wed, 30 Apr 2008 16:22:39 +1000 [thread overview]
Message-ID: <20080430162239.c0af9846.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080429.223854.24800777.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
On Tue, 29 Apr 2008 22:38:54 -0700 (PDT) David Miller <davem@davemloft.net> wrote:
>
> From: Andrew Morton <akpm@linux-foundation.org>
> Date: Tue, 29 Apr 2008 22:34:12 -0700
>
> > What is gregkh-03-ldp?
>
> That's the special tree that breaks the linux-next build every day
> in order to make sure Stephen is paying attention :-)
Today, that failed in its plan :-)
Actually is it is a tree for the Linux Driver Project that Greg is
running - I am in two minds about whether I should carry it. Currently,
it is right at the end of the build and if something fails in there it
gets reverted - I make no attempt to diagnose problems. Greg wanted
"exposure".
I will write up a general mail about what I want in linux-next from now
on and I suspect that I will exclude most (if not all) of that tree.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-04-30 6:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 22:51 Greg KH
2008-04-24 23:19 ` Jesse Barnes
2008-04-25 7:53 ` Sebastian Siewior
2008-04-25 14:06 ` Jesse Barnes
2008-04-25 9:41 ` Stephen Rothwell
2008-04-30 5:34 ` Andrew Morton
2008-04-30 5:38 ` David Miller
2008-04-30 5:49 ` Andrew Morton
2008-04-30 6:18 ` Greg KH
2008-04-30 6:22 ` Stephen Rothwell [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=20080430162239.c0af9846.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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
all inboxes | Powered by JetHome®