From: Steven Walter <srwalter@yahoo.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH 2.4.4.7: serial PCI fixes and cleanup
Date: Thu, 26 Apr 2001 17:59:07 -0500 [thread overview]
Message-ID: <20010426175907.A673@hapablap.dyn.dhs.org> (raw)
In-Reply-To: <3AE80BAC.494F096B@mandrakesoft.com>
In-Reply-To: <3AE80BAC.494F096B@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Thu, Apr 26, 2001 at 07:51:08AM -0400
Just a heads up: works great for me
On Thu, Apr 26, 2001 at 07:51:08AM -0400, Jeff Garzik wrote:
> The attached patch, against 2.4.4-pre7, cleans up the huge pci_board
> list in serial.c to remove PCI id information. In the process, it (a)
> demonstrates more complex new-style PCI probing, and (b) fixes a logical
> disconnect bug which was causing bug reports. The bug caused by me,
> when I added hotplugging to the serial driver (merging serial_cb in
> function, but not literally). The bug causes any PCI board which is
> listed in the serial.c PCI table, but was not
> PCI_CLASS_COMMUNICATION_SERIAL or PCI_CLASS_COMMUNICATION_MODEM, to be
> missed in the PCI probe.
>
> Linus - do not apply just yet. I would prefer this patch go into 2.4.5
> not 2.4.4, so that we can have a bit more public testing first.
> tytso - a quick eyeball would be awesome. Ask away with any questions
> you have.
> Alan - please consider applying to your tree.
> Steven - please test, this patch removes the need for your serial.c
> patch.
>
> Others - all testing is welcome.
prev parent reply other threads:[~2001-04-26 22:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 11:51 PATCH 2.4.4.7: serial PCI fixes and cleanup Jeff Garzik
2001-04-26 22:59 ` Steven Walter [this message]
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=20010426175907.A673@hapablap.dyn.dhs.org \
--to=srwalter@yahoo.com \
--cc=jgarzik@mandrakesoft.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 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.