From: Thomas Gleixner <tglx@kernel.org>
To: Zhan Xusheng <zhanxusheng1024@gmail.com>
Cc: linux-kernel@vger.kernel.org, Zhan Xusheng <zhanxusheng@xiaomi.com>
Subject: Re: [PATCH v2] timers/migration: Ensure proper resource cleanup on error in tmigr_init
Date: Thu, 05 Feb 2026 08:27:49 +0100 [thread overview]
Message-ID: <87ms1n1wga.ffs@tglx> (raw)
In-Reply-To: <20260205024537.100664-1-zhanxusheng@xiaomi.com>
On Thu, Feb 05 2026 at 10:45, Zhan Xusheng wrote:
> Free resources allocated by zalloc_cpumask_var and kcalloc on failure.
>
> Reviewed-by: Thomas Gleixner <tglx@kernel.org>
I surely did not give you a reviewed-by tag. The fact that I reviewed V1
does not mean you can slap such a tag on it.
next prev parent reply other threads:[~2026-02-05 7:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 8:50 [PATCH] timers/migration: Ensure proper resource cleanup on error in tmigr_init Zhan Xusheng
2026-02-04 15:08 ` Thomas Gleixner
2026-02-05 2:45 ` [PATCH v2] " Zhan Xusheng
2026-02-05 7:27 ` Thomas Gleixner [this message]
2026-02-05 7:35 ` [PATCH v3] " Zhan Xusheng
2026-02-11 15:40 ` Frederic Weisbecker
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=87ms1n1wga.ffs@tglx \
--to=tglx@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhanxusheng1024@gmail.com \
--cc=zhanxusheng@xiaomi.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