From: Johan Hovold <johan@kernel.org>
To: linux-media@vger.kernel.org
Subject: Re: [0/6] media: refactor USB endpoint lookups
Date: Mon, 30 Mar 2026 16:16:52 +0200 [thread overview]
Message-ID: <acqF1CyUUy2E_MoK@hovoldconsulting.com> (raw)
In-Reply-To: <69ca8460.050a0220.acff7.105a@mx.google.com>
On Mon, Mar 30, 2026 at 07:10:40AM -0700, Patchwork Integration wrote:
> Thanks for your patches! Unfortunately the Media CI robot detected some
> issues:
>
> # Test checkpatch:./0005-media-hdpvr-refactor-endpoint-lookup.patch checkpatch
> CHECK: Avoid CamelCase: <bulk_in_endpointAddr>
> #62: FILE: drivers/media/usb/hdpvr/hdpvr-core.c:331:
> +dev->bulk_in_endpointAddr = endpoint->bEndpointAddress;
>
> total: 0 errors, 0 warnings, 1 checks, 46 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.
> 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.
Checkpatch is complaining about an existing issue in the driver so this
bot warning is not valid.
Johan
prev parent reply other threads:[~2026-03-30 14:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 10:11 [PATCH 0/6] media: refactor USB endpoint lookups Johan Hovold
2026-03-30 10:11 ` [PATCH 1/6] media: si470x-usb: refactor endpoint lookup Johan Hovold
2026-03-30 10:11 ` [PATCH 2/6] media: imon_raw: " Johan Hovold
2026-03-30 10:11 ` [PATCH 3/6] media: irtoy: " Johan Hovold
2026-03-30 10:11 ` [PATCH 4/6] media: gspca: " Johan Hovold
2026-03-30 10:11 ` [PATCH 5/6] media: hdpvr: " Johan Hovold
2026-03-30 10:11 ` [PATCH 6/6] media: s2255: " Johan Hovold
[not found] ` <69ca8460.050a0220.acff7.105a@mx.google.com>
2026-03-30 14:16 ` Johan Hovold [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=acqF1CyUUy2E_MoK@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=linux-media@vger.kernel.org \
/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