From: Eric Sandeen <sandeen@sandeen.net>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/4] xfs_io: add a bulkstat command
Date: Thu, 26 Sep 2019 17:46:23 -0500 [thread overview]
Message-ID: <bd0e2c1c-9014-3ce6-3bfa-6b7b0e57c48c@sandeen.net> (raw)
In-Reply-To: <fd86aa65-2473-d316-80d9-944100519f77@sandeen.net>
On 9/26/19 5:40 PM, Eric Sandeen wrote:
>> +static bool debug;
> since I'm old and my brain is weakening... do you need to turn this global
> debug back off in each foo_f function unless the -d debug option was specified?
>
Actually it doesn't seem to be used in any sub-functions so it should
probably be local to each foo_f()
-Eric
next prev parent reply other threads:[~2019-09-26 22:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 21:32 [PATCH 0/4] xfsprogs: bulkstat v5 Darrick J. Wong
2019-09-25 21:33 ` [PATCH 1/4] xfs_io: add a bulkstat command Darrick J. Wong
2019-09-26 22:40 ` Eric Sandeen
2019-09-26 22:46 ` Eric Sandeen [this message]
2019-09-27 4:18 ` Darrick J. Wong
2019-09-30 20:02 ` Eric Sandeen
2019-09-30 20:15 ` Darrick J. Wong
2019-10-07 19:13 ` Eric Sandeen
2019-09-27 20:15 ` [PATCH v2 " Darrick J. Wong
2019-09-30 20:15 ` Eric Sandeen
2019-09-25 21:33 ` [PATCH 2/4] xfs_spaceman: remove open-coded per-ag bulkstat Darrick J. Wong
2019-09-25 21:33 ` [PATCH 3/4] xfs_scrub: convert to per-ag inode bulkstat operations Darrick J. Wong
2019-09-25 21:33 ` [PATCH 4/4] xfs_scrub: batch inumbers calls during fscounters calculation Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2019-09-06 3:35 [PATCH 0/4] xfsprogs: bulkstat v5 Darrick J. Wong
2019-09-06 3:35 ` [PATCH 1/4] xfs_io: add a bulkstat command Darrick J. Wong
2019-09-12 23:51 ` Dave Chinner
2019-08-26 21:27 [PATCH 0/4] xfsprogs: bulkstat v5 Darrick J. Wong
2019-08-26 21:27 ` [PATCH 1/4] xfs_io: add a bulkstat command Darrick J. Wong
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=bd0e2c1c-9014-3ce6-3bfa-6b7b0e57c48c@sandeen.net \
--to=sandeen@sandeen.net \
--cc=darrick.wong@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;
as well as URLs for NNTP newsgroup(s).