From: Stephen Rothwell <sfr@canb•auug.org.au>
To: NeilBrown <neilb@suse•de>
Cc: linux-next@vger•kernel.org, Johannes Weiner <jw@emlix•com>,
Dan Williams <dan.j.williams@intel•com>
Subject: Re: linux-next: manual merge of the md tree with the tree
Date: Tue, 10 Mar 2009 17:49:34 +1100 [thread overview]
Message-ID: <20090310174934.1dada698.sfr@canb.auug.org.au> (raw)
In-Reply-To: <ad338337833c61261ca27f348033e83d.squirrel@neil.brown.name>
[-- Attachment #1: Type: text/plain, Size: 301 bytes --]
Hi Neil,
On Tue, 10 Mar 2009 17:40:20 +1100 (EST) "NeilBrown" <neilb@suse•de> wrote:
>
> I've resolved this i my tree so you don't need to carry the fix any
> further.
Thanks again.
--
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-03-10 6:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 5:33 linux-next: manual merge of the md tree with the tree Stephen Rothwell
2009-03-10 6:40 ` NeilBrown
2009-03-10 6:49 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-10 4:38 Stephen Rothwell
2012-09-21 2:49 Stephen Rothwell
2014-01-15 4:02 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=20090310174934.1dada698.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dan.j.williams@intel$(echo .)com \
--cc=jw@emlix$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=neilb@suse$(echo .)de \
/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