From: Stephen Rothwell <sfr@canb.auug.org.au>
To: James Morris <jmorris@namei.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: linux-next: security-testing tree build failure
Date: Tue, 8 Sep 2009 13:22:44 +1000 [thread overview]
Message-ID: <20090908132244.3785a8a8.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090908104012.ff4bd25f.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 307 bytes --]
Hi James, David,
On Tue, 8 Sep 2009 10:40:12 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> This also broke the alpha and mips builds. I am going to use the version
And cris :-(
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-09-08 3:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 13:40 linux-next: security-testing tree build failure Stephen Rothwell
2009-09-07 13:43 ` Stephen Rothwell
2009-09-08 0:40 ` Stephen Rothwell
2009-09-08 3:22 ` Stephen Rothwell [this message]
2009-09-09 7:30 ` [PATCH] KEYS: Add missing linux/tracehook.h #inclusions David Howells
2009-09-09 8:38 ` James Morris
2009-09-09 8:48 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-09-07 10:38 linux-next: security-testing tree build failure Stephen Rothwell
2009-09-03 5:51 Stephen Rothwell
2009-08-07 4:59 Stephen Rothwell
2009-08-10 14:07 ` Eric Paris
2009-08-10 23:58 ` Stephen Rothwell
2009-02-06 7:28 Stephen Rothwell
2009-02-06 8:14 ` James Morris
2008-11-13 7:46 Stephen Rothwell
2008-11-14 7:43 ` Stephen Rothwell
2008-11-14 22:42 ` Eric Paris
2008-11-15 1:56 ` Stephen Rothwell
2008-11-12 5:05 Stephen Rothwell
2008-11-12 10:56 ` James Morris
2008-11-12 14:05 ` Eric Paris
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=20090908132244.3785a8a8.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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