Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Felix Maurer <fmaurer@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Sasha Levin <sashal@kernel.org>,
	stable@vger.kernel.org,
	Steffen Lindner <steffen.lindner@de.abb.com>,
	Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH 6.18.y 1/2] hsr: Implement more robust duplicate discard for PRP
Date: Tue, 9 Jun 2026 13:39:27 +0200	[thread overview]
Message-ID: <aif7b2qPzEGJx-EV@thinkpad> (raw)
In-Reply-To: <aifbzVmhiThTVLj7@thinkpad>

On Tue, Jun 09, 2026 at 11:24:34AM +0200, Felix Maurer wrote:
> I don't really know the guidelines around the stable trees. Do we want
> such (heavily modfied) patches so that others can be applied?

I only now saw the patches Sasha posted for the older stable trees (like
[1] for 6.12.y). I think we should do the same thing for 6.18.y as well
and not backport the rather big 415e6367512b ("hsr: Implement more
robust duplicate discard for PRP").

Thanks,
   Felix

[1]: https://lore.kernel.org/stable/20260529233922.1913663-1-sashal@kernel.org/


      reply	other threads:[~2026-06-09 11:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28  7:53 FAILED: patch "[PATCH] net: hsr: defer node table free until after RCU readers" failed to apply to 6.18-stable tree gregkh
2026-05-29 23:24 ` [PATCH 6.18.y 1/2] hsr: Implement more robust duplicate discard for PRP Sasha Levin
2026-05-29 23:24   ` [PATCH 6.18.y 2/2] net: hsr: defer node table free until after RCU readers Sasha Levin
2026-06-01  7:52   ` [PATCH 6.18.y 1/2] hsr: Implement more robust duplicate discard for PRP Sebastian Andrzej Siewior
2026-06-09  9:24     ` Felix Maurer
2026-06-09 11:39       ` Felix Maurer [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=aif7b2qPzEGJx-EV@thinkpad \
    --to=fmaurer@redhat.com \
    --cc=bigeasy@linutronix.de \
    --cc=pabeni@redhat.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=steffen.lindner@de.abb.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