Hi, I don't mind sending v2 but I suggest that the warnings below should be ignored. The extra long lines only refer either to syzkaller output log (that I already somewhat butchered to save space) or to Reported-and-tested-by: line that also can't be shortened. As far as I can tell, checkpatch.pl doesn't have any more issues. Regards, Nikita On 1/27/25 10:32, Patchwork Integration wrote: > Dear Nikita Zhandarovich: > > Thanks for your patches! Unfortunately the Media CI robot detected some > issues: > > # Test checkpatch:./0001-media-usb-hackrf-fix-device-unregister-order-in-hack.patch checkpatch > WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?) > #18: > CPU: 1 UID: 0 PID: 7854 Comm: v4l_id Not tainted 6.12.0-rc7-syzkaller-00125-gcfaaa7d010d1 #0 > > WARNING: Possible repeated word: 'Google' > #19: > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024 > > total: 0 errors, 2 warnings, 0 checks, 14 lines checked > > > > Please fix your series, and upload a new version. If you have a patchwork > account, do not forget to mark the current series as Superseded. > > For more details, check the full report at: > https://linux-media.pages.freedesktop.org/-/users/patchwork/-/jobs/70052367/artifacts/report.htm . > > > > Best regards, and Happy Hacking! > Media CI robot on behalf of the linux-media community. > > --- > Check the latest rules for contributing your patches at: > https://docs.kernel.org/driver-api/media/maintainer-entry-profile.html > > If you believe that the CI is wrong, kindly open an issue at > https://gitlab.freedesktop.org/linux-media/media-ci/-/issues or reply-all > to this message. >
