From: Bjorn Helgaas <helgaas@kernel.org>
To: Philipp Stanner <pstanner@redhat.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
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>,
Sam Ravnborg <sam@ravnborg.org>,
dakr@redhat.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 00/10] Make PCI's devres API more consistent
Date: Tue, 16 Jan 2024 12:29:43 -0600 [thread overview]
Message-ID: <20240116182943.GA101377@bhelgaas> (raw)
In-Reply-To: <20240115144655.32046-2-pstanner@redhat.com>
On Mon, Jan 15, 2024 at 03:46:11PM +0100, Philipp Stanner wrote:
> ...
> pci: add new set of devres functions
> pci: deprecate iomap-table functions
> pci: warn users about complicated devres nature
> pci: devres: make devres region requests consistent
> pci: move enabled status bit to pci_dev struct
> pci: move pinned status bit to pci_dev struct
> pci: devres: give mwi its own callback
> pci: devres: give pci(m)_intx its own callback
> pci: devres: remove legacy pcim_release()
> drm/vboxvideo: fix mapping leaks
If/when you update these, take a look at the drivers/pci/ subject line
history and capitalize these to match.
We haven't really used the "devres" prefix in drivers/pci.
The de facto convention is:
- "PCI/AER:" for major features defined by the PCIe base spec (AER,
DPC, VGA, ASPM, PM, etc).
- "PCI: iproc:" for controller drivers (iproc, dwc, qcom, mvebu,
etc).
- "PCI:" for everything else
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <helgaas@kernel.org>
To: Philipp Stanner <pstanner@redhat.com>
Cc: Daniel Vetter <daniel@ffwll.ch>, Jonathan Corbet <corbet@lwn.net>,
Sam Ravnborg <sam@ravnborg.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Maxime Ripard <mripard@kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
dakr@redhat.com, dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
David Airlie <airlied@gmail.com>
Subject: Re: [PATCH 00/10] Make PCI's devres API more consistent
Date: Tue, 16 Jan 2024 12:29:43 -0600 [thread overview]
Message-ID: <20240116182943.GA101377@bhelgaas> (raw)
In-Reply-To: <20240115144655.32046-2-pstanner@redhat.com>
On Mon, Jan 15, 2024 at 03:46:11PM +0100, Philipp Stanner wrote:
> ...
> pci: add new set of devres functions
> pci: deprecate iomap-table functions
> pci: warn users about complicated devres nature
> pci: devres: make devres region requests consistent
> pci: move enabled status bit to pci_dev struct
> pci: move pinned status bit to pci_dev struct
> pci: devres: give mwi its own callback
> pci: devres: give pci(m)_intx its own callback
> pci: devres: remove legacy pcim_release()
> drm/vboxvideo: fix mapping leaks
If/when you update these, take a look at the drivers/pci/ subject line
history and capitalize these to match.
We haven't really used the "devres" prefix in drivers/pci.
The de facto convention is:
- "PCI/AER:" for major features defined by the PCIe base spec (AER,
DPC, VGA, ASPM, PM, etc).
- "PCI: iproc:" for controller drivers (iproc, dwc, qcom, mvebu,
etc).
- "PCI:" for everything else
next prev parent reply other threads:[~2024-01-16 18:29 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 14:46 [PATCH 00/10] Make PCI's devres API more consistent Philipp Stanner
2024-01-15 14:46 ` Philipp Stanner
2024-01-15 14:46 ` [PATCH 01/10] pci: add new set of devres functions Philipp Stanner
2024-01-15 14:46 ` Philipp Stanner
2024-01-16 18:44 ` Bjorn Helgaas
2024-01-16 18:44 ` Bjorn Helgaas
2024-01-17 8:54 ` Philipp Stanner
2024-01-17 8:54 ` Philipp Stanner
2024-01-19 22:52 ` Bjorn Helgaas
2024-01-19 22:52 ` Bjorn Helgaas
2024-01-16 21:15 ` andy.shevchenko
2024-01-16 21:15 ` andy.shevchenko
2024-01-17 9:21 ` Philipp Stanner
2024-01-17 9:21 ` Philipp Stanner
2024-01-15 14:46 ` [PATCH 02/10] pci: deprecate iomap-table functions Philipp Stanner
2024-01-15 14:46 ` Philipp Stanner
2024-01-16 21:27 ` andy.shevchenko
2024-01-16 21:27 ` andy.shevchenko
2024-01-17 9:40 ` Philipp Stanner
2024-01-17 9:40 ` Philipp Stanner
2024-01-15 14:46 ` [PATCH 03/10] pci: warn users about complicated devres nature Philipp Stanner
2024-01-15 14:46 ` Philipp Stanner
2024-01-15 14:46 ` [PATCH 04/10] pci: devres: make devres region requests consistent Philipp Stanner
2024-01-15 14:46 ` Philipp Stanner
2024-01-16 21:29 ` andy.shevchenko
2024-01-16 21:29 ` andy.shevchenko
2024-01-15 14:46 ` [PATCH 05/10] pci: move enabled status bit to pci_dev struct Philipp Stanner
2024-01-15 14:46 ` Philipp Stanner
2024-01-15 14:46 ` [PATCH 06/10] pci: move pinned " Philipp Stanner
2024-01-15 14:46 ` Philipp Stanner
2024-01-16 21:34 ` andy.shevchenko
2024-01-16 21:34 ` andy.shevchenko
2024-01-17 9:02 ` Philipp Stanner
2024-01-17 9:02 ` Philipp Stanner
2024-01-15 14:46 ` [PATCH 07/10] pci: devres: give mwi its own callback Philipp Stanner
2024-01-15 14:46 ` Philipp Stanner
2024-01-16 18:35 ` Bjorn Helgaas
2024-01-16 18:35 ` Bjorn Helgaas
2024-01-15 14:46 ` [PATCH 08/10] pci: devres: give pci(m)_intx " Philipp Stanner
2024-01-15 14:46 ` Philipp Stanner
2024-01-16 21:37 ` andy.shevchenko
2024-01-16 21:37 ` andy.shevchenko
2024-01-15 14:46 ` [PATCH 09/10] pci: devres: remove legacy pcim_release() Philipp Stanner
2024-01-15 14:46 ` Philipp Stanner
2024-01-16 21:40 ` andy.shevchenko
2024-01-16 21:40 ` andy.shevchenko
2024-01-17 13:49 ` Philipp Stanner
2024-01-17 13:49 ` Philipp Stanner
2024-01-15 14:46 ` [PATCH 10/10] drm/vboxvideo: fix mapping leaks Philipp Stanner
2024-01-15 14:46 ` Philipp Stanner
2024-01-16 18:29 ` Bjorn Helgaas [this message]
2024-01-16 18:29 ` [PATCH 00/10] Make PCI's devres API more consistent Bjorn Helgaas
2024-01-16 21:17 ` andy.shevchenko
2024-01-16 21:17 ` andy.shevchenko
2024-01-17 9:59 ` Philipp Stanner
2024-01-17 9:59 ` Philipp Stanner
2024-01-18 8:48 ` Philipp Stanner
2024-01-18 8:48 ` Philipp Stanner
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=20240116182943.GA101377@bhelgaas \
--to=helgaas@kernel.org \
--cc=airlied@gmail.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=dakr@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=linux-doc@vger.kernel.org \
--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=sam@ravnborg.org \
--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 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.