On Tue, Jan 18, 2022 at 08:36:56AM -0800, Lucas De Marchi wrote:
> I had the impression the subject/title should be imperative, with it
> more relaxed in the body. It seems we have one more difference among
> subsystems and I will adapt on next submissions to x86.
We have written it down properly, in case it explains it better:
"The tip tree maintainers set value on following these rules, especially
on the request to write changelogs in imperative mood and not
impersonating code or the execution of it. This is not just a whim of
the maintainers. Changelogs written in abstract words are more precise
and tend to be less confusing than those written in the form of novels."
from Documentation/process/maintainer-tip.rst
> > So I wonder: why can't you simply pass in a static struct chipset *
> > pointer into the early_qrk[i].f function and in there you can set
> > QFLAG_APPLIED or so, so that you can mark that the quirk is applied by
> > using the nice, per-quirk flags someone has already added instead of
> > this ugly static variable?
>
> It seems you prefer v1. See 20211218061313.100571-1-lucas.demarchi@xxxxxxxxx
I do?
I don't see there:
early_qrk[i].f(&early_qrk[i], num, slot, func)
so that the ->f callback can set the flags. Or at least the flags passed
in.
If it is not clear what I mean, pls say so and I'll try to produce an
example diff ontop.
> Although in the review Bjorn suggested just splitting the commit, it was
> also mentioned that the PCI subsystem has no such logic in its
> equivalent pci_do_fixups(): a quirk/fixup needing that should instead
> use a static local.
Why?
There's perfectly nice ->flags there for exactly stuff like that. static
vars are ugly and should be avoided if possible.
> What is special about patch 3?
Nothing special. It is just ugly.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
