Linux PCI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Dave Airlie" <airlied@gmail.com>
Cc: kvm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH] pci/vgaarb: pass a data pointer to be used in the decode callback
Date: Tue, 22 Sep 2026 06:48:13 +0000	[thread overview]
Message-ID: <20260922064814.2651D1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260922064111.2468741-1-airlied@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] drm/loongson: missed vga_client_register API conversion breaks build
--

commit 53a905b209a5cf4aa1aeb17a42069c191d47a151
Author: Dave Airlie <airlied@redhat.com>

pci/vgaarb: pass a data pointer to be used in the decode callback

This commit updates the vga_client_register() API to accept a void *data
pointer, which is then passed to the decode callback. It also updates
various DRM drivers and VFIO to pass and use this new private data pointer.

[ ... ]

> diff --git a/include/linux/vgaarb.h b/include/linux/vgaarb.h
> index 97129a1bbb7df..71a364669eaf8 100644
> --- a/include/linux/vgaarb.h
> +++ b/include/linux/vgaarb.h
> @@ -33,7 +33,8 @@ struct pci_dev *vga_default_device(void);
>  void vga_set_default_device(struct pci_dev *pdev);
>  int vga_remove_vgacon(struct pci_dev *pdev);
>  int vga_client_register(struct pci_dev *pdev,
> -		unsigned int (*set_decode)(struct pci_dev *pdev, bool state));
> +		unsigned int (*set_decode)(void *data, bool state),
> +		void *data);

[Severity: Low]
Does this API change break the build for the loongson DRM driver?

It looks like the conversion of vga_client_register() missed lsdc_pci_probe()
in drivers/gpu/drm/loongson/lsdc_drv.c:

drivers/gpu/drm/loongson/lsdc_drv.c:lsdc_pci_probe() {
    ...
	vga_client_register(pdev, lsdc_vga_set_decode);
    ...
}

The callback lsdc_vga_set_decode() also still expects a struct pci_dev *
rather than void *data.

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260922064111.2468741-1-airlied@gmail.com?part=1

  reply	other threads:[~2026-09-22  6:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22  6:41 [PATCH] pci/vgaarb: pass a data pointer to be used in the decode callback Dave Airlie
2026-09-22  6:48 ` sashiko-bot [this message]
2026-09-24  2:09 ` kernel test robot
2026-09-24  3:03 ` kernel test robot
2026-09-24  5:15 ` kernel test robot
2026-09-24 19:12 ` Bjorn Helgaas

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=20260922064814.2651D1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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