From: David Woodhouse <dwmw2@infradead.org>
To: Mushahid Hussain <hmushi@amazon.co.uk>, tip-bot2@linutronix.de
Cc: efault@gmx.de, linux-kernel@vger.kernel.org,
linux-tip-commits@vger.kernel.org, peterz@infradead.org,
stable@vger.kernel.org, x86@kernel.org,
nh-open-source@amazon.com, sieberf@amazon.com
Subject: Re: [PATCH 6.12 000/122] 6.12.11-rc1 review
Date: Fri, 23 May 2025 17:46:41 +0100 [thread overview]
Message-ID: <edf9a5e62d8a92956ebf6c167df7d0f77e7e11cf.camel@infradead.org> (raw)
In-Reply-To: <20250523160128.8846-1-hmushi@amazon.co.uk>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
On Fri, 2025-05-23 at 16:01 +0000, Mushahid Hussain wrote:
> > The following commit has been merged into the sched/urgent branch of tip:
> >
> > Commit-ID: 55294004b122c997591d9de8446f5a4c60402805
> > Gitweb: https://git.kernel.org/tip/55294004b122c997591d9de8446f5a4c60402805
> > Author: Peter Zijlstra <peterz@infradead.org>
> > AuthorDate: Tue, 28 Jan 2025 15:39:49 +01:00
> > Committer: Peter Zijlstra <peterz@infradead.org>
> > CommitterDate: Sat, 08 Feb 2025 15:43:12 +01:00
>
> Was this merged to sched/urgent or any other branches/RCs? Given gitweb link
> sends me to "Bad commit reference". I don't see this commit in sched/urgent:
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=sched%2Furgent
I think something weird has just happened to the tip tree. All the
tip/x86/* branches also seem to have been reset to Linux 6.15-rc6.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5069 bytes --]
next prev parent reply other threads:[~2025-05-23 16:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 17:50 Greg Kroah-Hartman
2025-01-21 17:51 ` [PATCH 6.12 053/122] kheaders: Ignore silly-rename files Greg Kroah-Hartman
2025-01-21 19:10 ` [PATCH 6.12 000/122] 6.12.11-rc1 review Florian Fainelli
2025-01-21 20:57 ` Peter Schneider
2025-01-21 21:46 ` Salvatore Bonaccorso
2025-01-21 22:15 ` Ronald Warsow
2025-01-22 7:04 ` Jon Hunter
2025-01-22 9:01 ` Ron Economos
2025-01-22 9:29 ` Greg Kroah-Hartman
2025-01-21 23:05 ` Takeshi Ogasawara
2025-01-21 23:31 ` Shuah Khan
2025-01-21 23:48 ` SeongJae Park
2025-01-22 10:04 ` Naresh Kamboju
2025-01-22 10:42 ` Peter Zijlstra
2025-01-22 10:56 ` Arnd Bergmann
2025-01-22 10:59 ` Peter Zijlstra
2025-01-22 11:11 ` Ron Economos
2025-01-28 11:46 ` Mike Galbraith
2025-01-28 14:39 ` Peter Zijlstra
2025-01-28 15:20 ` Mike Galbraith
2025-05-23 15:13 ` Mushahid Hussain
2025-02-08 14:51 ` [tip: sched/urgent] sched/fair: Adhere to place_entity() constraints tip-bot2 for Peter Zijlstra
2025-05-23 16:01 ` [PATCH 6.12 000/122] 6.12.11-rc1 review Mushahid Hussain
2025-05-23 16:46 ` David Woodhouse [this message]
2025-01-23 8:09 ` Harshit Mogalapalli
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=edf9a5e62d8a92956ebf6c167df7d0f77e7e11cf.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=efault@gmx.de \
--cc=hmushi@amazon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=nh-open-source@amazon.com \
--cc=peterz@infradead.org \
--cc=sieberf@amazon.com \
--cc=stable@vger.kernel.org \
--cc=tip-bot2@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®