Hello,
Should I resend the patch v2 with the full hash? or is it ok as Miguel already mentioned it?
commit c104c16073b7fdb3e4eae18f66f4009f6b073d6f upstream.
Either way would be ok for me.
Sergio
On Tue, 17 Jun 2025 at 16:00, Greg KH gregkh@linuxfoundation.org wrote:
On Sun, Jun 08, 2025 at 06:10:13PM +0200, Sergio González Collado wrote:
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")'
No need to run checkpatch on stuff you are backporting to stable, as it should follow the same style as what ever is in Linus's tree.
We need/want the full hash here.
thanks,
greg k-h