public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Hans de Goede" <hdegoede@redhat.com>,
	"Harshit Mogalapalli" <harshit.m.mogalapalli@oracle.com>,
	platform-driver-x86@vger.kernel.org,
	kernel-janitors@vger.kernel.org,
	"Srinivas Pandruvada" <srinivas.pandruvada@linux.intel.com>,
	"Zhang Rui" <rui.zhang@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Dan Carpenter <error27@gmail.com>
Subject: Re: [v2] platform/x86: ISST: fix use-after-free in tpmi_sst_dev_remove()
Date: Tue, 21 May 2024 13:09:44 +0200	[thread overview]
Message-ID: <9c179632-a7d7-4dcd-ac2f-89ef77d362b2@web.de> (raw)
In-Reply-To: <c158e0f4-fcbd-13a6-ee98-adc26160c3c2@linux.intel.com>

>>> We'll not waste our time in wordsmithing commit messages to perfection,
>>
>> I hope that you would also like to avoid typos in change descriptions.
>
> Now you start derailing this with off-topic references to hypothetical "typos".

Which alternative term would you prefer for the word combination “the kfree() post”
(for example) instead?

Regards,
Markus

  reply	other threads:[~2024-05-21 11:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17 14:49 [PATCH v2] platform/x86: ISST: fix use-after-free in tpmi_sst_dev_remove() Harshit Mogalapalli
2024-05-17 15:15 ` srinivas pandruvada
2024-05-18 17:30 ` Markus Elfring
2024-05-20  9:38   ` Ilpo Järvinen
2024-05-20 10:56     ` [v2] " Markus Elfring
2024-05-20 17:49       ` Hans de Goede
2024-05-21  5:15         ` Markus Elfring
2024-05-21 10:06           ` Ilpo Järvinen
2024-05-21 10:42             ` Markus Elfring
2024-05-21 10:56               ` Ilpo Järvinen
2024-05-21 11:09                 ` Markus Elfring [this message]
2024-05-27  9:29 ` [PATCH v2] " Hans de Goede

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=9c179632-a7d7-4dcd-ac2f-89ef77d362b2@web.de \
    --to=markus.elfring@web.de \
    --cc=dan.carpenter@linaro.org \
    --cc=error27@gmail.com \
    --cc=harshit.m.mogalapalli@oracle.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=srinivas.pandruvada@linux.intel.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