From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Brian Foster <bfoster@redhat.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/3] xfs/122: embiggen struct xfs_agi size for inobtcount feature
Date: Thu, 25 Feb 2021 08:04:56 -0800 [thread overview]
Message-ID: <20210225160456.GJ7272@magnolia> (raw)
In-Reply-To: <20210225073848.GC2483198@infradead.org>
On Thu, Feb 25, 2021 at 07:38:48AM +0000, Christoph Hellwig wrote:
> On Fri, Feb 12, 2021 at 09:33:42PM -0800, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> >
> > Make the expected AGI size larger for the inobtcount feature.
>
> Is embiggen really a word? Otherwise looks good:
Yes.
Original source: https://youtu.be/FcxsgZxqnEg?t=65
Legitimate source: https://www.merriam-webster.com/dictionary/embiggen
:D
--D
> Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2021-02-25 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 5:33 [PATCHSET RFC 0/3] fstests: add inode btree blocks counters to the AGI header Darrick J. Wong
2021-02-13 5:33 ` [PATCH 1/3] xfs/{010,030}: update repair output to deal with inobtcount feature Darrick J. Wong
2021-02-25 7:38 ` Christoph Hellwig
2021-02-13 5:33 ` [PATCH 2/3] xfs/122: embiggen struct xfs_agi size for " Darrick J. Wong
2021-02-25 7:38 ` Christoph Hellwig
2021-02-25 16:04 ` Darrick J. Wong [this message]
2021-02-13 5:33 ` [PATCH 3/3] xfs: test inobtcount upgrade Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2021-03-23 4:20 [PATCHSET 0/3] fstests: add inode btree blocks counters to the AGI header Darrick J. Wong
2021-03-23 4:20 ` [PATCH 2/3] xfs/122: embiggen struct xfs_agi size for inobtcount feature 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=20210225160456.GJ7272@magnolia \
--to=djwong@kernel.org \
--cc=bfoster@redhat.com \
--cc=hch@infradead.org \
--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).