From: "Luck, Tony" <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Wentao Liang <vulab@iscas.ac.cn>, <linux-edac@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <qiuxu.zhuo@intel.com>
Subject: Re: [PATCH] EDAC/i10nm: Fix mdev reference leak in i10nm_get_ddr_munits()
Date: Tue, 22 Sep 2026 07:59:56 -0700 [thread overview]
Message-ID: <arKX7O905e7yv3Ra@agluck-desk3> (raw)
In-Reply-To: <20260922045057.GGarIJMRAjfqj6mkhE@fat_crate.local>
On Mon, Sep 21, 2026 at 09:50:57PM -0700, Borislav Petkov wrote:
> Dropping stable@ from CC as it shouldn't be on CC.
>
> On Mon, Sep 21, 2026 at 09:04:30AM -0700, Luck, Tony wrote:
> > I though urgent was for:
> > 1) Fixing something that broke in the current merge window
> > 2) Fixing something that's really important (security, corruption)
> >
> > This is just an old issue that's been around for ages.
>
> If this patch has CC:stable and a Fixes: tag, then it'll get backported to
> stable. So does it matter when it gets sent to Linus?
>
> IOW, those two things do turn it into an urgent patch.
The "Fixes:" tag is a matter of fact. The "Cc: stable" is just an
opinion.
An extreme example would be a patch that fixes a spelling error in a
comment posted on a Friday before Linus is expected to tag a "final"
release in a cycle. A "Cc: stable" on that patch shouldn't trigger
sending to Linus via an urgent pull.
But if you want to add this patch to edac-urgent, then go ahead.
-Tony
next prev parent reply other threads:[~2026-09-22 15:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 9:12 [PATCH] EDAC/i10nm: Fix mdev reference leak in i10nm_get_ddr_munits() Wentao Liang
2026-09-16 14:31 ` Leo Zhuo
2026-09-17 23:35 ` Luck, Tony
2026-09-19 5:34 ` Borislav Petkov
2026-09-21 16:04 ` Luck, Tony
2026-09-22 4:50 ` Borislav Petkov
2026-09-22 14:59 ` Luck, Tony [this message]
2026-09-22 18:53 ` Borislav Petkov
2026-09-22 19:25 ` Luck, Tony
2026-09-23 0:20 ` Borislav Petkov
2026-09-23 0:30 ` Luck, Tony
2026-09-23 0:33 ` Borislav Petkov
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=arKX7O905e7yv3Ra@agluck-desk3 \
--to=tony.luck@intel.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiuxu.zhuo@intel.com \
--cc=vulab@iscas.ac.cn \
/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.