From: Markus Elfring <Markus.Elfring@web.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Erick Archer <erick.archer@outlook.com>,
Henrik Rydberg <rydberg@bitmath.org>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>
Subject: Re: [PATCH] Input: bcm5974 - use guard notation when acquiring mutex
Date: Sun, 25 Aug 2024 22:02:28 +0200 [thread overview]
Message-ID: <7f1e75a2-0d34-40af-aed2-a53b5e10f459@web.de> (raw)
In-Reply-To: <ZsrBVO2w9WwX73iU@google.com>
> This makes the code …
Is there a need to improve such a change description with imperative wordings?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.11-rc5#n94
Regards,
Markus
prev parent reply other threads:[~2024-08-25 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 5:29 [PATCH] Input: bcm5974 - use guard notation when acquiring mutex Dmitry Torokhov
2024-08-25 9:09 ` rydberg
2024-08-25 20:02 ` Markus Elfring [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=7f1e75a2-0d34-40af-aed2-a53b5e10f459@web.de \
--to=markus.elfring@web.de \
--cc=dmitry.torokhov@gmail.com \
--cc=erick.archer@outlook.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@bitmath.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).