From: Niklas Schnelle <schnelle@linux.ibm.com>
To: mcgrof@kernel.org
Cc: alex.williamson@redhat.com, axboe@kernel.dk, bhelgaas@google.com,
cohuck@redhat.com, eric.auger@redhat.com,
giovanni.cabiddu@intel.com, gregkh@linuxfoundation.org,
jannh@google.com, jeyu@kernel.org, jgg@ziepe.ca,
jikos@kernel.org, jpoimboe@redhat.com, keescook@chromium.org,
kevin.tian@intel.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
mbenes@suse.com, minchan@kernel.org, mjrosato@linux.ibm.com,
ngupta@vflare.org, peterz@infradead.org, rostedt@goodmis.org,
sergey.senozhatsky.work@gmail.com, tglx@linutronix.de
Subject: Re: [PATCH 1/2] pci: export pci_dev_unlock() and the respective unlock
Date: Tue, 22 Jun 2021 09:45:27 +0200 [thread overview]
Message-ID: <20210622074527.3486039-1-schnelle@linux.ibm.com> (raw)
In-Reply-To: <20210622000310.728294-1-mcgrof@kernel.org>
Hello Luis, Hello Bjorn,
Interesting timing, I currently have a very similar patch lying around though
with also exporting pci_dev_lock(). I'm planning to use that for upcoming
support of automatic PCI devices recovery on s390x following the
Documentation/PCI/pci-error-recovery.rst recovery flow. There too exprting
these functions would make the code simpler to grok in my opinion. So if Bjorn
accepts this there could soon be another user, not sure if one would want to
then already export pci_dev_lock() too or wait until my patches so it's not
exported without users.
Best regards,
Niklas Schnelle
next prev parent reply other threads:[~2021-06-22 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 0:03 [PATCH 1/2] pci: export pci_dev_unlock() and the respective unlock Luis Chamberlain
2021-06-22 0:03 ` [PATCH 2/2] vfio: use the new pci_dev_trylock() helper to simplify try lock Luis Chamberlain
2021-06-22 7:45 ` Niklas Schnelle [this message]
2021-06-22 14:57 ` [PATCH 1/2] pci: export pci_dev_unlock() and the respective unlock 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=20210622074527.3486039-1-schnelle@linux.ibm.com \
--to=schnelle@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=axboe@kernel.dk \
--cc=bhelgaas@google.com \
--cc=cohuck@redhat.com \
--cc=eric.auger@redhat.com \
--cc=giovanni.cabiddu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=jeyu@kernel.org \
--cc=jgg@ziepe.ca \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mbenes@suse.com \
--cc=mcgrof@kernel.org \
--cc=minchan@kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=ngupta@vflare.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).