Skip to contentSkip to conversation

Bugs sitting in the RESOLVED state for more than 2 weeks

DISCUSSION Stacy Woods 2 participants 2 messages Apr 3, 2003

lore
Share & tools
lore
#0 lore raw

These bugs have been sitting in RESOLVED state for more than two weeks, 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

230 Other Configur [email protected]
diffsrv URL changed

300 Alternat mjb [email protected]
Oops in 2.5.59-mjb1

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

404 File Sys ext3 [email protected]
turning off htree causes fsck to complain

#1 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

" " == Stacy Woods <[email protected]> writes:

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

This patch is *not* NFS specific. It needs to be pushed to linux-fsdevel and linux-kernel for more general review.

Cheers,
Trond