On Thu, Sep 12, 2019 at 08:01:45AM -0700, Joe Perches wrote: > On Thu, 2019-09-12 at 05:17 -0700, Christoph Hellwig wrote: > > Instead of arguing what is better just stick to what the surrounding > > code does. > > That's not always feasible nor readable. > > Especially for the logic inversion blocks where > the existing code does unreadable and error prone > things like hiding semicolons immediately after > comments. > > if (foo) > /* longish comment */; > else { > <code>; > }
Which has nothing to do with your patch. > > Or in other words: Feel free to be a codingstyle nazi for your code > > (I am for some of mine), but leave others peoples code alone with > > "cleanup" patches. > > My point was to avoid documenting per-subsystem > coding style rules. It is called common sense. In many cases different parts of the subsystem might have slight variations. Just stick to your preferred style in the bounds of coding style. Maintainers will either remind you if they feel strongly that they have a slightly different preference or just fix it up. What we really don't need need it whitespace cleanup patches in the micro variation area. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm