From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org
Subject: Re: media: pci: Use PCI_DEVICE macros and drop zeros from pci_device_id arrays
Date: Thu, 7 May 2026 11:10:07 +0200 [thread overview]
Message-ID: <afxV1qkHJaHbmtk2@monoceros> (raw)
In-Reply-To: <69fbbba5.050a0220.1ee6cd.0145@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]
Hello,
On Wed, May 06, 2026 at 03:07:33PM -0700, Patchwork Integration wrote:
> Dear Uwe Kleine-König (The Capable Hub):
>
> Thanks for your patches! Unfortunately the Media CI robot detected some
> issues:
>
> # Test media-patchstyle:./0001-media-pci-Use-PCI_DEVICE-macros-and-drop-zeros-from-.patch media style
> ERROR: ./0001-media-pci-Use-PCI_DEVICE-macros-and-drop-zeros-from-.patch: Missing committer Ricardo Ribalda <ribalda@chromium.org> Signed-off-by
I don't understand that one. Ricardo has nothing to do with creating and
applying the patch so far, so why should there be an S-o-b by them?
> # Test checkpatch:./0001-media-pci-Use-PCI_DEVICE-macros-and-drop-zeros-from-.patch checkpatch
> CHECK: No space is necessary after a cast
> #2473: FILE: drivers/media/pci/saa7146/hexium_gemini.c:365:
> +.driver_data = (unsigned long) &hexium_gemini_4bnc,
>
> CHECK: No space is necessary after a cast
> #2486: FILE: drivers/media/pci/saa7146/hexium_gemini.c:369:
> +.driver_data = (unsigned long) &hexium_gemini_dual_4bnc,
>
> CHECK: No space is necessary after a cast
> #2524: FILE: drivers/media/pci/saa7146/hexium_orion.c:429:
> +.driver_data = (unsigned long) &hexium_hv_pci6,
>
> CHECK: No space is necessary after a cast
> #2527: FILE: drivers/media/pci/saa7146/hexium_orion.c:432:
> +.driver_data = (unsigned long) &hexium_orion_1svhs_3bnc,
>
> CHECK: No space is necessary after a cast
> #2530: FILE: drivers/media/pci/saa7146/hexium_orion.c:435:
> +.driver_data = (unsigned long) &hexium_orion_4bnc,
I didn't introduce these, but can cleanup that en passant. IMHO it's ok
to leave it as is because I will touch these lines in the (hopefully
near) future anyhow to make them
.driver_data_ptr = &hexium_orion_4bnc,
.
Please tell me about your expectations here.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-05-07 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 17:44 [PATCH] media: pci: Use PCI_DEVICE macros and drop zeros from pci_device_id arrays Uwe Kleine-König (The Capable Hub)
[not found] ` <69fbbba5.050a0220.1ee6cd.0145@mx.google.com>
2026-05-07 9:10 ` Uwe Kleine-König (The Capable Hub) [this message]
2026-05-07 21:02 ` Ricardo Ribalda Delgado
2026-05-07 15:17 ` [PATCH] " Uwe Kleine-König (The Capable Hub)
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=afxV1qkHJaHbmtk2@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.