From: Greg KH <greg@kroah.com>
To: "Wang, Wade" <wade.wang@hp.com>
Cc: "jikos@kernel.org" <jikos@kernel.org>,
"bentiss@kernel.org" <bentiss@kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] HID: plantronics: Additional PID for double volume key presses quirk
Date: Fri, 13 Sep 2024 10:23:54 +0200 [thread overview]
Message-ID: <2024091345-sliceable-magnetize-190a@gregkh> (raw)
In-Reply-To: <EA2PR84MB37800B3DCB1F28FAAF266FC18B652@EA2PR84MB3780.NAMPRD84.PROD.OUTLOOK.COM>
Please do not top-post.
On Fri, Sep 13, 2024 at 07:16:13AM +0000, Wang, Wade wrote:
> Hi Greg,
>
> Just add "Cc: stable@vger.kernel.org" in 2nd patch submission, because kernel test robot required. Any other thing I need to do for your question now? Thanks
That's a great start, but you need to document the difference when you
do this, as the documentation says to do so, below the --- line.
Otherwise maintainers have no idea what changed, and what version of a
patch to take.
Think about what you would want to see if you got 1000 emails a day to
do something with?
thanks,
greg k-h
next prev parent reply other threads:[~2024-09-13 8:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 6:07 [PATCH] HID: plantronics: Additional PID for double volume key presses quirk Wade Wang
2024-09-13 6:28 ` Greg KH
2024-09-13 7:16 ` Wang, Wade
2024-09-13 8:23 ` Greg KH [this message]
2024-09-13 14:01 ` Benjamin Tissoires
2024-09-16 9:06 ` Wang, Wade
-- strict thread matches above, loose matches on Subject: below --
2024-09-13 5:58 Wade Wang
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=2024091345-sliceable-magnetize-190a@gregkh \
--to=greg@kroah.com \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=wade.wang@hp.com \
/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).