public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Theo Kanter <theo@verkstad.net>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.18 PATA support for sata_promise not working for PDC20378 on MSI 865PE-NEO FISR2 motherboard
Date: Sun, 01 Oct 2006 22:12:49 +0200	[thread overview]
Message-ID: <45202141.3010304@verkstad.net> (raw)
In-Reply-To: <45201E98.5030104@garzik.org>

Jeff Garzik wrote:
> Theo Kanter wrote:
>> Kernel 2.6.18 claims to provide PATA support for sata_promise 
>> according to the changelog.
> Which changelog?  I assure you (a) PATA support for sata_promise is 
> not in 2.6.18, and (b) it implies nothing of the sort in the official 
> kernel changelog on ftp.kernel.org.
Thanks Jeff for a quick response. Well, it is only because 
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.18 mentions 
the following:

    Author: Jeff Garzik <jeff@garzik.org>
    Date:   Wed May 24 01:43:25 2006 -0400
        [libata sata_promise] Add PATA cable detection.
        Original patch from Phillip Jordan <phillip.m.jordan@gmail.com>
        Cleanups and fixes by me.

Does this mean something other than that sata_promise actually provides 
support for PATA or how should I interpret this? Also, with respect to 
the error messages in my previous messages, could you please advise me 
about my options? (e.g., wait for a new kernel, etc.)?

Thanks,
Theo



      reply	other threads:[~2006-10-01 20:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-01 19:38 Kernel 2.6.18 PATA support for sata_promise not working for PDC20378 on MSI 865PE-NEO FISR2 motherboard Theo Kanter
2006-10-01 20:01 ` Jeff Garzik
2006-10-01 20:12   ` Theo Kanter [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=45202141.3010304@verkstad.net \
    --to=theo@verkstad.net \
    --cc=jeff@garzik.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox