All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Cc: xfs ML <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfs: Remove the description about nodelaylog mount option from, the xfs document.
Date: Mon, 26 Nov 2012 09:55:11 -0600	[thread overview]
Message-ID: <20121126155511.GF27055@sgi.com> (raw)
In-Reply-To: <50B30B41.8040400@jp.fujitsu.com>

On Mon, Nov 26, 2012 at 03:25:05PM +0900, Satoru Takeuchi wrote:
> From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
> 
> nodelaylog mount option is removed by commit 93b8a585. But there still be
> the description about it in the xfs document. This patch removes it.
> 
> Signed-off-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
> ---
>  Documentation/filesystems/xfs.txt |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/Documentation/filesystems/xfs.txt b/Documentation/filesystems/xfs.txt
> index 3fc0c31..860b845 100644
> --- a/Documentation/filesystems/xfs.txt
> +++ b/Documentation/filesystems/xfs.txt
> @@ -43,7 +43,7 @@ When mounting an XFS filesystem, the following options are accepted.
>         Issue command to let the block device reclaim space freed by the
>         filesystem.  This is useful for SSD devices, thinly provisioned
>         LUNs and virtual machine images, but may have a performance
> -       impact.  This option is incompatible with the nodelaylog option.
> +       impact.

Looks good.

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

Thanks Satoru!

-Ben

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

  reply	other threads:[~2012-11-26 15:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26  6:25 [PATCH] xfs: Remove the description about nodelaylog mount option from, the xfs document Satoru Takeuchi
2012-11-26 15:55 ` Ben Myers [this message]
2012-11-26 22:07   ` Ben Myers
2012-11-27  7:33     ` Satoru Takeuchi

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=20121126155511.GF27055@sgi.com \
    --to=bpm@sgi.com \
    --cc=takeuchi_satoru@jp.fujitsu.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.