From: Christian Hewitt <christianshewitt@gmail.com>
To: "Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Peter Rosin" <peda@axentia.se>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [v2] media: si2168: increase cmd execution timeout value
Date: Wed, 2 Jul 2025 12:13:21 +0400 [thread overview]
Message-ID: <796D5DD1-D49E-4B9B-9F20-7FC5A88DD37B@gmail.com> (raw)
In-Reply-To: <67ea654f.050a0220.2a49ac.2402@mx.google.com>
> On 31 Mar 2025, at 1:50 pm, Patchwork Integration <patchwork@media-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
prev parent reply other threads:[~2025-07-02 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 8:44 [PATCH v2] " Christian Hewitt
[not found] ` <67ea654f.050a0220.2a49ac.2402@mx.google.com>
2025-07-02 8:13 ` Christian Hewitt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=796D5DD1-D49E-4B9B-9F20-7FC5A88DD37B@gmail.com \
--to=christianshewitt@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=peda@axentia.se \
--cc=tzimmermann@suse.de \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wsa+renesas@sang-engineering.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®