kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sungwoo Kim <iam@sung-woo.kim>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Markus Elfring <Markus.Elfring@web.de>,
	linux-bluetooth@vger.kernel.org,
	 kernel-janitors@vger.kernel.org,
	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: [PATCH] Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_send_cmd
Date: Fri, 26 Apr 2024 05:48:11 -0400	[thread overview]
Message-ID: <CAJNyHpKEKoOKGsh8RSn+Tt=0mawG4Bz6LKwq3H2UFwuGuXH0vQ@mail.gmail.com> (raw)
In-Reply-To: <dd466a68-f3ae-4dc1-8389-6adc463735db@moroto.mountain>

On Fri, Apr 26, 2024 at 5:38 AM Dan Carpenter <dan.carpenter@linaro.org> wrote:
>
> Please just ignore Markus.  A lot of people have asked him to stop
> commenting on commit messages but he doesn't listen.  Here is a message
> from yesterday:
>
> https://lore.kernel.org/all/2024042547-shimmy-guileless-c7f2@gregkh/
>
> 1) It doesn't matter at all if there is anyone in the To: header.
> 2) You are allowed to ask questions.
> 3) Yes, the commit message will need to be changed but first fix the bug
>    and then we can worry about the commit message.
>
> regards,
> dan carpenter
>
>

Thank you for letting me know :)

  reply	other threads:[~2024-04-26  9:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240426072006.358802-1-iam@sung-woo.kim>
2024-04-26  8:25 ` [PATCH] Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_send_cmd Markus Elfring
2024-04-26  8:38   ` Sungwoo Kim
2024-04-26  9:38     ` Dan Carpenter
2024-04-26  9:48       ` Sungwoo Kim [this message]
2024-04-26 10:01       ` Markus Elfring

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='CAJNyHpKEKoOKGsh8RSn+Tt=0mawG4Bz6LKwq3H2UFwuGuXH0vQ@mail.gmail.com' \
    --to=iam@sung-woo.kim \
    --cc=Markus.Elfring@web.de \
    --cc=dan.carpenter@linaro.org \
    --cc=daveti@purdue.edu \
    --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;
as well as URLs for NNTP newsgroup(s).