From: "Martin Mareš" <mj@ucw.cz>
To: "Pali Rohár" <pali@kernel.org>
Cc: "Bjorn Helgaas" <helgaas@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Matthew Wilcox" <willy@infradead.org>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH pciutils 0/4] Support for PCI_FILL_DRIVER
Date: Fri, 21 Jan 2022 15:46:20 +0100 [thread overview]
Message-ID: <mj+md-20220121.144118.18107.nikam@ucw.cz> (raw)
In-Reply-To: <20220121144007.rmocpkiy32slhbzb@pali>
Hello!
> Reported data are exactly same. Just with this change lspci can report
> driver also for non-sysfs backend (e.g. procfs backend or new WIP win32
> backend).
>
> Basically sysfs logic from lspci executable was moved into the libpci
> library and therefore now it is available also for other applications.
I am not convinced that it is right to make something with so vague
semantics a part of libpci API.
The procfs back-end is a pretty weak motivation, because it's long obsolete
and basically I haven't dropped it yet only because it takes more effort
than letting it stay :-)
Now, the win32 back-end could be intersting, but let's make it mergeable
in its basic form first.
Martin
prev parent reply other threads:[~2022-01-21 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 14:03 [PATCH pciutils 0/4] Support for PCI_FILL_DRIVER Pali Rohár
2022-01-21 14:03 ` [PATCH pciutils 1/4] libpci: Define new string property PCI_FILL_DRIVER Pali Rohár
2022-01-21 14:03 ` [PATCH pciutils 2/4] libpci: proc: Implement support for PCI_FILL_DRIVER Pali Rohár
2022-01-21 14:03 ` [PATCH pciutils 3/4] libpci: sysfs: " Pali Rohár
2022-01-21 14:03 ` [PATCH pciutils 4/4] lspci: Replace find_driver() via libpci PCI_FILL_DRIVER Pali Rohár
2022-01-21 14:31 ` [PATCH pciutils 0/4] Support for PCI_FILL_DRIVER Martin Mareš
2022-01-21 14:40 ` Pali Rohár
2022-01-21 14:46 ` Martin Mareš [this message]
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=mj+md-20220121.144118.18107.nikam@ucw.cz \
--to=mj@ucw.cz \
--cc=helgaas@kernel.org \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=pali@kernel.org \
--cc=willy@infradead.org \
/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).