From: Jeff Garzik <jeff@garzik.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.20-rc4 1/2] sata_promise: TX2plus PATA support
Date: Tue, 09 Jan 2007 05:12:46 -0500 [thread overview]
Message-ID: <45A36A9E.8030408@garzik.org> (raw)
In-Reply-To: <200701090950.l099oRPU011573@harpo.it.uu.se>
Mikael Pettersson wrote:
> This patch implements a simple way of setting up per-port
> flags on the SATA+PATA Promise TX2plus chips, which is a
> prerequisite for supporting the PATA port on those chips.
>
> It is based on the observation that ap->flags isn't really
> used until after ->port_start() has been invoked. So it
> places the "exceptional" per-port flags array in the driver's
> private host structure, and uses it in ->port_start() to
> finalise the port's flags.
>
> This patch obsoletes the #promise-sata-pata branch included
> in the #all branch.
>
> Signed-off-by: Mikael Pettersson <mikpe@it.uu.se>
applied patches 1-2 to #upstream. minor follow-up comments follow in
separate emails.
Thanks a bunch for working on this, sata_promise has needed some "love"
for quite a while.
Any chance you could be talked to becoming "official" sata_promise
maintainer, by sending in a patch to MAINTAINERS?
One open issue that remains is port enumeration order. Bug reports
consistently indicate that the ports are numbered on the board (visible
to the naked eye) in a different manner than how the chip enumerates
each port. According to the bug reports, Promise's driver enumerates
the ports in the correct order.
Jeff
next prev parent reply other threads:[~2007-01-09 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 9:50 [PATCH 2.6.20-rc4 1/2] sata_promise: TX2plus PATA support Mikael Pettersson
2007-01-09 10:12 ` Jeff Garzik [this message]
2007-01-09 10:16 ` Jeff Garzik
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=45A36A9E.8030408@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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).