Thanks, I will leave it that way as it will make my life easier (with automatic vim tools and automation) and doesn't really break code understanding.
On Mon, May 04, 2020 at 01:16:10PM +0300, Shenhar, Talel wrote:
checkpatch.pl - while useful - should not be taken to the letter andI rather avoid having this as a checkpatch warnning... (automation and+ mci = edac_mc_alloc(0, ARRAY_SIZE(layers), layers,You can let that line stick out.
+ sizeof(struct al_mc_edac));
stuff...)
human brain should be applied to sanity check it what it warns about.
This line break does seems to my eye as too hard to read.I'm just sayin' - in the end of the day you'll be staring at that code -
Let me know if you feel strongly about it.
not me - so whatever *you* prefer. :-)
Just don't follow tools blindly.
Shall be part of v7.
That warrants a comment above it.Correct.+ if (al_mc->irq_ue <= 0 || al_mc->irq_ce <= 0)Shouldn't this be && here?
I mean, you want to poll when neither of the IRQs can be found. But then
if you find one of them and not the other, what do you do? Poll and
interrupt? Is that case even possible?
In case dt defined interrupt line only for one type and not for the other,
than the interrupt mode shall be used for one of them while polling mode for
the other.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette