From: Bjorn Helgaas <helgaas@kernel.org>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
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: [RFC PATCH v3 0/3] Add test to verify probe of devices from discoverable busses
Date: Thu, 28 Dec 2023 17:53:48 -0600 [thread overview]
Message-ID: <20231228235348.GA1559485@bhelgaas> (raw)
In-Reply-To: <20231227123643.52348-1-nfraprado@collabora.com>
I have no opinion about the patches themselves, but just a heads-up
that "busses" may be regarded as a misspelling of "buses", e.g.,
https://lore.kernel.org/r/20231223184720.25645-1-tintinm2017@gmail.com,
I'm guessing because codespell complains about it.
Git grep says there are almost as many instances of "busses" as
"buses" in the kernel, so I don't go out of my way to change them.
Just FYI, doesn't matter to me either way.
Bjorn
next prev parent reply other threads:[~2023-12-28 23:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 12:34 [RFC PATCH v3 0/3] Add test to verify probe of devices from discoverable busses Nícolas F. R. A. Prado
2023-12-27 12:35 ` [RFC PATCH v3 1/3] kselftest: " Nícolas F. R. A. Prado
2023-12-27 12:35 ` [RFC PATCH v3 2/3] kselftest: devices: Add sample board file for google,spherion Nícolas F. R. A. Prado
2023-12-27 12:35 ` [RFC PATCH v3 3/3] kselftest: devices: Add sample board file for XPS 13 9300 Nícolas F. R. A. Prado
2023-12-28 23:53 ` Bjorn Helgaas [this message]
2023-12-29 12:33 ` [RFC PATCH v3 0/3] Add test to verify probe of devices from discoverable busses Nícolas F. R. A. Prado
2024-01-02 7:45 ` Dan Carpenter
2024-01-02 13:12 ` Nícolas F. R. A. Prado
2024-01-04 14:54 ` Mark Brown
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=20231228235348.GA1559485@bhelgaas \
--to=helgaas@kernel.org \
--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=nfraprado@collabora.com \
--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