From: Lukas Wunner <lukas@wunner.de>
To: Alistair Francis <alistair23@gmail.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Greg KH <gregkh@linuxfoundation.org>,
bhelgaas@google.com, linux-pci@vger.kernel.org,
alex.williamson@redhat.com, christian.koenig@amd.com,
kch@nvidia.com, logang@deltatee.com,
linux-kernel@vger.kernel.org,
Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [PATCH v2] PCI/DOE: Expose the DOE protocols via sysfs
Date: Fri, 4 Aug 2023 18:05:42 +0200 [thread overview]
Message-ID: <20230804160542.GA19120@wunner.de> (raw)
In-Reply-To: <CAKmqyKNypBUPNK37wby-0_7G2-10BmZ4f8WQbevVn9uX1mZreQ@mail.gmail.com>
On Fri, Aug 04, 2023 at 11:17:59AM -0400, Alistair Francis wrote:
> On Wed, Aug 2, 2023 at 6:52???PM Lukas Wunner <lukas@wunner.de> wrote:
> > I kind of like the approach of exposing a list which can be grep'ed,
> > even though it may go against the rule of having just one datum per
> > attribute. I'd prefer a representation that's human-readable though,
> > e.g. "0001:01" for CMA-SPDM.
>
> Yeah, it's my preferred method as well, but it's not going to be
> accepted upstream
How about procfs instead of sysfs?
No "single datum per file" rule over there.
PCI content goes into /proc/bus/pci/.
Already used by lspci to access config space.
Thanks,
Lukas
next prev parent reply other threads:[~2023-08-04 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 12:18 [PATCH v2] PCI/DOE: Expose the DOE protocols via sysfs Alistair Francis
2023-08-01 13:25 ` Greg KH
2023-08-01 13:28 ` Greg KH
2023-08-01 13:48 ` Alistair Francis
2023-08-01 16:07 ` Jonathan Cameron
2023-08-01 18:24 ` Alistair Francis
2023-08-02 22:52 ` Lukas Wunner
2023-08-04 15:17 ` Alistair Francis
2023-08-04 16:05 ` Lukas Wunner [this message]
2023-08-05 5:59 ` Greg KH
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=20230804160542.GA19120@wunner.de \
--to=lukas@wunner.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=alex.williamson@redhat.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
/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