From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
To: "Bird, Tim" <Tim.Bird@sony.com>
Cc: Shuah Khan <shuah@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Saravana Kannan <saravanak@google.com>,
Rob Herring <robh+dt@kernel.org>,
"kernelci@lists.linux.dev" <kernelci@lists.linux.dev>,
David Gow <davidgow@google.com>,
Guenter Roeck <groeck@chromium.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"kernel@collabora.com" <kernel@collabora.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Doug Anderson <dianders@chromium.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v2 2/2] kselftest: devices: Add sample board file for google,spherion
Date: Tue, 28 Nov 2023 09:43:53 -0500 [thread overview]
Message-ID: <ee913bc5-c752-4da7-a140-7492f429c2cb@notapiano> (raw)
In-Reply-To: <BN8PR13MB27384F089C7DAAF06DF9DDECFDBCA@BN8PR13MB2738.namprd13.prod.outlook.com>
On Tue, Nov 28, 2023 at 12:10:46AM +0000, Bird, Tim wrote:
> > -----Original Message-----
> > From: Nícolas F. R. A. Prado <nfraprado@collabora.com>
> > Add a sample board file describing the file's format and with the list
> > of devices expected to be probed on the google,spherion machine as an
> > example.
> >
> > Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
> > ---
> >
> > (no changes since v1)
> >
> > .../testing/selftests/devices/boards/google,spherion | 12 ++++++++++++
>
> Overall, while trying to maintain a comprehensive set of board definitions
> seems hard, I think having a few as examples is useful.
>
> I'm not a big fan of naming these with a comma in the name. Is there a reason
> you are not using dash or underscore?
I'm using the name that we get from the DT compatible, so the right file can be
automatically selected by the test.
>
> Do you anticipate a convention of <producer> <board-or-product-name> tuples for
> the filename?
I'd just stick to the DT compatible as it's the simplest option and should work
just the same, assuming I understood correctly what you mean.
Thanks,
Nícolas
next prev parent reply other threads:[~2023-11-28 14:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 23:34 [RFC PATCH v2 0/2] Add test to verify probe of devices from discoverable busses Nícolas F. R. A. Prado
2023-11-27 23:34 ` [RFC PATCH v2 1/2] kselftest: " Nícolas F. R. A. Prado
2023-11-27 23:34 ` [RFC PATCH v2 2/2] kselftest: devices: Add sample board file for google,spherion Nícolas F. R. A. Prado
2023-11-28 0:10 ` Bird, Tim
2023-11-28 14:10 ` Mark Brown
2023-11-28 14:43 ` Nícolas F. R. A. Prado [this message]
2023-11-28 17:54 ` Bird, Tim
2023-11-28 19:52 ` Nícolas F. R. A. Prado
2023-11-28 17:59 ` Christopher Obbard
2023-11-28 18:33 ` Bird, Tim
2023-11-28 21:05 ` Nícolas F. R. A. Prado
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=ee913bc5-c752-4da7-a140-7492f429c2cb@notapiano \
--to=nfraprado@collabora.com \
--cc=Tim.Bird@sony.com \
--cc=bhelgaas@google.com \
--cc=dan.carpenter@linaro.org \
--cc=davidgow@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=kernel@collabora.com \
--cc=kernelci@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=saravanak@google.com \
--cc=shuah@kernel.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