Re: [PATCH v2 00/15] NTB: Add full multi-port API support to the test drivers

From: Logan Gunthorpe
Date: Tue Dec 05 2017 - 11:57:56 EST




On 05/12/17 08:54 AM, Serge Semin wrote:
Yeah, I know that. As I already said, it isn't usual of my patches
being so complicated. The reason why I made so many small renamings
was the code refactoring. I tried to set all the test drivers code
up to the same naming convention, so it would be easier for a code
reader to study it. Definitely, such the alterations should have
been done within a separate patch. But I started refactoring the
code and changing the logic for multi-portness all together, so it
would be too painful to unpick one from another after the work was
done. It especially concerned the ntb_tool and ntb_perf drivers. Next
time the procedures will be separately. Sorry for inconvenience and
thanks for understanding.

It's really not that hard, using git, to refactor a patch. If it's such a mess that you can't refactor it then it's probably a good indication that said patch should not be merged. The vast majority of other maintainers in the kernel would never accept such a large convoluted patch as it's too difficult to determine if something unintended changed and it makes debugging and bisecting (once it's merged) more difficult. Not to mention the fact that few developers are willing to put in the time to untangle it enough to properly review.

Oops. We discussed it in the IRC. We agreed to add commentaries
around the types definition, so a reader would better understand their
purpose. I just forgot to move the change from my repo to the fork of
Jon's one. I'll do it and resend the patch.

I agree with Allen. The unions are completely unnecessary. If there was a space constraint then they could be justified but we really don't have that here. In my opinion, you should just drop them -- a comment doesn't really improve things much.

Logan