From: Steven Rostedt <rostedt@goodmis•org>
To: "Aithal, Srikanth" <sraithal@amd•com>
Cc: Bert Karwatzki <spasswolf@web•de>,
"Paul E . McKenney" <paulmck@kernel•org>,
Andrew Morton <akpm@linux-foundation•org>,
Kuniyuki Iwashima <kuniyu@amazon•com>,
Mateusz Guzik <mjguzik@gmail•com>, Petr Mladek <pmladek@suse•com>,
John Ogness <john.ogness@linutronix•de>,
Sergey Senozhatsky <senozhatsky@chromium•org>,
linux-kernel@vger•kernel.org,
Linux-Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: commit dd4cf8c9e1f4 leads to failed boot
Date: Wed, 23 Apr 2025 10:01:15 -0400 [thread overview]
Message-ID: <20250423100115.657c68be@gandalf.local.home> (raw)
In-Reply-To: <8f7671cc-32f1-4028-a1b0-c7dccf472f76@amd.com>
On Wed, 23 Apr 2025 19:17:43 +0530
"Aithal, Srikanth" <sraithal@amd•com> wrote:
> On todays linux-next build the commit id is
> c8943bdecfc76711f83241e21da9d4530f872f0d.
Which is why you should always state the subject of the commit and not only
use the sha of the commit.
Thanks,
-- Steve
next prev parent reply other threads:[~2025-04-23 13:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250423115409.3425-1-spasswolf@web.de>
2025-04-23 13:39 ` commit dd4cf8c9e1f4 leads to failed boot Aithal, Srikanth
2025-04-23 13:46 ` Steven Rostedt
2025-04-23 13:47 ` Aithal, Srikanth
2025-04-23 14:01 ` Steven Rostedt [this message]
2025-04-23 14:02 ` Steven Rostedt
2025-04-23 14:18 ` Paul E. McKenney
2025-04-23 14:59 ` Bert Karwatzki
2025-04-23 18:03 ` Bert Karwatzki
2025-04-23 15:19 ` Aithal, Srikanth
2025-04-23 18:07 ` Paul E. McKenney
2025-04-23 19:19 ` Bert Karwatzki
2025-04-23 19:56 ` Paul E. McKenney
2025-04-24 4:30 ` Aithal, Srikanth
2025-04-24 7:36 ` Petr Mladek
2025-04-24 14:43 ` Paul E. McKenney
2025-04-25 9:35 ` Petr Mladek
2025-04-25 16:34 ` Paul E. McKenney
2025-04-24 12:40 ` Bert Karwatzki
2025-04-24 14:30 ` Paul E. McKenney
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=20250423100115.657c68be@gandalf.local.home \
--to=rostedt@goodmis$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=john.ogness@linutronix$(echo .)de \
--cc=kuniyu@amazon$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mjguzik@gmail$(echo .)com \
--cc=paulmck@kernel$(echo .)org \
--cc=pmladek@suse$(echo .)com \
--cc=senozhatsky@chromium$(echo .)org \
--cc=spasswolf@web$(echo .)de \
--cc=sraithal@amd$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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