From: "Mehmet Koseoglu" <mehmet.mkoseoglu@gmail.com>
To: "Viresh Kumar" <viresh.kumar@linaro.org>,
"spidermana" <xuyiwen14@gmail.com>
Cc: <miguel.ojeda.sandonis@gmail.com>, <a.hindborg@kernel.org>,
<acourbot@nvidia.com>, <aliceryhl@google.com>,
<bjorn3_gh@protonmail.com>, <boqun@kernel.org>, <dakr@kernel.org>,
<daniel.almeida@collabora.com>, <gary@garyguo.net>,
<linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>,
<lossin@kernel.org>, <mehmet.mkoseoglu@gmail.com>,
<ojeda@kernel.org>, <rafael@kernel.org>,
<rust-for-linux@vger.kernel.org>, <tamird@kernel.org>,
<tmgross@umich.edu>, <work@onurozkan.dev>
Subject: Re: [PATCH v3] rust: cpufreq: reject NULL from cpufreq_cpu_get()
Date: Thu, 01 Oct 2026 12:49:04 +0300 [thread overview]
Message-ID: <DLTEONSHWRPQ.1U2Y6GDBRURFX@gmail.com> (raw)
In-Reply-To: <ar38vCqqekY7T3SZ@vireshk-B250M-D3H>
On Thu Oct 1, 2026 at 9:25 AM +03, Viresh Kumar wrote:
> On 29-09-26, 11:55, spidermana wrote:
>> On Mon, 28 Sep 2026 19:17:08 +0200, Miguel Ojeda wrote:
>> > The From: doesn't seem to match the email of the tag, is that intended?
>>
>> Oops, no, thanks for noticing! Please disregard the tag in my
>> previous reply. the correct one is:
>>
>> Reviewed-by: spidermana <xuyiwen14@gmail.com>
>
> Please resend the patch with all the fixes / tags / improvements. Thanks.
Hi Viresh,
I see that v3 was already applied as 0ba1ee052b3f. Would you prefer
a follow-up patch updating the SAFETY comment, or a v4 of the original
patch with the comment update and collected review tags?
Thanks,
Mehmet
next prev parent reply other threads:[~2026-10-01 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 16:10 [PATCH v3] rust: cpufreq: reject NULL from cpufreq_cpu_get() Mehmet Koseoglu
2026-08-29 19:52 ` Onur Özkan
2026-09-28 16:22 ` spidermana
2026-09-28 17:17 ` Miguel Ojeda
2026-09-29 9:55 ` spidermana
2026-10-01 6:25 ` Viresh Kumar
2026-10-01 9:49 ` Mehmet Koseoglu [this message]
2026-10-01 9:58 ` Viresh Kumar
2026-10-01 10:19 ` [PATCH v4] " Mehmet Koseoglu
2026-10-05 3:56 ` 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=DLTEONSHWRPQ.1U2Y6GDBRURFX@gmail.com \
--to=mehmet.mkoseoglu@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=viresh.kumar@linaro.org \
--cc=work@onurozkan.dev \
--cc=xuyiwen14@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.