From: Markus Elfring <Markus.Elfring@web.de>
To: Dan Carpenter <dan.carpenter@linaro.org>,
Sungwoo Kim <iam@sung-woo.kim>,
linux-bluetooth@vger.kernel.org, kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
"Dave (Jing) Tian" <daveti@purdue.edu>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_send_cmd
Date: Fri, 26 Apr 2024 12:01:20 +0200 [thread overview]
Message-ID: <9d186852-9ac0-4cbf-b9df-54d433b3483c@web.de> (raw)
In-Reply-To: <dd466a68-f3ae-4dc1-8389-6adc463735db@moroto.mountain>
> 1) It doesn't matter at all if there is anyone in the To: header.
I suggest to reconsider this view according to proper selection of message recipients.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9-rc5#n231
> 2) You are allowed to ask questions.
Yes, of course.
But we are looking more for “answers” in consistent and improved change descriptions,
aren't we?
The placement of related wordings can be adjusted another bit.
> 3) Yes, the commit message will need to be changed but first fix the bug
> and then we can worry about the commit message.
Will such a suggestion trigger further clarifications for the desired patching process?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9-rc5#n77
I hope that recurring communication difficulties will result in helpful ideas.
Regards,
Markus
next prev parent reply other threads:[~2024-04-26 10:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 7:20 [PATCH] " Sungwoo Kim
2024-04-26 7:31 ` Sungwoo Kim
2024-04-26 7:55 ` Paul Menzel
2024-04-26 8:25 ` Markus Elfring
2024-04-26 8:38 ` Sungwoo Kim
2024-04-26 9:38 ` Dan Carpenter
2024-04-26 9:48 ` Sungwoo Kim
2024-04-26 10:01 ` Markus Elfring [this message]
2024-04-26 9:16 ` Dan Carpenter
2024-04-26 9:35 ` Sungwoo Kim
2024-04-26 10:24 ` Dan Carpenter
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=9d186852-9ac0-4cbf-b9df-54d433b3483c@web.de \
--to=markus.elfring@web.de \
--cc=dan.carpenter@linaro.org \
--cc=daveti@purdue.edu \
--cc=iam@sung-woo.kim \
--cc=johan.hedberg@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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
all inboxes | Powered by JetHome®