linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Rob OpenSuSE <rob.opensuse.linux@googlemail.com>
Cc: Mark Lord <liml@rtr.ca>,
	Sergei Shtylyov <sshtylyov@ru.mvista.com>,
	Jeff Garzik <jeff@garzik.org>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [RFC PATCH] pata_hpt366: fix mode configuration
Date: Wed, 10 Dec 2008 16:00:22 +0900	[thread overview]
Message-ID: <493F6906.9010407@kernel.org> (raw)
In-Reply-To: <ce9d8ed60812091302k37b220d1l3dce6878274d8be2@mail.gmail.com>

Rob OpenSuSE wrote:
> 2008/12/9 Mark Lord <liml@rtr.ca>:
>> Rob OpenSuSE wrote:
>> There are tons of PCI add-on cards still out there with these chips,
>> and they will continue to work fine so long as PCI slots
>> and PATA drives exist.  So we may as well ensure Linux does the Right Things (tm).
> 
> Yes, my point was in support of pragmatism; so that new kernel builds
> and distro installs can have a chance to succeed in boxes with these
> cards used, without opening case,  reconfiguring, and finding special
> boot paramters.  Those cards need working code now, not next year.  So
> "The Right Thing (tm)" would be bad, if it caused perfectly capable
> kit to be non-functioning, whilst perfection is under discussion and
> development.

I already pushed those patches into openSUSE and in one form or
another it will make into upstream and other distros, so no worries.

>> Nice work, Tejun!
> 
> Seconded!  If you are the Mark who sent the card, thanks to you to
> from me to.

Yeap, he's the Mark who sends me old and weird hardwares from time to
time.  :-)

Thanks.

-- 
tejun

      reply	other threads:[~2008-12-10  7:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08  7:11 [RFC PATCH] pata_hpt366: fix mode configuration Tejun Heo
2008-12-08 10:40 ` Sergei Shtylyov
2008-12-08 23:18   ` Rob OpenSuSE
2008-12-09 19:47     ` Mark Lord
2008-12-09 21:02       ` Rob OpenSuSE
2008-12-10  7:00         ` Tejun Heo [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=493F6906.9010407@kernel.org \
    --to=tj@kernel.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=rob.opensuse.linux@googlemail.com \
    --cc=sshtylyov@ru.mvista.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 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).