From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for March 27
Date: Fri, 28 Mar 2008 15:53:16 +1100 [thread overview]
Message-ID: <20080328155316.a44e368d.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080327144505.GB18810@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
Hi Greg,
On Thu, 27 Mar 2008 07:45:05 -0700 Greg KH <greg@kroah.com> wrote:
>
> Can you add my "linux drivers" tree at:
> http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-04-ldp/
> to the mix as well? It should come after my 3 other trees. It contains
> new drivers that are being worked on by the linux driver project group.
Are these drivers targetted at 2.6.26? If so, I will add this at the end
(and drop it temporarily when it breaks). If not, then it should wait
until after 2.6.25 is out.
> The code there isn't the best, but it is actively being worked on to
> clean up and get ready for merging, and should always build properly.
> If not, I'd like to know about it, as it passes my build tests on i386
> and x86-64.
That is promising.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-03-28 4:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 7:33 Stephen Rothwell
2008-03-27 8:49 ` [BUILD_FAILURE] " Kamalesh Babulal
2008-03-27 9:42 ` Haavard Skinnemoen
2008-03-27 10:47 ` Adrian Bunk
2008-03-27 11:32 ` Haavard Skinnemoen
2008-03-27 11:54 ` Adrian Bunk
2008-03-27 12:11 ` Haavard Skinnemoen
2008-03-27 12:54 ` Jan Dittmer
2008-03-27 13:22 ` Adrian Bunk
2008-03-27 13:31 ` Haavard Skinnemoen
2008-03-27 22:29 ` Stephen Rothwell
2008-03-27 14:45 ` Greg KH
2008-03-28 4:53 ` Stephen Rothwell [this message]
2008-03-28 20:27 ` Greg KH
2008-03-29 3:56 ` Stephen Rothwell
2009-03-27 12:19 Stephen Rothwell
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=20080328155316.a44e368d.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=greg@kroah.com \
--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®