From: Stacy Woods <stacyw@us.ibm.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Bugs sitting in the RESOLVED state for more than 28 days
Date: Tue, 15 Jul 2003 15:01:05 -0400 [thread overview]
Message-ID: <3F144F71.4050106@us.ibm.com> (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 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
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
590 File Sys VFS zwane@holomorphy.com
Cannot boot: get VFS cannot mount root on XFS and EXT2 partitions
719 Process Schedule rml@tech9.net
[perf][kernbench] lower performance with HT enabled on low loads
796 File Sys JFS shaggy@austin.ibm.com
Kernel Oops with nfsd.
807 Drivers PCMCIA bugme-janitors@lists.osdl.org
gprs pcmcia card not works in linux
next reply other threads:[~2003-07-15 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 19:01 Stacy Woods [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 19:43 Bugs sitting in the RESOLVED state for more than 28 days Stacy Woods
2003-10-24 13:12 Stacy Woods
2003-10-24 19:00 ` Sam Ravnborg
2003-09-19 15:04 Stacy Woods
2003-08-19 13:36 Stacy Woods
2003-06-13 18:25 Stacy Woods
2003-06-13 18:40 ` Greg KH
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=3F144F71.4050106@us.ibm.com \
--to=stacyw@us.ibm.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).