All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Gerard Snitselaar <dev@snitselaar.org>
Cc: xfs@oss.sgi.com, elder@kernel.org, linux-kernel@vger.kernel.org,
	xfs-master@oss.sgi.com
Subject: Re: [PATCH] fs: xfs: fix section mismatch in linux-next
Date: Thu, 22 Mar 2012 13:33:34 -0500	[thread overview]
Message-ID: <20120322183334.GN8451@sgi.com> (raw)
In-Reply-To: <1331922978-28572-1-git-send-email-dev@snitselaar.org>

On Fri, Mar 16, 2012 at 11:36:18AM -0700, Gerard Snitselaar wrote:
> xfs_qm_exit() is called in init_xfs_fs().
> 
> Signed-off-by: Gerard Snitselaar <dev@snitselaar.org>

Thanks Gerard.
Reviewed-by: Ben Myers <bpm@sgi.com>

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Ben Myers <bpm@sgi.com>
To: Gerard Snitselaar <dev@snitselaar.org>
Cc: elder@kernel.org, xfs-master@oss.sgi.com, xfs@oss.sgi.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: xfs: fix section mismatch in linux-next
Date: Thu, 22 Mar 2012 13:33:34 -0500	[thread overview]
Message-ID: <20120322183334.GN8451@sgi.com> (raw)
In-Reply-To: <1331922978-28572-1-git-send-email-dev@snitselaar.org>

On Fri, Mar 16, 2012 at 11:36:18AM -0700, Gerard Snitselaar wrote:
> xfs_qm_exit() is called in init_xfs_fs().
> 
> Signed-off-by: Gerard Snitselaar <dev@snitselaar.org>

Thanks Gerard.
Reviewed-by: Ben Myers <bpm@sgi.com>


  parent reply	other threads:[~2012-03-22 18:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 18:36 [PATCH] fs: xfs: fix section mismatch in linux-next Gerard Snitselaar
2012-03-16 18:36 ` Gerard Snitselaar
2012-03-17 11:50 ` Christoph Hellwig
2012-03-17 11:50   ` Christoph Hellwig
2012-03-22 18:33 ` Ben Myers [this message]
2012-03-22 18:33   ` Ben Myers

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=20120322183334.GN8451@sgi.com \
    --to=bpm@sgi.com \
    --cc=dev@snitselaar.org \
    --cc=elder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xfs-master@oss.sgi.com \
    --cc=xfs@oss.sgi.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.