From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Shuah Khan <shuah@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bjorn Helgaas <bhelgaas@google.com>,
kernelci@lists.linux.dev, kernel@collabora.com,
Tim Bird <Tim.Bird@sony.com>,
linux-pci@vger.kernel.org, David Gow <davidgow@google.com>,
linux-kselftest@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Doug Anderson <dianders@chromium.org>,
linux-usb@vger.kernel.org,
Saravana Kannan <saravanak@google.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
Guenter Roeck <groeck@chromium.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] kselftest: Add test to verify probe of devices from discoverable buses
Date: Mon, 29 Dec 2025 11:14:59 -0300 [thread overview]
Message-ID: <8caf35529d2825ba98a8f7ea63ce03d23007292a.camel@collabora.com> (raw)
In-Reply-To: <20251229145542-059157e7-1864-4407-8734-0a32589f9b0b@linutronix.de>
On Mon, 2025-12-29 at 14:57 +0100, Thomas Weißschuh wrote:
> On Mon, Jan 22, 2024 at 03:53:21PM -0300, Nícolas F. R. A. Prado
> wrote:
> > Add a new test to verify that a list of expected devices from
> > discoverable buses (ie USB, PCI) have been successfully
> > instantiated and
> > probed by a driver.
> >
> > The per-platform list of expected devices is selected from the ones
> > under the boards/ directory based on the DT compatible or the DMI
> > IDs.
> >
> > Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
> > ---
> > tools/testing/selftests/Makefile | 1 +
> > tools/testing/selftests/devices/Makefile | 4 +
>
> > tools/testing/selftests/devices/ksft.py | 90 ++++++
>
> This seems to be a copy of tools/testing/selftests/kselftest/ksft.py.
> Instead of copying the file, try to use it from the standard
> location.
This series is almost 1 year old and has long ago been merged :)
--
Thanks,
Nícolas
next prev parent reply other threads:[~2025-12-29 14:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 18:53 [PATCH v4 0/3] Add test to verify probe of devices from discoverable buses Nícolas F. R. A. Prado
2024-01-22 18:53 ` [PATCH v4 1/3] kselftest: " Nícolas F. R. A. Prado
2025-12-29 13:57 ` Thomas Weißschuh
2025-12-29 14:14 ` Nícolas F. R. A. Prado [this message]
2024-01-22 18:53 ` [PATCH v4 2/3] kselftest: devices: Add sample board file for google,spherion Nícolas F. R. A. Prado
2024-01-22 18:53 ` [PATCH v4 3/3] kselftest: devices: Add sample board file for XPS 13 9300 Nícolas F. R. A. Prado
2024-01-23 11:08 ` AngeloGioacchino Del Regno
2024-01-23 14:50 ` Nícolas F. R. A. Prado
2025-12-28 5:47 ` Askar Safin
2025-12-29 13:42 ` Nícolas F. R. A. Prado
2025-12-30 11:36 ` Askar Safin
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=8caf35529d2825ba98a8f7ea63ce03d23007292a.camel@collabora.com \
--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 \
--cc=thomas.weissschuh@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