From: Sven Eckelmann <sven@narfation.org>
To: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y] batman-adv: Drop unmanaged ELP metric worker
Date: Fri, 21 Feb 2025 19:32:44 +0100 [thread overview]
Message-ID: <6025110.MhkbZ0Pkbq@ripper> (raw)
In-Reply-To: <4657309.LvFx2qVVIh@sven-l14>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
On Wednesday, 19 February 2025 23:38:07 CET Sven Eckelmann wrote:
> On Wednesday, 19 February 2025 23:09:53 GMT+1 Sasha Levin wrote:
> > [ Sasha's backport helper bot ]
> >
> > Hi,
> >
> > Summary of potential issues:
> > ❌ Build failures detected
> >
> > The upstream commit SHA1 provided is correct: 8c8ecc98f5c65947b0070a24bac11e12e47cc65d
> >
> >
> > Status in newer kernel trees:
> > 6.13.y | Present (different SHA1: 7350aafa40a7)
> > 6.12.y | Present (different SHA1: c09f874f226b)
> > 6.6.y | Present (different SHA1: c8db60b2a7fd)
> > 6.1.y | Present (different SHA1: 831dda93b13c)
> > 5.4.y | Not found
> >
> > Note: The patch differs from the upstream commit:
> > ---
> > Failed to apply patch cleanly.
>
> Was this patch applied with or without the already queued up patches from
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.15 ?
> They are required for this patch to apply correctly.
Ok, now it will definitely fail because you've added your own backport..
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-02-21 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 11:24 FAILED: patch "[PATCH] batman-adv: Drop unmanaged ELP metric worker" failed to apply to 5.15-stable tree gregkh
2025-02-19 18:49 ` [PATCH 5.15.y] batman-adv: Drop unmanaged ELP metric worker Sven Eckelmann
2025-02-19 22:09 ` Sasha Levin
2025-02-19 22:38 ` Sven Eckelmann
2025-02-21 18:32 ` Sven Eckelmann [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=6025110.MhkbZ0Pkbq@ripper \
--to=sven@narfation.org \
--cc=sashal@kernel.org \
--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