public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: Wang Sheng-Hui <shhuiw@gmail.com>
Cc: chris.mason@fusionio.com, linux-btrfs@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Btrfs: small fix the commment for the action flags in delayed-ref.h
Date: Thu, 20 Sep 2012 23:12:29 +0800	[thread overview]
Message-ID: <505B325D.4020802@oracle.com> (raw)
In-Reply-To: <505B3117.9040603@gmail.com>

On 09/20/2012 11:07 PM, Wang Sheng-Hui wrote:
> The action has been merged into struct btrfs_delayed_ref_node,
> and no struct btrfs_delayed_ref is available now.
> 

You can consider sending this kind of typo fix patch to trivial list instead.

thanks,
liubo

> Signed-off-by: Wang Sheng-Hui <shhuiw@gmail.com>
> ---
>  fs/btrfs/delayed-ref.h |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/btrfs/delayed-ref.h b/fs/btrfs/delayed-ref.h
> index ab53005..c9d7036 100644
> --- a/fs/btrfs/delayed-ref.h
> +++ b/fs/btrfs/delayed-ref.h
> @@ -18,7 +18,7 @@
>  #ifndef __DELAYED_REF__
>  #define __DELAYED_REF__
>  
> -/* these are the possible values of struct btrfs_delayed_ref->action */
> +/* these are the possible values of struct btrfs_delayed_ref_node->action */
>  #define BTRFS_ADD_DELAYED_REF    1 /* add one backref to the tree */
>  #define BTRFS_DROP_DELAYED_REF   2 /* delete one backref from the tree */
>  #define BTRFS_ADD_DELAYED_EXTENT 3 /* record a full extent allocation */
> 


      reply	other threads:[~2012-09-20 15:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 15:07 [PATCH] Btrfs: small fix the commment for the action flags in delayed-ref.h Wang Sheng-Hui
2012-09-20 15:12 ` Liu Bo [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=505B325D.4020802@oracle.com \
    --to=bo.li.liu@oracle.com \
    --cc=chris.mason@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shhuiw@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox