Skip to contentSkip to conversation

Bugs sitting in the RESOLVED state for more than 28 days

DISCUSSION Stacy Woods 2 participants 2 messages Jun 13, 2003

lore
Share & tools
lore
#0 lore raw

These bugs have been sitting in RESOLVED state for more than 28 days, ie, they have fixes, but aren't back in the mainline tree (when they should move to CLOSED state). If the fixes are back in mainline already, could the owner close them out? Otherwise, perhaps we can get those fixes back in?

Kernel Bug Tracker: http://bugme.osdl.org

24 File Sys NFS [email protected]
statfs returns incorrect number fo blocks

85 Drivers Network [email protected]
ham radio stuff still using cli etc

150 Drivers PNP [email protected]
[PNP][2.5] IDE Detection problems (wrong IRQ and wrong IDE device number)

206 Drivers Console/ [email protected]
broken colors on framebuffer console

345 Drivers SCSI [email protected]
compile failure in drivers/scsi/inia100.c

367 Platform Alpha [email protected]
modules fail to resolve illegal Unhandled relocation of type 10 for .text

372 Platform UML [email protected]
uml doesn't not compile

412 Drivers USB [email protected]
[EHCI] report of first interrupt transfer is delayed

418 Drivers USB [email protected]
Bad use of GFP_DMA

663 Drivers Sound [email protected]
"make modules" causes an error in mwavedd.h.

691 Platform x86-64 [email protected]
change_pageattr corrupts memory (breaks AGP)