From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux@roeck-us.net, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] clocksource: Make negative motion detection more robust" failed to apply to 6.12-stable tree
Date: Thu, 12 Dec 2024 15:35:14 +0100 [thread overview]
Message-ID: <2024121205-override-postbox-5ed6@gregkh> (raw)
In-Reply-To: <87frmt9dl3.ffs@tglx>
On Thu, Dec 12, 2024 at 03:32:24PM +0100, Thomas Gleixner wrote:
> On Thu, Dec 12 2024 at 15:18, Greg KH wrote:
> > On Thu, Dec 12, 2024 at 03:17:03PM +0100, Greg KH wrote:
> >> > But I don't think these two commits are necessarily stable material,
> >> > though I don't have a strong opinion on it. If c163e40af9b2 is
> >> > backported, then it has it's own large dependency chain on pre 6.10
> >> > kernels...
> >>
> >> It's in the queues for some reason, let me figure out why...
> >
> > Ah, it was an AUTOSEL thing, I'll go drop it from all queues except
> > 6.12.y for now, thanks.
> >
> > But, for 6.12.y, we want this fixup too, right?
>
> If you have c163e40af9b2 pulled back into 6.12.y, then yes. I don't know
> why this actually rejects. I just did
>
> git-cherry-pick c163e40af9b2
> git-cherry-pick 51f109e92935
>
> on top of v6.12.4 and that just worked fine.
The build breaks :(
next prev parent reply other threads:[~2024-12-12 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 13:03 FAILED: patch "[PATCH] clocksource: Make negative motion detection more robust" failed to apply to 6.12-stable tree gregkh
2024-12-12 13:58 ` Thomas Gleixner
2024-12-12 14:17 ` Greg KH
2024-12-12 14:18 ` Greg KH
2024-12-12 14:32 ` Thomas Gleixner
2024-12-12 14:35 ` Greg KH [this message]
2024-12-12 14:37 ` Greg KH
2024-12-12 15:02 ` Thomas Gleixner
2024-12-12 17:57 ` Sasha Levin
2024-12-13 11:33 ` Greg KH
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=2024121205-override-postbox-5ed6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.net \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.