From: Markus Elfring <Markus.Elfring@web.de>
To: David Arcari <darcari@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: Re: [v2] intel_th: core: fix null pointer dereference in intel_th_irq
Date: Thu, 20 Nov 2025 14:07:24 +0100 [thread overview]
Message-ID: <0d5bad33-49ed-4531-b399-e548d3dfce66@web.de> (raw)
In-Reply-To: <e314be75-c171-40dd-8298-dce40f65d93b@redhat.com>
…>>> the same array. This can be fixed by disabling interrupts
>>> during the call to intel_th_output_enable().
>>
>> 1. Would another imperative wording become helpful for an improved change description?
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.18-rc6#n94
>
> I feel like the description explains the problem well.
Perhaps?
> However, do you have alternate wording you would like to suggest?
Under which circumstances would you get into the mood to convert the wording approach
“can be fixed by” into an imperative one?
Regards,
Markus
next prev parent reply other threads:[~2025-11-20 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251118212106.541728-1-darcari@redhat.com>
2025-11-19 12:55 ` [PATCH v2] intel_th: core: fix null pointer dereference in intel_th_irq Markus Elfring
2025-11-20 12:32 ` David Arcari
2025-11-20 13:07 ` Markus Elfring [this message]
2025-11-20 13:22 ` [v2] " David Arcari
2026-01-16 12:49 ` Alexander Shishkin
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=0d5bad33-49ed-4531-b399-e548d3dfce66@web.de \
--to=markus.elfring@web.de \
--cc=alexander.shishkin@linux.intel.com \
--cc=darcari@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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