From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: Mark Pearson <mpearson-lenovo@squebb.ca>
Cc: Hans de Goede <hdegoede@redhat.com>,
"markgross@kernel.org" <markgross@kernel.org>,
Mark Pearson <markpearson@lenovo.com>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH v3 2/3] platform/x86: think-lmi: Add possible_values for ThinkStation
Date: Sun, 19 Mar 2023 00:01:29 +0000 [thread overview]
Message-ID: <faff3b63-5ccd-4b9d-af7a-68568b6ee934@t-8ch.de> (raw)
In-Reply-To: <7f8a0183-2da6-4ccb-9dd8-3602e67edd5a@app.fastmail.com>
On Sat, Mar 18, 2023 at 01:59:38PM -0400, Mark Pearson wrote:
> On Sat, Mar 18, 2023, at 12:35 PM, Thomas Weißschuh wrote:
> > Hi Mark,
> >
> > please also CC linux-kernel@vger.kernel.org and previous reviewers.
>
> My apologies on previous reviewers - that was a miss on my behalf
>
> I've never cc'd linux-kernel previously - is that a requirement? It's
> new to me if it is - what's the reason? (that mailing list seems
> unusable to me from my limited experience...)
The wording in Documentation/process/submitting-patches.rst is indeed
unclear about always Cc'ing linux-kernel.
My arguments for it are:
- People can look at the linux-kernel archives to see what's going on
all over the kernel. (I do that sometimes myself)
Also it makes it easier to search on lore.kernel.org on linux-specific
messages/patches. The /all/ archives also contains other projects.
- Some bots are processing proposed patches from mailing lists.
These are not subscribed to all subsystem lists.
- The b4 tool does it.
- Greg does it:
https://lore.kernel.org/lkml/20230313182918.1312597-5-gregkh@linuxfoundation.org/
Thomas
next prev parent reply other threads:[~2023-03-19 0:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 15:46 [PATCH v3 1/3] platform/x86: think-lmi: add missing type attribute Mark Pearson
2023-03-17 15:46 ` [PATCH v3 2/3] platform/x86: think-lmi: Add possible_values for ThinkStation Mark Pearson
2023-03-18 16:35 ` Thomas Weißschuh
2023-03-18 17:53 ` Mark Pearson
2023-03-18 23:52 ` Thomas Weißschuh
2023-03-19 0:08 ` Mark Pearson
2023-03-19 9:34 ` Hans de Goede
2023-03-18 17:59 ` Mark Pearson
2023-03-19 0:01 ` Thomas Weißschuh [this message]
2023-03-19 0:04 ` Mark Pearson
2023-03-17 15:46 ` [PATCH v3 3/3] platform/x86: think-lmi: use correct possible_values delimters Mark Pearson
2023-03-18 14:37 ` Barnabás Pőcze
2023-03-18 17:55 ` Mark Pearson
2023-03-18 16:39 ` Thomas Weißschuh
2023-03-18 18:06 ` Mark Pearson
2023-03-19 0:11 ` Thomas Weißschuh
2023-03-19 0:18 ` Mark Pearson
2023-03-20 0:52 ` [PATCH v3 1/3] platform/x86: think-lmi: add missing type attribute Limonciello, Mario
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=faff3b63-5ccd-4b9d-af7a-68568b6ee934@t-8ch.de \
--to=thomas@t-8ch.de \
--cc=hdegoede@redhat.com \
--cc=markgross@kernel.org \
--cc=markpearson@lenovo.com \
--cc=mpearson-lenovo@squebb.ca \
--cc=platform-driver-x86@vger.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;
as well as URLs for NNTP newsgroup(s).