mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Breno Leitao <leitao@debian.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>,
	Nicolas Dichtel <nicolas.dichtel@6wind.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: Remove redundant variable declaration in __dev_change_flags()
Date: Fri, 14 Feb 2025 16:02:10 +0100	[thread overview]
Message-ID: <943abc29-d5af-4064-8853-5f3c365bf6d6@lunn.ch> (raw)
In-Reply-To: <20250214-civet-of-regular-refinement-23b247@leitao>

> But I agree with you, if you needed to look at it, it means the message
> is NOT good enough. I will update it.

Thanks.

> 
> > > Fixes: 991fb3f74c142e ("dev: always advertise rx_flags changes via netlink")
> > 
> > I suppose there is also a danger here this code has at some point in
> > the past has been refactored, such that the outer old_flags was used
> > at some point? Backporting this patch could then break something?  Did
> > you check for this? Again, a comment in the commit message that you
> > have checked this is safe to backport would be nice.
> 
> I haven't look at this, and I don't think this should be backported,
> thus, that is why I sent to net-next and didn't cc: stable.
> 
> That said, I don't think this should be backported, since it is not
> a big deal. Shouldn't I add the Fixes: in such case?

The danger of adding a Fixes: is that the ML bot will see the Fixes:
tag and might select it for backporting, even if we did not explicitly
queue it up for back porting. So i suggest dropping the tag.

    Andrew

  reply	other threads:[~2025-02-14 15:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14 12:47 Breno Leitao
2025-02-14 13:27 ` Mateusz Polchlopek
2025-02-14 13:33 ` Andrew Lunn
2025-02-14 14:21   ` Breno Leitao
2025-02-14 15:02     ` Andrew Lunn [this message]
2025-02-14 16:09       ` Breno Leitao

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=943abc29-d5af-4064-8853-5f3c365bf6d6@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=pabeni@redhat.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

all inboxes | Powered by JetHome®