linux-kernel - RE: [PATCH 01/11] mmc: core: Use BIT() macro

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <da39a415784e4bbabfa99596ffd5b565@hyperstone.com>
Date:   Wed, 21 Jun 2023 11:23:54 +0000
From:   Christian Loehle <CLoehle@...erstone.com>
To:     Ulf Hansson <ulf.hansson@...aro.org>,
        "linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
        Marek Vasut <marex@...x.de>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 01/11] mmc: core: Use BIT() macro



> -----Original Message-----
> From: Ulf Hansson <ulf.hansson@...aro.org>
> Sent: Mittwoch, 21. Juni 2023 11:19
> To: Marek Vasut <marex@...x.de>
> Cc: linux-mmc@...r.kernel.org; Adrian Hunter <adrian.hunter@...el.com>;
> Avri Altman <avri.altman@....com>; Bo Liu <liubo03@...pur.com>; Deren
> Wu <deren.wu@...iatek.com>; Philipp Zabel <p.zabel@...gutronix.de>;
> Pierre Ossman <pierre@...man.eu>; Russell King <linux@...linux.org.uk>;
> Yang Yingliang <yangyingliang@...wei.com>
> Subject: Re: [PATCH 01/11] mmc: core: Use BIT() macro
> 
> CAUTION: this mail comes from external!/ACHTUNG: Diese Mail kommt von
> extern!
> 
> On Wed, 21 Jun 2023 at 04:36, Marek Vasut <marex@...x.de> wrote:
> >
> > On 6/20/23 13:15, Ulf Hansson wrote:
> > > On Tue, 20 Jun 2023 at 12:47, Marek Vasut <marex@...x.de> wrote:
> > >>
> > >> Use the BIT(n) macro instead of (1<<n), no functional change.
> > >> Regex 's@(1 \?<< \?\([0-9A-Z_]\+\))@BIT(\1)' .
> > >>
> > >> Signed-off-by: Marek Vasut <marex@...x.de>
> > >
> > > I don't think the benefit of this change is worth it. For example,
> > > it's quite useful to run a git blame to see the history of what has
> > > happened.
> >
> > Understood.
> >
> > git blame does allow you to specify either --since or revision range though.
> 
> Yes, but I think you get my point.
> 
> >
> > > So, sorry, but I am not going to pick this up - or any other similar
> > > changes, at least for the core layer.
> >
> > Is this a policy of the mmc subsystem to reject all code clean ups then ?
> 
> Of course it isn't, I regularly pick up clean ups.
> 
> My point here is that the clean-up should make the code better, in some
> way. I don't think converting to the BIT macro helps in this regard. It may be
> preferred to use the BIT macro by some and by others not.

FWIW I agree with Uffe here.
For host/ files, which are mostly written by a handful each, it's still a nuisance. (One could argue that they are often git blamed by people not familiar with mmc subsystem, thus giving off the wrong picture).
For much of the core code you already have to go many revisions back, I'm grateful for each I don't have to.
Something like the mq rework would have been a good moment to do these minor nitpicks, if something like that ever happens again, but even then I  would prefer just one commit including everything.


Regards,
Christian

Download attachment "smime.p7s" of type "application/pkcs7-signature" (10302 bytes)