Hello,
Thanks for the remarks.
The commit is exactly the same as in the mainline commit.
The upstreamed commit, is mentioned in that way, because when I used the full hash, I was getting this error from scripts/checkpatch.pl:
ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")' #10:
Regards, Sergio
On Sun, 8 Jun 2025 at 17:59, Miguel Ojeda miguel.ojeda.sandonis@gmail.com wrote:
On Sun, Jun 8, 2025 at 4:55 PM Sergio González Collado sergio.collado@gmail.com wrote:
commit c104c16073b7 ("Kunit to check the longest symbol length") upstream
I think this may need to be the full hash, and a period at the end:
commit c104c16073b7fdb3e4eae18f66f4009f6b073d6f upstream.But like in the other patch, maybe the stable team's tooling still picks it up or maybe they fix it manually.
However, more importantly, is there any difference w.r.t. the original mainline commit?
If yes, what the difference is should be mentioned.
If not, this probably could just be Option 2, since at least if I take the hash I can directly apply it (auto-merged). Same for the other patch.
Thanks!
Cheers, Miguel