From: Stacy Woods <stacyw@us.ibm.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
"Martin J. Bligh" <mbligh@aracnet.com>
Subject: Bugs sitting in the RESOLVED state for more than 2 weeks
Date: Tue, 22 Apr 2003 11:04:50 -0400 [thread overview]
Message-ID: <3EA55A12.2090306@us.ibm.com> (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 khoa@us.ibm.com
statfs returns incorrect number fo blocks
85 Drivers Network jgarzik@pobox.com
ham radio stuff still using cli etc
150 Drivers PNP ambx1@neo.rr.com
[PNP][2.5] IDE Detection problems (wrong IRQ and wrong IDE device number)
206 Drivers Console/ jsimmons@infradead.org
broken colors on framebuffer console
282 Drivers Other hannal@us.ibm.com
tty drivers need to set .owner field
367 Platform Alpha rth@twiddle.net
modules fail to resolve illegal Unhandled relocation of type 10 for .text
372 Platform UML jdike@karaya.com
uml doesn't not compile
404 File Sys ext3 akpm@digeo.com
turning off htree causes fsck to complain
418 Drivers USB greg@kroah.com
Bad use of GFP_DMA
500 Memory M Page All akpm@digeo.com
fbcon sleeping function call from illegal context
next reply other threads:[~2003-04-22 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 15:04 Stacy Woods [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-03 15:47 Bugs sitting in the RESOLVED state for more than 2 weeks Stacy Woods
2003-04-03 17:28 ` Trond Myklebust
2003-03-06 19:24 Stacy Woods
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=3EA55A12.2090306@us.ibm.com \
--to=stacyw@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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