From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>
Subject: Re: linux-next: Tree for January 2
Date: Fri, 2 Jan 2009 15:08:34 +0100 [thread overview]
Message-ID: <200901021508.34847.rjw@sisk.pl> (raw)
In-Reply-To: <20090102203303.f314a99a.sfr@canb.auug.org.au>
On Friday 02 January 2009, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20081231:
>
> Removed tree:
> boot-params (became 2.6.30 material)
>
> Dropped trees (temporarily):
> driver-core (build problem)
Can you please tell me what exactly the build problem with the driver-core tree
is? Maybe I can fix it.
Thanks,
Rafael
next prev parent reply other threads:[~2009-01-02 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 9:33 linux-next: Tree for January 2 Stephen Rothwell
2009-01-02 14:08 ` Rafael J. Wysocki [this message]
2009-01-02 17:52 ` Greg KH
2009-01-02 18:18 ` [PATCH -next] sunrpc: fix RDMA dependency Randy Dunlap
2009-01-02 18:18 ` [PATCH -next] 9p: " Randy Dunlap
2009-01-02 19:59 ` Roland Dreier
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=200901021508.34847.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=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).