From: Petr Mladek <pmladek@suse.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Bradley Morgan <include@grrlz.net>,
Feng Tang <feng.tang@linux.alibaba.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <chleroy@kernel.org>,
Mukesh Kumar Chaurasiya <mchauras@linux.ibm.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jinchao Wang <wangjinchao600@gmail.com>,
Kees Cook <kees@kernel.org>, Rio <rioo.tsukatsukii@gmail.com>,
Joel Granados <joel.granados@kernel.org>,
Pnina Feder <pnina.feder@mobileye.com>,
Petr Pavlu <petr.pavlu@suse.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Douglas Anderson <dianders@chromium.org>,
Mayank Rungta <mrungta@google.com>, Tejun Heo <tj@kernel.org>,
Zhenguo Yao <yaozhenguo1@gmail.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Michal Hocko <mhocko@suse.cz>,
Miroslav Benes <mbenes@suse.cz>, Jiri Kosina <jkosina@suse.cz>
Subject: Fixed tag magic: was: Re: [PATCH v2 1/4] sys_info: add helper for callers that handle all_bt
Date: Thu, 25 Jun 2026 17:30:15 +0200 [thread overview]
Message-ID: <aj1Jh57McGH94gGY@pathway.suse.cz> (raw)
In-Reply-To: <20260624133419.a2d566f50c44ee2d4e0fb395@linux-foundation.org>
On Wed 2026-06-24 13:34:19, Andrew Morton wrote:
> On Tue, 23 Jun 2026 15:34:58 +0000 Bradley Morgan <include@grrlz.net> wrote:
>
> > Some callers handle SYS_INFO_ALL_BT themselves before calling sys_info().
> > Add a helper that strips that bit without turning an all_bt only mask into
> > a kernel_sys_info fallback.
>
> I assume this patch wants a Fixes: and a cc:stable also.
>
> It would be nice to have the conventional [0/N] cover letter to tell
> readers what this is all about.
>
> The patches all have different Fixes: targets. This risks inviting the
> -stable maintainers to merge only some of the patches into some
> kernels, resulting in an untested combination and which might break
> things.
I do not agree here. The Fixes tag should should point to a commit
which introduced the regression into the given code. And finding
some magic common point beause there is some magic undocumented
process for maintaining stable kernels sounds like a way to hell
to me.
Best Regards,
Petr
next prev parent reply other threads:[~2026-06-25 15:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 15:34 [PATCH v2 1/4] sys_info: add helper for callers that handle all_bt Bradley Morgan
2026-06-23 15:34 ` [PATCH v2 2/4] watchdog: avoid sys_info fallback for all_bt Bradley Morgan
2026-06-23 15:35 ` [PATCH v2 3/4] powerpc/watchdog: " Bradley Morgan
2026-06-23 15:35 ` [PATCH v2 4/4] panic: avoid duplicate all CPU backtraces from sys_info Bradley Morgan
2026-06-24 2:50 ` Feng Tang
2026-06-24 16:12 ` Bradley Morgan
2026-06-25 3:33 ` Feng Tang
2026-06-23 20:11 ` [PATCH v2 1/4] sys_info: add helper for callers that handle all_bt Andy Shevchenko
2026-06-23 20:14 ` Andy Shevchenko
2026-06-23 20:16 ` Bradley Morgan
2026-06-24 20:34 ` Andrew Morton
2026-06-24 20:44 ` Bradley Morgan
2026-06-25 6:25 ` Andy Shevchenko
2026-06-25 15:30 ` Petr Mladek [this message]
2026-06-25 15:31 ` Fixed tag magic: was: " Bradley Morgan
2026-06-25 15:42 ` Petr Mladek
2026-06-25 15:46 ` Bradley Morgan
2026-06-25 15:48 ` Bradley Morgan
2026-06-25 18:38 ` Andrew Morton
2026-06-25 21:00 ` Bradley Morgan
2026-06-25 14:03 ` Petr Mladek
2026-06-25 14:43 ` Bradley Morgan
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=aj1Jh57McGH94gGY@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=chleroy@kernel.org \
--cc=dianders@chromium.org \
--cc=feng.tang@linux.alibaba.com \
--cc=include@grrlz.net \
--cc=jkosina@suse.cz \
--cc=joel.granados@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mbenes@suse.cz \
--cc=mchauras@linux.ibm.com \
--cc=mhocko@suse.cz \
--cc=mpe@ellerman.id.au \
--cc=mrungta@google.com \
--cc=npiggin@gmail.com \
--cc=petr.pavlu@suse.com \
--cc=pnina.feder@mobileye.com \
--cc=rioo.tsukatsukii@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
--cc=wangjinchao600@gmail.com \
--cc=yaozhenguo1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox