From: Ben Myers <bpm@sgi.com>
To: Chen Baozi <baozich@gmail.com>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [RESEND PATCH] xfs: fix typo in comment of xfs_dinode_t.
Date: Fri, 25 May 2012 14:24:46 -0500 [thread overview]
Message-ID: <20120525192445.GW16099@sgi.com> (raw)
In-Reply-To: <D347A332-0256-43E4-8FCE-BCFC1DD478C8@gmail.com>
On Sat, May 26, 2012 at 12:48:47AM +0800, Chen Baozi wrote:
> There should be "XFS_DFORK_DPTR, XFS_DFORK_APTR, and XFS_DFORK_PTR" instead
> of "XFS_DFORK_PTR, XFS_DFORK_DPTR, and XFS_DFORK_PTR".
>
> Signed-off-by: Chen Baozi <baozich@gmail.com>
> Reviewed-by: Mark Tinguely <tinguely@sgi.com>
Committed. Thanks for the patch Chen!
Signed-off-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: Chen Baozi <baozich@gmail.com>
Cc: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] xfs: fix typo in comment of xfs_dinode_t.
Date: Fri, 25 May 2012 14:24:46 -0500 [thread overview]
Message-ID: <20120525192445.GW16099@sgi.com> (raw)
In-Reply-To: <D347A332-0256-43E4-8FCE-BCFC1DD478C8@gmail.com>
On Sat, May 26, 2012 at 12:48:47AM +0800, Chen Baozi wrote:
> There should be "XFS_DFORK_DPTR, XFS_DFORK_APTR, and XFS_DFORK_PTR" instead
> of "XFS_DFORK_PTR, XFS_DFORK_DPTR, and XFS_DFORK_PTR".
>
> Signed-off-by: Chen Baozi <baozich@gmail.com>
> Reviewed-by: Mark Tinguely <tinguely@sgi.com>
Committed. Thanks for the patch Chen!
Signed-off-by: Ben Myers <bpm@sgi.com>
next prev parent reply other threads:[~2012-05-25 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 16:48 [RESEND PATCH] xfs: fix typo in comment of xfs_dinode_t Chen Baozi
2012-05-25 16:48 ` Chen Baozi
2012-05-25 19:24 ` Ben Myers [this message]
2012-05-25 19:24 ` 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=20120525192445.GW16099@sgi.com \
--to=bpm@sgi.com \
--cc=baozich@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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.