public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: jianqi.ren.cn@windriver.com
Cc: cratiu@nvidia.com, dtatulea@nvidia.com, tariqt@nvidia.com,
	pabeni@redhat.com, patches@lists.linux.dev,
	stable@vger.kernel.org, saeedm@nvidia.com, leon@kernel.org,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	roid@nvidia.com, netdev@vger.kernel.org,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.1.y] net/mlx5e: Don't call cleanup on profile rollback failure
Date: Wed, 11 Dec 2024 10:18:46 +0100	[thread overview]
Message-ID: <2024121114-subsidize-tattered-dd8c@gregkh> (raw)
In-Reply-To: <20241211100953.2069964-1-jianqi.ren.cn@windriver.com>

On Wed, Dec 11, 2024 at 06:09:53PM +0800, jianqi.ren.cn@windriver.com wrote:
> From: Cosmin Ratiu <cratiu@nvidia.com>
> 
> [ Upstream commit 4dbc1d1a9f39c3711ad2a40addca04d07d9ab5d0 ]

Please note that we can not apply a commit to an older stable tree that
is NOT in newer ones as you would obviously have a regression when
moving to a newer kernel.

I am guessing that you are being tasked with backporting CVE fixes to
older stable kernels, which is great, but please work "down the release
list" by starting with the newest one, and then moving to the older
ones.  Otherwise we just can't take these and you are causing a lot of
extra review/checking time on our side here to verify you are doing it
all correctly :(

thanks,

greg k-h

  reply	other threads:[~2024-12-11  9:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 10:09 [PATCH 6.1.y] net/mlx5e: Don't call cleanup on profile rollback failure jianqi.ren.cn
2024-12-11  9:18 ` Greg KH [this message]
2024-12-11 16:33 ` Sasha Levin
  -- strict thread matches above, loose matches on Subject: below --
2024-12-26  7:11 jianqi.ren.cn
2024-12-26 16:44 ` Sasha Levin
2024-12-10  6:55 jianqi.ren.cn
2024-12-10 19:25 ` Sasha Levin

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=2024121114-subsidize-tattered-dd8c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cratiu@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=dtatulea@nvidia.com \
    --cc=edumazet@google.com \
    --cc=jianqi.ren.cn@windriver.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=patches@lists.linux.dev \
    --cc=roid@nvidia.com \
    --cc=saeedm@nvidia.com \
    --cc=stable@vger.kernel.org \
    --cc=tariqt@nvidia.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