Control: tag -1 wontfix
Control: severity -1 normal
As this usage of block devices is not supported by upstream and that
isn't likely to change, I'm marking this wontfix and reducing severity.
Ben.
--
Ben Hutchings
All the simple programs have been written, and all the good names taken
sign
Control: reopen -1
Hi Joshua,
On Wed, Feb 19, 2025 at 07:39:34AM -0800, Joshua Hudson wrote:
> Bug is still active on upstream kernel today. Verification is trivial.
Thanks for reporting back. In this case can you please report it to
upstream and reference the upstream report here please?
I'm
Hi Joshua,
On Wed, Feb 19, 2025 at 07:57:16AM -0800, Joshua Hudson wrote:
> I did long ago; no one cares.
Went trough the upstream posting at
https://lore.kernel.org/lkml/CA+jjjYTk=5wn2o46uNB+bJYX8xLgMP==dsjuvc94dvtn2f_...@mail.gmail.com/
.
So as long there is nothing ongoing upstream related to
I did long ago; no one cares.
On Wed, Feb 19, 2025 at 7:55 AM Salvatore Bonaccorso wrote:
>
> Control: reopen -1
>
> Hi Joshua,
>
> On Wed, Feb 19, 2025 at 07:39:34AM -0800, Joshua Hudson wrote:
> > Bug is still active on upstream kernel today. Verification is trivial.
>
> Thanks for reporting ba
Bug verified *upstream* on stock kernel version 6.4.12
Package: src:linux
Version: 6.1.38-4
Severity: important
Dear Maintainer,
* What led up to the situation?
Upgrade to bookworm fragmented the EFI paritition (due to changing boot logo)
and defrag was in order. As this BIOS
currently has broken legacy boot, I used dosbox-x to defrag the EFI pa
6 matches
Mail list logo
