From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 4/7] xfs: rename btree cursur private btree member flags
Date: Thu, 5 Mar 2020 13:29:05 +1100 [thread overview]
Message-ID: <20200305022905.GG10776@dread.disaster.area> (raw)
In-Reply-To: <20200305020804.GO8045@magnolia>
On Wed, Mar 04, 2020 at 06:08:04PM -0800, Darrick J. Wong wrote:
> On Thu, Mar 05, 2020 at 12:45:34PM +1100, Dave Chinner wrote:
> > From: Dave Chinner <dchinner@redhat.com>
> >
> > BPRV is not longer appropriate because bc_private is going away.
> > Script:
> >
> > $ sed -i 's/BTCUR_BPRV/BC_BT/g' fs/xfs/*[ch] fs/xfs/*/*[ch]
>
> I kinda hate the name though... BTCUR_BMBT?
Sure, that's simple enough to change. It's just a
s/BC_BT/BTCUR_BMBT/g
on the patch before I pop/push all the patches for a repost.
> (Also 'cursor' is misspelled in the subject line)
Fixed.
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2020-03-05 2:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 1:45 [PATCH 0/7] xfs: make btree cursor private unions anonymous Dave Chinner
2020-03-05 1:45 ` [PATCH 1/7] xfs: introduce new private btree cursor names Dave Chinner
2020-03-05 2:29 ` Darrick J. Wong
2020-03-05 2:47 ` Dave Chinner
2020-03-05 1:45 ` [PATCH 2/7] xfs: convert btree cursor ag private member name Dave Chinner
2020-03-05 2:31 ` Darrick J. Wong
2020-03-05 2:43 ` Dave Chinner
2020-03-05 1:45 ` [PATCH 3/7] xfs: convert btree cursor btree " Dave Chinner
2020-03-05 1:45 ` [PATCH 4/7] xfs: rename btree cursur private btree member flags Dave Chinner
2020-03-05 2:08 ` Darrick J. Wong
2020-03-05 2:29 ` Dave Chinner [this message]
2020-03-05 1:45 ` [PATCH 5/7] xfs: make btree cursor private union anonymous Dave Chinner
2020-03-05 1:45 ` [PATCH 6/7] xfs: make the btree cursor union members named structure Dave Chinner
2020-03-05 1:45 ` [PATCH 7/7] xfs: make the btree ag cursor private union anonymous Dave Chinner
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=20200305022905.GG10776@dread.disaster.area \
--to=david@fromorbit.com \
--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).