From: Gregory Haskins <gregory.haskins@gmail.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 November 24
Date: Tue, 24 Nov 2009 09:09:36 -0500 [thread overview]
Message-ID: <4B0BE920.40106@gmail.com> (raw)
In-Reply-To: <20091124212255.87e083ce.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 223 bytes --]
Stephen Rothwell wrote:
[...]
>
> The alacrity tree gained a build failure so I used the version from
> next-20091123.
>
Should be fixed in tomorrows tree. Sorry for the trouble!
Kind Regards,
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 267 bytes --]
next prev parent reply other threads:[~2009-11-24 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 10:22 linux-next: Tree for November 24 Stephen Rothwell
2009-11-24 10:54 ` Michal Simek
2009-11-24 14:09 ` Gregory Haskins [this message]
2009-11-24 20:13 ` [PATCH -next] staging/rtl8192x: fix printk formats Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2010-11-24 2:10 linux-next: Tree for November 24 Stephen Rothwell
2008-11-24 7:05 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=4B0BE920.40106@gmail.com \
--to=gregory.haskins@gmail.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).