From: Greg KH <gregkh@linuxfoundation.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: cassel@kernel.org, hare@suse.de, john.g.garry@oracle.com,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] ata: libata-core: Fix null pointer dereference on error" failed to apply to 6.9-stable tree
Date: Tue, 2 Jul 2024 11:11:22 +0200 [thread overview]
Message-ID: <2024070208-dazzling-charging-d5db@gregkh> (raw)
In-Reply-To: <64b91917-f2bc-48a2-9382-e4045c91dad9@kernel.org>
On Tue, Jul 02, 2024 at 06:50:05AM +0900, Damien Le Moal wrote:
> On 7/1/24 23:31, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 6.9-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-6.9.y
> > git checkout FETCH_HEAD
> > git cherry-pick -x 5d92c7c566dc76d96e0e19e481d926bbe6631c1e
> > # <resolve conflicts, build, test, etc.>
> > git commit -s
> > git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2024070105-falsify-surrender-babc@gregkh' --subject-prefix 'PATCH 6.9.y' HEAD^..
> >
> > Possible dependencies:
> >
> > 5d92c7c566dc ("ata: libata-core: Fix null pointer dereference on error")
>
> Greg,
>
> I am confused... This patch applies cleanly to linux-6.9.y. The procedure above
> also works just fine. And the "Possible dependencies" on itself does not make
> sense. Bot problem ?
Odd, this seems to already be in the tree, sorry for the noise.
greg k-h
next prev parent reply other threads:[~2024-07-02 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 14:31 FAILED: patch "[PATCH] ata: libata-core: Fix null pointer dereference on error" failed to apply to 6.9-stable tree gregkh
2024-07-01 21:50 ` Damien Le Moal
2024-07-02 9:11 ` Greg KH [this message]
2024-07-02 11:51 ` 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=2024070208-dazzling-charging-d5db@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=hare@suse.de \
--cc=john.g.garry@oracle.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