Linux Power Management development
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Cristian Marussi <cristian.marussi@arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Henry Martin <bsdhenrymartin@gmail.com>,
	arm-scmi@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [v2 0/2] cpufreq: scmi/scpi: Fix NULL pointer dereference in get_rate()
Date: Wed, 9 Apr 2025 14:25:52 +0200	[thread overview]
Message-ID: <3f5662dc-7547-4585-a396-4546fa98d34f@web.de> (raw)
In-Reply-To: <Z_Zhp38o9KiicPVw@pluto>

>>>> Can any other summary phrase variants become more desirable accordingly?
>
> I agree with Sudeep, the above sentence is completely incomprehensible
> to me

Can any suggestions gain acceptance also for better summary phrases?



>>> This is meaningless, sorry can't parse. Ignoring it as others in the
>>> community are doing already.
>> Do you care if the term “null pointer dereference” would be used in consistent ways?
>
> ...this is more comprehensible,

Thanks for another bit of constructive information.


>                                 but again I cannot grasp what's yor advice
> specifically on this commit message.
May the usage of abbreviations be reconsidered once more also for such messages
(in presented update steps)?

Regards,
Markus

  reply	other threads:[~2025-04-09 12:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 15:03 [PATCH v2 0/2] cpufreq: scmi/scpi: Fix NULL pointer dereference in get_rate() Henry Martin
2025-04-08 15:03 ` [PATCH v2 1/2] cpufreq: scmi: Fix null-ptr-deref in scmi_cpufreq_get_rate() Henry Martin
2025-04-08 15:03 ` [PATCH v2 2/2] cpufreq: scpi: Fix null-ptr-deref in scpi_cpufreq_get_rate() Henry Martin
2025-04-08 19:23 ` [PATCH v2 0/2] cpufreq: scmi/scpi: Fix NULL pointer dereference in get_rate() Markus Elfring
2025-04-09 11:20   ` Sudeep Holla
2025-04-09 11:48     ` Markus Elfring
2025-04-09 12:01       ` Cristian Marussi
2025-04-09 12:25         ` Markus Elfring [this message]
2025-04-09 13:21           ` [v2 " Sudeep Holla
2025-04-09 14:24             ` Markus Elfring
2025-04-09 11:30 ` [PATCH v2 " Sudeep Holla
2025-04-09 12:40   ` henry martin
2025-04-10  4:40 ` Viresh Kumar

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=3f5662dc-7547-4585-a396-4546fa98d34f@web.de \
    --to=markus.elfring@web.de \
    --cc=arm-scmi@vger.kernel.org \
    --cc=bsdhenrymartin@gmail.com \
    --cc=cristian.marussi@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=viresh.kumar@linaro.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