public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	Sam Ravnborg <sam@ravnborg.org>,
	dakr@redhat.com, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 00/10] Make PCI's devres API more consistent
Date: Thu, 29 Feb 2024 14:57:15 -0600	[thread overview]
Message-ID: <20240229205715.GA362688@bhelgaas> (raw)
In-Reply-To: <2057fd477ad404c9adf603eac1ad933c04ecf293.camel@redhat.com>

On Thu, Feb 29, 2024 at 09:31:20AM +0100, Philipp Stanner wrote:
> @Bjorn:
> Hey Bjorn, are we good with this series? Any more wishes or
> suggestions?

Sorry, haven't had a chance to go through it yet.  

FWIW, I just tried to apply these on top of pci/devres, but it failed
here:

  Applying: PCI: Add new set of devres functions
  Applying: PCI: Deprecate iomap-table functions
  Applying: PCI: Warn users about complicated devres nature
  Applying: PCI: Make devres region requests consistent
  Applying: PCI: Move dev-enabled status bit to struct pci_dev
  error: patch failed: drivers/pci/pci.h:811
  error: drivers/pci/pci.h: patch does not apply
  Patch failed at 0005 PCI: Move dev-enabled status bit to struct pci_dev

Haven't investigated, so maybe it's some trivial easily fixed thing.

Bjorn

  reply	other threads:[~2024-02-29 20:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 13:39 [PATCH v3 00/10] Make PCI's devres API more consistent Philipp Stanner
2024-02-06 13:39 ` [PATCH v3 01/10] PCI: Add new set of devres functions Philipp Stanner
2024-02-06 13:39 ` [PATCH v3 02/10] PCI: Deprecate iomap-table functions Philipp Stanner
2024-02-06 13:39 ` [PATCH v3 03/10] PCI: Warn users about complicated devres nature Philipp Stanner
2024-02-06 13:39 ` [PATCH v3 04/10] PCI: Make devres region requests consistent Philipp Stanner
2024-02-06 13:39 ` [PATCH v3 05/10] PCI: Move dev-enabled status bit to struct pci_dev Philipp Stanner
2024-02-06 13:39 ` [PATCH v3 06/10] PCI: Move pinned " Philipp Stanner
2024-02-06 13:39 ` [PATCH v3 07/10] PCI: Give pcim_set_mwi() its own devres callback Philipp Stanner
2024-02-06 13:39 ` [PATCH v3 08/10] PCI: Give pci(m)_intx " Philipp Stanner
2024-02-06 13:39 ` [PATCH v3 09/10] PCI: Remove legacy pcim_release() Philipp Stanner
2024-02-06 13:39 ` [PATCH v3 10/10] drm/vboxvideo: fix mapping leaks Philipp Stanner
2024-02-29  8:31 ` [PATCH v3 00/10] Make PCI's devres API more consistent Philipp Stanner
2024-02-29 20:57   ` Bjorn Helgaas [this message]
2024-03-01  9:29     ` 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=20240229205715.GA362688@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=airlied@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=dakr@redhat.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox