From: Andrew Morton <akpm@linux-foundation.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-kernel@vger.kernel.org, phdm@macqel.be,
hancockrwd@gmail.com, abelay@mit.edu, lenb@kernel.org,
stable@kernel.org
Subject: Re: [PATCH] floppy: request only the ports we actually use
Date: Thu, 5 Feb 2009 14:29:48 -0800 [thread overview]
Message-ID: <20090205142948.1a48d983.akpm@linux-foundation.org> (raw)
In-Reply-To: <200902051055.34149.bjorn.helgaas@hp.com>
On Thu, 5 Feb 2009 10:55:33 -0700
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> On Thursday 05 February 2009 10:48:59 am Bjorn Helgaas wrote:
> > The floppy driver requests an I/O port it doesn't need, and
> > sometimes this causes a conflict with a motherboard device
> > reported by PNPBIOS.
> >
> > This patch makes the floppy driver request only the ports it
> > actually uses.
> > ...
> > Philippe reported that this conflict broke the floppy driver between
> > 2.6.11 and 2.6.22. ...
>
> While this is old and BIOS-specific, it is a regression, so we might
> consider it for 2.6.29.
>
And earlier, surely?
I tagged it
Cc: <stable@kernel.org> [2.6.25.x, 2.6.26.x, 2.6.27.x, 2.6.28.x]
(I'm not sure if 2.6.25.x is still being maintained by Greg & Chris,
but other parties are maintaining 2.6.25-based kernels, and such
tagging might help them).
next prev parent reply other threads:[~2009-02-05 22:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 17:48 Bjorn Helgaas
2009-02-05 17:55 ` Bjorn Helgaas
2009-02-05 22:29 ` Andrew Morton [this message]
2009-02-05 23:43 ` Bjorn Helgaas
2009-02-06 8:55 ` [PATCH] floppy: release only the ports we actually requested Philippe De Muyter
2009-02-06 16:20 ` Bjorn Helgaas
2009-02-06 17:57 ` Bjorn Helgaas
2009-02-09 9:15 ` Philippe De Muyter
2009-02-10 17:16 ` Bjorn Helgaas
2009-02-13 8:55 ` [PATCH] floppy: request and release only the ports we actually use Philippe De Muyter
2009-02-13 16:37 ` Bjorn Helgaas
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=20090205142948.1a48d983.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=abelay@mit.edu \
--cc=bjorn.helgaas@hp.com \
--cc=hancockrwd@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phdm@macqel.be \
--cc=stable@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
Powered by JetHome