All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: sagi@lightbitslabs.com, hch@lst.de, roys@lightbitslabs.com,
	sashas@lightbitslabs.com
Cc: stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] nvmet-tcp: add NVMe over TCP target driver" failed to apply to 5.15-stable tree
Date: Sat, 7 Feb 2026 16:01:19 +0100	[thread overview]
Message-ID: <2026020759-desolate-cozily-df60@gregkh> (raw)
In-Reply-To: <2026020722-probable-democracy-26e2@gregkh>

On Sat, Feb 07, 2026 at 03:35:23PM +0100, gregkh@linuxfoundation.org wrote:
> 
> The patch below does not apply to the 5.15-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
> 
> To reproduce the conflict and resubmit, you may use the following commands:
> 
> git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-5.15.y
> git checkout FETCH_HEAD
> git cherry-pick -x 872d26a391da92ed8f0c0f5cb5fef428067b7f30
> # <resolve conflicts, build, test, etc.>
> git commit -s
> git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2026020722-probable-democracy-26e2@gregkh' --subject-prefix 'PATCH 5.15.y' HEAD^..
> 
> Possible dependencies:
> 
> 
> 
> thanks,
> 
> greg k-h
> 
> ------------------ original commit in Linus's tree ------------------
> 
> >From 872d26a391da92ed8f0c0f5cb5fef428067b7f30 Mon Sep 17 00:00:00 2001
> From: Sagi Grimberg <sagi@lightbitslabs.com>
> Date: Mon, 3 Dec 2018 17:52:15 -0800
> Subject: [PATCH] nvmet-tcp: add NVMe over TCP target driver

Crap, wrong commit, sorry!  I was cut/pasting from a fix that resolves
an issue in this commit, my fault.

greg k-h

      reply	other threads:[~2026-02-07 15:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-07 14:35 FAILED: patch "[PATCH] nvmet-tcp: add NVMe over TCP target driver" failed to apply to 5.15-stable tree gregkh
2026-02-07 15:01 ` 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=2026020759-desolate-cozily-df60@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=roys@lightbitslabs.com \
    --cc=sagi@lightbitslabs.com \
    --cc=sashas@lightbitslabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.