Conversation

Jarkko Sakkinen

@ljs you got it, i did my fedora ark test (compile a random tip as distribution kernel) with a "random patch set".
1
0
0
@ljs i guess it goes as a review by itself that i could understand the code changes despite somewhat alien subsystem internals (thus ack's). it's usually a good sign at least.
1
0
0
@jarkko @ljs note it's nice when adding just acked-by/tested-by with no code comments to do it right under s-o-b and remove the code :) and when the comments are only to some parts of the code, also trim the nrelated ones. Please consider next time :) Thanks.
1
0
2

Jarkko Sakkinen

Edited 26 days ago
@vbabka @ljs sure, i can do that. different subsystem have different expectations about everything so you cannot know without sending something, so if i don't put anything extensive, i do as little as possible and wait for suggestions like this.

i'm sure that my tags plus minor comments can still be relatively easily accessed but next time i'll follow the advice.

edit: lol put my signature into the comment (removed)
2
0
1
@vbabka @ljs Like in some arch-tree's I've been asked not to use "we" but instead imperative passive in commit messages whereas in other subsystems that is perfectly fine.

"don't do before do, and then do following the feedback" is my "minimum rant heuristics" :-)
0
0
1
@jarkko @vbabka it was really hard for me to read, best to put it after signed-off esp with a ton of code like the tests!

Appreciate you (even accidentally) checking this + giving tags though. Glad it works for you also.
1
0
2
@ljs @vbabka ya keep this in mind, my language model has now been upgraded ;-)
0
0
1