Linux Media Controller development
 help / color / mirror / Atom feed
From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Hans Verkuil <hverkuil@kernel.org>,
	 Andy Walls <awalls@md.metrocast.net>,
	Yong Zhi <yong.zhi@intel.com>,
	 Sakari Ailus <sakari.ailus@linux.intel.com>,
	Dan Scally <dan.scally@ideasonboard.com>,
	 Martin Tuma <martin.tuma@digiteqautomotive.com>,
	Abylay Ospan <aospan@amazon.com>,
	 Bluecherry Maintainers <maintainers@bluecherrydvr.com>,
	Ismael Luceno <ismael@iodev.co.uk>,
	 Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	Corentin Labbe <clabbe@baylibre.com>,
	 Jai Luthra <jai.luthra@linux.dev>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	 Kees Cook <kees@kernel.org>,
	Bradford Love <brad@nextdimension.cc>,
	 Wang Jun <1742789905@qq.com>,
	Atharv Dubey <atharvd440@gmail.com>,
	 Haoxiang Li <lihaoxiang@isrc.iscas.ac.cn>,
	Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
	 Sean Young <sean@mess.org>, Zhaoyang Yu <2426767509@qq.com>,
	linux-media@vger.kernel.org,  linux-kernel@vger.kernel.org,
	mjpeg-users@lists.sourceforge.net,
	 Markus Schneider-Pargmann <msp@baylibre.com>
Subject: Re: [PATCH] media: pci: Use PCI_DEVICE macros and drop zeros from pci_device_id arrays
Date: Mon, 29 Jun 2026 19:19:12 +0200	[thread overview]
Message-ID: <akKouitA4lNoqios@monoceros> (raw)
In-Reply-To: <20260629171254.3470651-2-u.kleine-koenig@baylibre.com>

[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]

Hello,

On Mon, Jun 29, 2026 at 07:12:54PM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> Some pci_device_id arrays already used the PCI_DEVICE macros, others
> used named initializers or list initializers. Unify all to use the
> PCI_DEVICE macros and (if applicable) a named initializer for
> .driver_data. Also drop all zeros that the compiler can care for and
> unify indention and spacing.
> 
> Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
> ---
> Hello,
> 
> v2 can be found at https://lore.kernel.org/linux-media/423da5a0ba0c9371c3d30011ed245f596d70b58b.1781020630.git.u.kleine-koenig@baylibre.com
> 
> Changes since then:
>     
>  - Fix code-styling as pointed out by the Media CI robot (instead of
>    keeping the style as it was) in
>    drivers/media/pci/saa7146/hexium_{gemini,orion}.c
> 
>  - rebased to next/master
> 
> Note I already claimed to have fixed the coding-style in v2, but I
> failed to commit that. Just mention it to prevent further confusion.

I again failed to send this out properly: I forgot to add "v3" to the
Subject and to remove the prerequisite-patch-id lines below.

Please tell me if I should resend.

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2026-06-29 17:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29 17:12 [PATCH] media: pci: Use PCI_DEVICE macros and drop zeros from pci_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-06-29 17:19 ` Uwe Kleine-König (The Capable Hub) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-06 17:44 Uwe Kleine-König (The Capable Hub)
2026-05-07 15:17 ` 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=akKouitA4lNoqios@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=1742789905@qq.com \
    --cc=2426767509@qq.com \
    --cc=aospan@amazon.com \
    --cc=atharvd440@gmail.com \
    --cc=awalls@md.metrocast.net \
    --cc=brad@nextdimension.cc \
    --cc=clabbe@baylibre.com \
    --cc=dan.scally@ideasonboard.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=hverkuil@kernel.org \
    --cc=ismael@iodev.co.uk \
    --cc=jai.luthra@linux.dev \
    --cc=kees@kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=lihaoxiang@isrc.iscas.ac.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=maintainers@bluecherrydvr.com \
    --cc=martin.tuma@digiteqautomotive.com \
    --cc=mchehab@kernel.org \
    --cc=mjpeg-users@lists.sourceforge.net \
    --cc=msp@baylibre.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sean@mess.org \
    --cc=yong.zhi@intel.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