From: w15303746062 <w15303746062@163.com>
To: "Greg KH" <greg@kroah.com>
Cc: simona@ffwll.ch, deller@gmx.de, tzimmermann@suse.de,
ville.syrjala@linux.intel.com, sam@ravnborg.org, kees@kernel.org,
yanquanmin1@huawei.com, syoshida@redhat.com,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
"Mingyu Wang" <25181214217@stu.xidian.edu.cn>,
stable@vger.kernel.org
Subject: Re:Re: Re:[PATCH 7.0] fbdev: fbcon: fix memory leak in error path of fbcon_do_set_font()
Date: Mon, 27 Jul 2026 15:28:14 +0800 (CST) [thread overview]
Message-ID: <39aeae7d.5bf9.19fa2796cc0.Coremail.w15303746062@163.com> (raw)
In-Reply-To: <2026072719-kissable-antonym-d31e@gregkh>
>
>Why not just take the same upstream commits for older kernels as well?
>
>Whenever you do "one off" patches like this, it makes backporting future
>changes/fixes almost impossible, and we almost always get it wrong. So
>backporting the same changes is almost always the best idea.
>
>Also note that the 7.0.y kernel is long end-of-life.
>
From: Mingyu Wang <25181214217@stu.xidian.edu.cn>
Hi Greg,
Understood. Thanks for the explanation and for letting me know.
I will drop this patch since 7.0 is EOL, and I will make sure
to stick to upstream commits for future backports.
Best regards,
Mingyu
prev parent reply other threads:[~2026-07-27 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 8:27 [PATCH 7.0] fbdev: fbcon: fix memory leak in error path of fbcon_do_set_font() w15303746062
2026-06-05 3:33 ` w15303746062
2026-07-27 7:00 ` w15303746062
2026-07-27 7:11 ` Greg KH
2026-07-27 7:28 ` w15303746062 [this message]
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=39aeae7d.5bf9.19fa2796cc0.Coremail.w15303746062@163.com \
--to=w15303746062@163.com \
--cc=25181214217@stu.xidian.edu.cn \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=greg@kroah.com \
--cc=kees@kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=syoshida@redhat.com \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.intel.com \
--cc=yanquanmin1@huawei.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