Thread (18 messages) 18 messages, 4 authors, 2021-09-20

Re: [PATCH v5 2/8] configfs: use BIT() for internal flags

From: Bartosz Golaszewski <hidden>
Date: 2021-09-20 15:01:44
Also in: linux-doc, lkml

On Mon, Sep 20, 2021 at 4:50 PM Geert Uytterhoeven [off-list ref] wrote:
Hi Bartosz,

On Mon, Sep 20, 2021 at 4:47 PM Bartosz Golaszewski [off-list ref] wrote:
quoted
On Mon, Sep 20, 2021 at 4:30 PM Christoph Hellwig [off-list ref] wrote:
quoted
On Mon, Sep 20, 2021 at 04:29:30PM +0200, Geert Uytterhoeven wrote:
quoted
On Mon, Sep 20, 2021 at 4:09 PM Christoph Hellwig [off-list ref] wrote:
quoted
On Mon, Sep 20, 2021 at 04:05:03PM +0200, Bartosz Golaszewski wrote:
quoted
For better readability and maintenance: use the BIT() macro for flag
definitions.
NAK.  BIT() is the stupidest macro in the kernel and shall not be used
ever.  And I'm pretty sure we had this discussion a few times.
Care to explain why it is a stupid macro?
Please look at the previous thread.  I'm tired of this discussion.
The only previous answer from Christoph is this:
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg2399968.html
Yep, found that one, too.

Now, as these definitions do not correspond to hardware register bits,
perhaps use an enum?
These are flags, we can set more than one to any given dirent.

Anyway, I'm more interested in Al's comments on the implementation of
committable items than bikeshedding about whether to use or not to use
BIT() so I'll wait for those before revisiting this patch.

Bart
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help