From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: albertl@mail.com
Cc: Tejun Heo <htejun@gmail.com>, Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org, Brian King <brking@us.ibm.com>,
Doug Maxey <dwm@bebe.enoyolf.org>,
Unicorn Chang <uchang@tw.ibm.com>
Subject: Re: [PATCH] libata: add host_set->next for legacy two host_sets case, take #3
Date: Wed, 28 Jun 2006 12:38:52 +0100 [thread overview]
Message-ID: <1151494733.15166.18.camel@localhost.localdomain> (raw)
In-Reply-To: <44A25979.3020709@tw.ibm.com>
Ar Mer, 2006-06-28 am 18:27 +0800, ysgrifennodd Albert Lee:
> Hmm, the current patch looks more like a temporary solution. The legacy mode
> ATA_HOST_SIMPLEX host_set->flags could be assigned to both legacy ports.
> In the long term, have one host_set for both legacy ports
> instead of two host_sets for both legacy ports can fix the problem.
I'm diddling with this at the moment. Following up on Jeffs request that
there should be a single host_set in such cases since its the same pci
device.
Alan
prev parent reply other threads:[~2006-06-28 11:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 5:17 [PATCH] libata: add host_set->next for legacy two host sets case Tejun Heo
2006-06-12 6:55 ` Jeff Garzik
2006-06-12 7:06 ` Tejun Heo
2006-06-12 10:14 ` [PATCH] libata: add host_set->next for legacy two host_sets case, take #2 Tejun Heo
2006-06-12 13:35 ` Jeff Garzik
2006-06-12 13:44 ` Tejun Heo
2006-06-12 14:05 ` [PATCH] libata: add host_set->next for legacy two host_sets case, take #3 Tejun Heo
2006-06-12 14:24 ` Jeff Garzik
2006-06-28 10:27 ` Albert Lee
2006-06-28 10:42 ` Tejun Heo
2006-06-28 10:53 ` Albert Lee
2006-06-28 16:25 ` Alan Cox
2006-06-28 11:38 ` Alan Cox [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=1151494733.15166.18.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=albertl@mail.com \
--cc=brking@us.ibm.com \
--cc=dwm@bebe.enoyolf.org \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=uchang@tw.ibm.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 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.