From: Jens Axboe <jens.axboe@oracle.com>
To: Medve Emilian-EMMEDVE1 <Emilian.Medve@freescale.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH v2] Fix a build error when BLOCK=n
Date: Tue, 23 Oct 2007 22:21:17 +0200 [thread overview]
Message-ID: <20071023202117.GJ14671@kernel.dk> (raw)
In-Reply-To: <598D5675D34BE349929AF5EDE9B03E27016E5644@az33exm24.fsl.freescale.net>
On Tue, Oct 23 2007, Medve Emilian-EMMEDVE1 wrote:
> Hello Jens,
>
>
> In who's tree would this go?
I'll add it to the block tree.
--
Jens Axboe
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2007-10-23 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 14:55 [PATCH v2] Fix a build error when BLOCK=n Emil Medve
2007-10-18 15:26 ` Jens Axboe
2007-10-23 19:27 ` Medve Emilian-EMMEDVE1
2007-10-23 20:21 ` Jens Axboe [this message]
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=20071023202117.GJ14671@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=Emilian.Medve@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
/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).