All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Thorsten Leemhuis <fedora@leemhuis.info>
Cc: Chr <chunkeey@web.de>,
	"Gaston, Jason D" <jason.d.gaston@intel.com>,
	Chuck Ebbert <cebbert@redhat.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 2.6.22-rc6] ATA: add a PCI ID for Intel Santa Rosa PATA controller
Date: Fri, 06 Jul 2007 16:43:51 -0400	[thread overview]
Message-ID: <468EA987.80001@garzik.org> (raw)
In-Reply-To: <468E9F9C.9010508@leemhuis.info>

Thorsten Leemhuis wrote:
> But anyway: Sorry, am I the only one that gets nervous if we start to
> run a ATA-Hardware (Intels recent ICH southbridges in this case) with a
> speed grade (Ultra ATA/133) that is not specified by its manufacturer in
> his public data sheets (Ultra ATA/100 max)?

That's why the patch I applied referenced ATA/100...

If they fix the datasheets, we can always upgrade it later.

	Jeff



  reply	other threads:[~2007-07-06 20:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-28 19:16 ATA: add a PCI ID for Intel Santa Rosa PATA controller Chuck Ebbert
2007-06-28 19:47 ` [patch 2.6.22-rc6] " Chuck Ebbert
2007-06-29 14:31   ` Jeff Garzik
2007-07-02  5:02   ` Thorsten Leemhuis
2007-07-02  9:07     ` Thorsten Leemhuis
2007-07-02 11:24       ` Chr
2007-07-02 11:44         ` Thorsten Leemhuis
2007-07-02 14:36           ` Chr
2007-07-04 14:03             ` Thorsten Leemhuis
2007-07-05 20:30               ` Chr
2007-07-06 19:06                 ` Gaston, Jason D
2007-07-06 19:06                   ` Gaston, Jason D
2007-07-06 19:45                   ` Chr
2007-07-06 20:01                     ` Thorsten Leemhuis
2007-07-06 20:43                       ` Jeff Garzik [this message]
2007-07-05 21:17               ` Alan Cox

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=468EA987.80001@garzik.org \
    --to=jeff@garzik.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cebbert@redhat.com \
    --cc=chunkeey@web.de \
    --cc=fedora@leemhuis.info \
    --cc=jason.d.gaston@intel.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.