public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Liuwenyi <qingshenlwy@gmail.com>
To: jim owens <jowens@hp.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [RFC INFO PATCH 02/03] export use_mm and unuse_mm for filesystem modules.
Date: Wed, 20 Jan 2010 07:37:55 +0800	[thread overview]
Message-ID: <4B564253.20405@gmail.com> (raw)
In-Reply-To: <4B562B14.3050208@hp.com>

Maybe, you should send this patch to

Andrew Morton <akpm@linux-foundation.org>
Andrea Arcangeli <aarcange@redhat.com>
Michael S. Tsirkin <mst@redhat.com>
linux-kernel@vger.kernel.org
linux-mm@kvack.org


=E4=BA=8E 2010=E5=B9=B401=E6=9C=8820=E6=97=A5 05:58, jim owens =E5=86=99=
=E9=81=93:
> required for btrfs directio worker threads.
>
> Signed-off-by: jim owens<jowens@hp.com>
> ---
> mm/mmu_context.c |    3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/mm/mmu_context.c b/mm/mmu_context.c
> index ded9081..daabf4d 100644
> --- a/mm/mmu_context.c
> +++ b/mm/mmu_context.c
> @@ -3,6 +3,7 @@
>   * See ../COPYING for licensing terms.
>   */
>
> +#include<linux/module.h>
> #include<linux/mm.h>
> #include<linux/mmu_context.h>
> #include<linux/sched.h>
> @@ -37,6 +38,7 @@ void use_mm(struct mm_struct *mm)
>      if (active_mm !=3D mm)
>          mmdrop(active_mm);
> }
> +EXPORT_SYMBOL_GPL(use_mm);
>
> /*
>   * unuse_mm
> @@ -56,3 +58,4 @@ void unuse_mm(struct mm_struct *mm)
>      enter_lazy_tlb(mm, tsk);
>      task_unlock(tsk);
> }
> +EXPORT_SYMBOL_GPL(unuse_mm);
>   =20

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-01-19 23:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19 21:58 [RFC INFO PATCH 02/03] export use_mm and unuse_mm for filesystem modules jim owens
2010-01-19 23:37 ` Liuwenyi [this message]
2010-01-20 13:34   ` jim owens
2010-01-20 17:08     ` jim owens

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=4B564253.20405@gmail.com \
    --to=qingshenlwy@gmail.com \
    --cc=jowens@hp.com \
    --cc=linux-btrfs@vger.kernel.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