From: Bjorn Helgaas <helgaas@kernel.org>
To: Philipp Stanner <pstanner@redhat.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Bjorn Helgaas <bhelgaas@google.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 0/2] Use pcim_request_region() in vboxvideo
Date: Wed, 31 Jul 2024 14:36:05 -0500 [thread overview]
Message-ID: <20240731193605.GA77260@bhelgaas> (raw)
In-Reply-To: <20240729093625.17561-2-pstanner@redhat.com>
On Mon, Jul 29, 2024 at 11:36:24AM +0200, Philipp Stanner wrote:
> Hi everyone,
>
> Now that we've got the simplified PCI devres API available we can slowly
> start using it in drivers and step by step phase the more problematic
> API out.
>
> vboxvideo currently does not have a region request, so it is a suitable
> first user.
>
> P.
>
> Philipp Stanner (2):
> PCI: Make pcim_request_region() a public function
> drm/vboxvideo: Add PCI region request
>
> drivers/gpu/drm/vboxvideo/vbox_main.c | 4 ++++
> drivers/pci/devres.c | 1 +
> drivers/pci/pci.h | 2 --
> include/linux/pci.h | 1 +
> 4 files changed, 6 insertions(+), 2 deletions(-)
Given an ack from the vboxvideo maintainers, I can apply both of these
via the PCI tree so there's no race during the merge window.
next prev parent reply other threads:[~2024-07-31 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 9:36 [PATCH 0/2] Use pcim_request_region() in vboxvideo Philipp Stanner
2024-07-29 9:36 ` [PATCH 1/2] PCI: Make pcim_request_region() a public function Philipp Stanner
2024-07-29 9:36 ` [PATCH 2/2] drm/vboxvideo: Add PCI region request Philipp Stanner
2024-07-31 19:36 ` Bjorn Helgaas [this message]
2024-08-01 15:15 ` [PATCH 0/2] Use pcim_request_region() in vboxvideo Hans de Goede
2024-08-01 15:14 ` Hans de Goede
2024-08-01 17:04 ` 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=20240731193605.GA77260@bhelgaas \
--to=helgaas@kernel.org \
--cc=airlied@gmail.com \
--cc=bhelgaas@google.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=pstanner@redhat.com \
--cc=tzimmermann@suse.de \
/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