From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: fix the comment explaining xfs_trans_dqlockedjoin
Date: Fri, 15 Nov 2013 09:34:15 -0800 [thread overview]
Message-ID: <20131115173415.GA19381@infradead.org> (raw)
In-Reply-To: <20131106114536.GA18548@infradead.org>
Not the most important patch ever, but I think it should still be picked
up :)
On Wed, Nov 06, 2013 at 03:45:36AM -0800, Christoph Hellwig wrote:
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> diff --git a/fs/xfs/xfs_trans_dquot.c b/fs/xfs/xfs_trans_dquot.c
> index cd2a10e..4117286 100644
> --- a/fs/xfs/xfs_trans_dquot.c
> +++ b/fs/xfs/xfs_trans_dquot.c
> @@ -295,8 +295,8 @@ xfs_trans_mod_dquot(
> /*
> * Given an array of dqtrx structures, lock all the dquots associated and join
> * them to the transaction, provided they have been modified. We know that the
> - * highest number of dquots of one type - usr, grp OR prj - involved in a
> - * transaction is 2 so we don't need to make this very generic.
> + * highest number of dquots of one type - usr, grp and prj - involved in a
> + * transaction is 3 so we don't need to make this very generic.
> */
> STATIC void
> xfs_trans_dqlockedjoin(
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
---end quoted text---
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-11-15 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 11:45 [PATCH] xfs: fix the comment explaining xfs_trans_dqlockedjoin Christoph Hellwig
2013-11-06 12:50 ` Carlos Maiolino
2013-11-15 17:34 ` Christoph Hellwig [this message]
2013-11-18 15:26 ` Ben Myers
2013-12-04 21:54 ` 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=20131115173415.GA19381@infradead.org \
--to=hch@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox