Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: stable@vger.kernel.org, joshua.a.hay@intel.com,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: Patch "idpf: enable WB_ON_ITR" has been added to the 6.11-stable tree
Date: Tue, 1 Oct 2024 15:19:49 +0200	[thread overview]
Message-ID: <2024100142-flagpole-paragraph-8f1a@gregkh> (raw)
In-Reply-To: <8b2988ff-17d0-421e-8cf4-3eafef1276ca@intel.com>

On Tue, Oct 01, 2024 at 02:55:27PM +0200, Alexander Lobakin wrote:
> From: Sasha Levin <sashal@kernel.org>
> Date: Mon, 30 Sep 2024 19:08:34 -0400
> 
> > This is a note to let you know that I've just added the patch titled
> > 
> >     idpf: enable WB_ON_ITR
> > 
> > to the 6.11-stable tree which can be found at:
> >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > 
> > The filename of the patch is:
> >      idpf-enable-wb_on_itr.patch
> > and it can be found in the queue-6.11 subdirectory.
> > 
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> 
> Hi,
> 
> This commit should not be applied standalone and requires relatively big
> prerequisites from the series it was sent in, so I'd suggest just
> dropping it from stable.

Now dropped, thanks.

greg k-h

      reply	other threads:[~2024-10-01 13:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240930230835.2554923-1-sashal@kernel.org>
2024-10-01 12:55 ` Patch "idpf: enable WB_ON_ITR" has been added to the 6.11-stable tree Alexander Lobakin
2024-10-01 13:19   ` Greg KH [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=2024100142-flagpole-paragraph-8f1a@gregkh \
    --to=greg@kroah.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=joshua.a.hay@intel.com \
    --cc=kuba@kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=stable@vger.kernel.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