From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 222016] kernel 5.15.221 does not recognize mbr partitions and therefore does not boot
Date: Sat, 19 Sep 2026 14:36:01 +0000 [thread overview]
Message-ID: <bug-222016-11613-qllzvVmJMH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-222016-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=222016
Richard Narron (richard@aaazen.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|CODE_FIX |---
--- Comment #15 from Richard Narron (richard@aaazen.com) ---
Where is the new version of 5.15.x with the bugfix?
I see nothing on kernel.org...
Programming manager John Moline used to have programmers who reported bug fixes
as "done" before the code was installed into production.
He made sure that the fix was "done done" before closing it out.
I'm marking this bug as open until it is "done done".
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2026-09-19 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-222016-11613@https.bugzilla.kernel.org/>
2026-09-16 19:28 ` [Bug 222016] kernel 5.15.221 does not recognize mbr partitions and therefore does not boot bugzilla-daemon
2026-09-19 7:12 ` bugzilla-daemon
2026-09-19 14:36 ` bugzilla-daemon [this message]
2026-09-24 16:58 ` bugzilla-daemon
2026-09-24 17:06 ` bugzilla-daemon
2026-09-25 13:58 ` bugzilla-daemon
2026-09-25 14:55 ` bugzilla-daemon
2026-09-29 21:29 ` bugzilla-daemon
2026-09-29 21:33 ` bugzilla-daemon
2026-09-30 20:46 ` bugzilla-daemon
2026-10-01 13:00 ` bugzilla-daemon
2026-10-03 14:19 ` bugzilla-daemon
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-222016-11613-qllzvVmJMH@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-scsi@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