From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"J.A. Magall?n" <jamagallon@ono.com>,
"Linux-Kernel," <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [2.6.18-rc2-mm1] libata ate one PATA channel
Date: Mon, 31 Jul 2006 15:05:23 -0400 [thread overview]
Message-ID: <44CE5473.8080903@pobox.com> (raw)
In-Reply-To: <44CE515B.1060302@gmail.com>
Tejun Heo wrote:
> I like 'registering both always and disabling one' approach for
> partially stolen legacy devices. We can make ->hard_port_no do the job
> as before, but IMHO it's error-prone and only useful for very limited
> cases (first legacy port stolen).
>
> Jeff, what do you think?
The reason for hard_port_no's existence is the fact that is can
sometimes differ from port_no, and we need to know the "real" port
number, as opposed to the port number based on counting probed ports.
If you eliminate the need for hard_port_no, feel free to erase it.
Jeff
next prev parent reply other threads:[~2006-07-31 19:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 11:45 [2.6.18-rc2-mm1] libata ate one PATA channel J.A. Magallón
2006-07-30 19:53 ` Tejun Heo
2006-07-31 15:24 ` J.A. Magallón
2006-07-31 16:00 ` Tejun Heo
2006-07-31 16:31 ` Alan Cox
2006-07-31 16:50 ` Tejun Heo
2006-07-31 17:03 ` Tejun Heo
2006-07-31 18:52 ` Alan Cox
2006-07-31 18:52 ` Tejun Heo
2006-07-31 19:05 ` Jeff Garzik [this message]
2006-07-31 18:38 ` Alan Cox
2006-07-31 21:41 ` J.A. Magallón
2006-08-01 6:22 ` Andrew Morton
2006-08-01 7:32 ` Tejun Heo
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=44CE5473.8080903@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jamagallon@ono.com \
--cc=linux-ide@vger.kernel.org \
--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.