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 28 days
Date: Fri, 13 Jun 2003 14:25:26 -0400 [thread overview]
Message-ID: <3EEA1716.9000903@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
345 Drivers SCSI mikenc@us.ibm.com
compile failure in drivers/scsi/inia100.c
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
412 Drivers USB dbrownell@users.sourceforge.net
[EHCI] report of first interrupt transfer is delayed
418 Drivers USB greg@kroah.com
Bad use of GFP_DMA
663 Drivers Sound bugme-janitors@lists.osdl.org
"make modules" causes an error in mwavedd.h.
691 Platform x86-64 ak@suse.de
change_pageattr corrupts memory (breaks AGP)
next reply other threads:[~2003-06-13 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 18:25 Stacy Woods [this message]
2003-06-13 18:40 ` Bugs sitting in the RESOLVED state for more than 28 days Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-07-15 19:01 Stacy Woods
2003-08-19 13:36 Stacy Woods
2003-09-19 15:04 Stacy Woods
2003-10-24 13:12 Stacy Woods
2003-10-24 19:00 ` Sam Ravnborg
2003-12-04 19:43 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=3EEA1716.9000903@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.