Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] fs: define inode flags using bit numbers
Date: Mon, 13 Jul 2020 12:59:47 +0100 [thread overview]
Message-ID: <20200713115947.GX12769@casper.infradead.org> (raw)
In-Reply-To: <20200713030952.192348-1-ebiggers@kernel.org>
On Sun, Jul 12, 2020 at 08:09:52PM -0700, Eric Biggers wrote:
> Define the VFS inode flags using bit numbers instead of hardcoding
> powers of 2, which has become unwieldy now that we're up to 65536.
If you're going to change these, why not use the BIT() macro?
next prev parent reply other threads:[~2020-07-13 11:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 3:09 Eric Biggers
2020-07-13 11:59 ` Matthew Wilcox [this message]
2020-07-13 16:02 ` Eric Biggers
2020-07-14 1:18 ` Dave Chinner
2020-07-27 16:48 ` Eric Biggers
2020-07-27 18:38 ` Al Viro
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=20200713115947.GX12769@casper.infradead.org \
--to=willy@infradead.org \
--cc=ebiggers@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--subject='Re: [PATCH] fs: define inode flags using bit numbers' \
/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
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).