From: Mark Brown <broonie@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"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>,
"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, 4 Jan 2024 14:54:20 +0000 [thread overview]
Message-ID: <ded0cce0-3462-4c40-96e5-ca53b2028767@sirena.org.uk> (raw)
In-Reply-To: <3271d300-74c9-4ef3-b993-a8ddeda6076c@suswa.mountain>
[-- Attachment #1: Type: text/plain, Size: 401 bytes --]
On Tue, Jan 02, 2024 at 10:45:59AM +0300, Dan Carpenter wrote:
> Life hack: Don't put RFC in the subject. Especially if it's a v2 or
> higher. No one reads RFC patches.
RFC does tend to be useful in cases where you know that there are
substantial problems with the patches but are posting to solicit
feedback of some kind - otherwise people will tend to get annoyed when
they notice the problems.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-01-04 14:54 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 ` [RFC PATCH v3 0/3] Add test to verify probe of devices from discoverable busses Bjorn Helgaas
2023-12-29 12:33 ` 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 [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=ded0cce0-3462-4c40-96e5-ca53b2028767@sirena.org.uk \
--to=broonie@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.