linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: 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 09:50:23 +0000	[thread overview]
Message-ID: <20060204095023.GA11140@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20060203151150.3d9aa8b3.akpm@osdl.org>

On Fri, Feb 03, 2006 at 03:11:50PM -0800, Andrew Morton wrote:
> serial
> ======
> 
> [Bug 5832] Enabling ACPI Plug and Play in kernels
> 	http://bugzilla.kernel.org/show_bug.cgi?id=5832

This seems to be misfiled.  Why do you think this is a serial bug?
It seems to be talking about parallel ports.

> [Bug 5875] quad RS232 port card detected as 8,
> 	http://bugzilla.kernel.org/show_bug.cgi?id=5875

This seems to be because we have an explicit vendor/device ID listed
in 8250_pci for (according to this bug report) something which isn't
a serial device.  What I don't know is if these vendor/device IDs
also exist for something which is a serial device.  Hence, removing
them could cause more problems than keeping them.  Since it has no
effect other than causing extra ports to appear, this is low priority.

> [Bug 5942] serial driver gives up and we get IRQ3
> 	http://bugzilla.kernel.org/show_bug.cgi?id=5942

No idea what's happening here.  No one else seems to be using IRQ3,
we've disabled the interrupt at the UART, yet we get a stuck IRQ3.
Don't think it's serial related, it just happens that closing the
serial port shows it.

> [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.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2006-02-04  9:50 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 [this message]
2006-02-04 16:47   ` Martin J. Bligh
2006-02-04 23:14     ` Russell King
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=20060204095023.GA11140@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=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).