From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: John Garry <john.g.garry@oracle.com>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
"chandan.babu@oracle.com" <chandan.babu@oracle.com>,
"djwong@kernel.org" <djwong@kernel.org>
Subject: Re: [PATCH] xfs: Use xfs set and clear mp state helpers
Date: Fri, 12 Jul 2024 17:39:12 +0000 [thread overview]
Message-ID: <d3362032-e334-4e75-baf0-90e992c7314f@nvidia.com> (raw)
In-Reply-To: <20240710103119.854653-1-john.g.garry@oracle.com>
On 7/10/2024 3:31 AM, John Garry wrote:
> Use the set and clear mp state helpers instead of open-coding.
>
> It is noted that in some instances calls to atomic operation set_bit() and
> clear_bit() are being replaced with test_and_set_bit() and
> test_and_clear_bit(), respectively, as there is no specific helpers for
> set_bit() and clear_bit() only. However should be ok, as we are just
> ignoring the returned value from those "test" variants.
>
> Signed-off-by: John Garry<john.g.garry@oracle.com>
This patch looks good to me, however formatting of the patch seems
little odd to me, what I meant is section describing the number of flies
changes and lines per file seems to be missing, e.g. (from different
patch) :-
"
---
fs/xfs/scrub/trace.h | 10 ++++------
fs/xfs/xfs_trace.h | 10 ++++------
2 files changed, 8 insertions(+), 12 deletions(-)
"
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2024-07-12 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 10:31 [PATCH] xfs: Use xfs set and clear mp state helpers John Garry
2024-07-11 2:53 ` Darrick J. Wong
2024-07-11 22:44 ` Dave Chinner
2024-07-12 17:39 ` Chaitanya Kulkarni [this message]
2024-07-15 6:56 ` John Garry
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=d3362032-e334-4e75-baf0-90e992c7314f@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=john.g.garry@oracle.com \
--cc=linux-xfs@vger.kernel.org \
/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