From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Dan Williams <dan.j.williams@intel•com>
Cc: "linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: async_tx tree build failure
Date: Thu, 23 Jul 2009 15:17:48 +1000 [thread overview]
Message-ID: <20090723151748.4a7d7281.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1248323620.24951.2.camel@dwillia2-linux.ch.intel.com>
[-- Attachment #1: Type: text/plain, Size: 320 bytes --]
Hi Dan,
On Wed, 22 Jul 2009 21:33:40 -0700 Dan Williams <dan.j.williams@intel•com> wrote:
>
> Gah, yes that commit was half baked. I have pushed out an updated tree
> with the following fix:
Thanks.
--
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-07-23 5:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 2:00 linux-next: async_tx tree build failure Stephen Rothwell
2009-07-23 4:33 ` Dan Williams
2009-07-23 5:17 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-07 3:08 Stephen Rothwell
2009-09-09 1:35 ` Dan Williams
2009-09-09 1:41 ` 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=20090723151748.4a7d7281.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dan.j.williams@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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