mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	"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 10:36:53 +0100	[thread overview]
Message-ID: <2f7a89-67653a80-c09b-70827e80@197000382> (raw)
In-Reply-To: <2f7a83-67653280-a2f5-5cf12280@54008765>

On Friday, December 20, 2024 10:01 CET, "Ariel Otilibili-Anieli" <Ariel.Otilibili-Anieli@eurecom.fr> wrote:

> On Friday, December 20, 2024 09:53 CET, Greg KH <gregkh@linuxfoundation.org> wrote:
> 
> > On Fri, Dec 20, 2024 at 09:44:31AM +0100, Ariel Otilibili-Anieli wrote:
> > > 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?
> > 
> > I'm confused, what are you expecting to happen here?  Why is this even
> > marked as a "fix"?

My understanding was that, for one-liners, the reference commit should be included; and CC stable.
> > 
> > > [1] https://docs.kernel.org/process/submitting-patches.html
> > 
> > Please read:
> >     https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> 
> I am, Greg; thanks for the heads up.

Now I got the procedure; thank you.
> > 
> > for the stable kernel rules.
> > 
> > Again, you have a "cc: stable@..." in your patch, why?
> 
> Removed stable from the thread.

Hello again, Greg;

I should have said it upfront, for us to understand one another.
I have just checked, this thread is about v2 of the patch (with stable in CC); and v1 (without) was already accepted by  Andrew Morton [1].

If anything else I need to do, let me know.

Have a good day,
Ariel

[1] https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/lib-remove-dead-code.patch
> > 
> > thanks,
> > 
> > greg k-h


      reply	other threads:[~2024-12-20  9:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19  9:21 [PATCH 0/1] " 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
2024-12-20  8:53         ` Greg KH
2024-12-20  9:01           ` Ariel Otilibili-Anieli
2024-12-20  9:36             ` Ariel Otilibili-Anieli [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=2f7a89-67653a80-c09b-70827e80@197000382 \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®