From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 216902] WARNING: CPU: 0 PID: 70 at kernel/locking/irqflag-debug.c:10 at kallsyms_selftest
Date: Sat, 19 Aug 2023 23:03:47 +0000 [thread overview]
Message-ID: <bug-216902-206035-Yyt97Lr4GD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216902-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216902
Erhard F. (erhard_f@mailbox.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |OBSOLETE
--- Comment #2 from Erhard F. (erhard_f@mailbox.org) ---
Have not seen this on kernel 6.4.x and latest 6.5-rc6.
Closing.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2023-08-19 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 14:00 [Bug 216902] New: WARNING: CPU: 0 PID: 70 at kernel/locking/irqflag-debug.c:10 at kallsyms_selftest bugzilla-daemon
2023-01-08 14:01 ` [Bug 216902] " bugzilla-daemon
2023-08-19 23:03 ` bugzilla-daemon [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=bug-216902-206035-Yyt97Lr4GD@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).