[<prev] [next>] [day] [month] [year] [list]
Message-Id: <796D5DD1-D49E-4B9B-9F20-7FC5A88DD37B@gmail.com>
Date: Wed, 2 Jul 2025 12:13:21 +0400
From: Christian Hewitt <christianshewitt@...il.com>
To: Mauro Carvalho Chehab <mchehab@...nel.org>,
Peter Rosin <peda@...ntia.se>,
Thomas Zimmermann <tzimmermann@...e.de>,
Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
Heiner Kallweit <hkallweit1@...il.com>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
linux-media@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [v2] media: si2168: increase cmd execution timeout value
> On 31 Mar 2025, at 1:50 pm, Patchwork Integration <patchwork@...ia-ci.org> wrote:
>
> Dear Christian Hewitt:
>
> Thanks for your patches! Unfortunately the Media CI robot detected some
> issues:
>
> # Test checkpatch:./0001-media-si2168-increase-cmd-execution-timeout-value.patch checkpatch
> WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
> #9:
> Jan 28 12:23:46.788180 LibreELEC kernel: si2168 1-0060: cmd execution took 0 ms
>
> total: 0 errors, 1 warnings, 0 checks, 25 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/73642454/artifacts/report.htm
Can someone please confirm whether I do need to submit a v3 of
this patch? - the line-length issue flagged by the bot refers
to the patch description text (which has some longer log lines
that demo the issue) not code in the patch. I’d like to get this
merged so I can clear the patch from my distro’s patchset.
Christian
Powered by blists - more mailing lists