From: Al Viro <viro@ZenIV.linux.org.uk>
To: jim owens <jowens@hp.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
mst@redhat.com, linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] export use_mm and unuse_mm for filesystem modules.
Date: Wed, 9 Dec 2009 22:45:36 +0000 [thread overview]
Message-ID: <20091209224536.GT14381@ZenIV.linux.org.uk> (raw)
In-Reply-To: <4B20277B.1030903@hp.com>
On Wed, Dec 09, 2009 at 05:40:59PM -0500, jim owens wrote:
>
> required for btrfs directio worker threads.
Careful. It's very easy to fsck up on biarch architectures with
that stuff.
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ZenIV.linux.org.uk>
To: jim owens <jowens@hp.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
mst@redhat.com, linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] export use_mm and unuse_mm for filesystem modules.
Date: Wed, 9 Dec 2009 22:45:36 +0000 [thread overview]
Message-ID: <20091209224536.GT14381@ZenIV.linux.org.uk> (raw)
In-Reply-To: <4B20277B.1030903@hp.com>
On Wed, Dec 09, 2009 at 05:40:59PM -0500, jim owens wrote:
>
> required for btrfs directio worker threads.
Careful. It's very easy to fsck up on biarch architectures with
that stuff.
--
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>
next prev parent reply other threads:[~2009-12-09 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 22:40 [PATCH] export use_mm and unuse_mm for filesystem modules jim owens
2009-12-09 22:40 ` jim owens
2009-12-09 22:45 ` Al Viro [this message]
2009-12-09 22:45 ` Al Viro
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=20091209224536.GT14381@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=jowens@hp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mst@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.