From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "Martin J. Bligh" <mbligh@mbligh.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
video4linux-list@redhat.com,
linux-fbdev-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net, netdev@vger.kernel.org,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: open bugzilla reports
Date: Sat, 4 Feb 2006 23:14:26 +0000 [thread overview]
Message-ID: <20060204231425.GA24887@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20060204084729.defc7c19.mbligh@mbligh.org>
On Sat, Feb 04, 2006 at 08:47:29AM -0800, Martin J. Bligh wrote:
>
> > > [Bug 5958] CF bluetooth card oopses machine when
> > > http://bugzilla.kernel.org/show_bug.cgi?id=5958
> >
> > This isn't a serial bug - it's a bluetooth ldisc bug. I reported it
> > to the bluetooth folk back when it first got raised by Pavel. However,
> > they seem to be completely disinterested in fixing it.
> >
> > Unfortunately, there isn't a category for bt crap in bugzilla, otherwise
> > I'd reassign it. Please kick the bt folk.
>
> Stick it under Drivers/Other if you want ...
It _is_ under Networking/Other, yet akpm still thinks it's a serial
bug. I'm not sure why though, I've fully explained why it isn't
a serial problem in the bug comments.
akpm is buggy and needs fixing. Where do I file this bug? 8)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-02-04 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 23:11 open bugzilla reports Andrew Morton
2006-02-04 9:50 ` Russell King
2006-02-04 16:47 ` Martin J. Bligh
2006-02-04 23:14 ` Russell King [this message]
2006-02-05 21:09 ` Pavel Machek
2006-02-04 11:29 ` Eric Piel
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=20060204231425.GA24887@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=mbligh@mbligh.org \
--cc=netdev@vger.kernel.org \
--cc=video4linux-list@redhat.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;
as well as URLs for NNTP newsgroup(s).