From: "Ariel Otilibili-Anieli" <Ariel.Otilibili-Anieli@eurecom.fr>
To: "Greg KH" <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, "Jan Beulich" <jbeulich@suse.com>,
stable@vger.kernel.org,
"Andrew Morton" <akpm@linux-foundation.org>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 1/1] lib: Remove dead code
Date: Fri, 20 Dec 2024 09:44:31 +0100 [thread overview]
Message-ID: <2f7a82-67652e80-9181-6eae3780@215109797> (raw)
In-Reply-To: <2024122042-guidable-overhand-b8a9@gregkh>
On Friday, December 20, 2024 08:09 CET, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Thu, Dec 19, 2024 at 11:45:01PM +0100, Ariel Otilibili wrote:
> > This is a follow up from a discussion in Xen:
> >
> > The if-statement tests `res` is non-zero; meaning the case zero is never reached.
> >
> > Link: https://lore.kernel.org/all/7587b503-b2ca-4476-8dc9-e9683d4ca5f0@suse.com/
> > Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> > Suggested-by: Jan Beulich <jbeulich@suse.com>
> > Signed-off-by: Ariel Otilibili <ariel.otilibili-anieli@eurecom.fr>
> > --
> > Cc: stable@vger.kernel.org
>
> Why is "removing dead code" a stable kernel thing?
Hello Greg,
It is what I understood from the process:
"Attaching a Fixes: tag does not subvert the stable kernel rules process nor the requirement to Cc: stable@vger.kernel.org on all stable patch candidates." [1]
Does my understanding make sense?
Regards,
Ariel
[1] https://docs.kernel.org/process/submitting-patches.html
>
> confused,
>
> greg k-h
next prev parent reply other threads:[~2024-12-20 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 9:21 [PATCH 0/1] lib: Remove dead code Ariel Otilibili
2024-12-19 9:21 ` [PATCH 1/1] " Ariel Otilibili
2024-12-19 22:45 ` [PATCH v2 0/1] " Ariel Otilibili
2024-12-19 22:45 ` [PATCH v2 1/1] " Ariel Otilibili
2024-12-20 7:09 ` Greg KH
2024-12-20 8:44 ` Ariel Otilibili-Anieli [this message]
2024-12-20 8:53 ` Greg KH
2024-12-20 9:01 ` Ariel Otilibili-Anieli
2024-12-20 9:36 ` Ariel Otilibili-Anieli
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=2f7a82-67652e80-9181-6eae3780@215109797 \
--to=ariel.otilibili-anieli@eurecom.fr \
--cc=akpm@linux-foundation.org \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=gregkh@linuxfoundation.org \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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.