linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Velu Erwan <erwan@seanodes.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: SATA feature list available
Date: Thu, 15 Dec 2005 22:16:59 +0000	[thread overview]
Message-ID: <1134685019.20495.0.camel@localhost.localdomain> (raw)
In-Reply-To: <43A1AEA7.60101@seanodes.com>

On Iau, 2005-12-15 at 18:57 +0100, Velu Erwan wrote:
> Alan Cox a écrit :
> 
> >ATIIXP
> >  
> >
> Did your patch includes a patch for ATIIXP to solve the troubles we 
> tried to fix with bruno ?

No. I'd actually expect libata to handle that internally as its drive
level, but I'm not sure it does. Added to the 'to investigate' list.


  reply	other threads:[~2005-12-15 22:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-15 17:10 SATA feature list available Jeff Garzik
2005-12-15 17:51 ` Alan Cox
2005-12-15 17:57   ` Velu Erwan
2005-12-15 22:16     ` Alan Cox [this message]
2005-12-16  9:14       ` Velu Erwan

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=1134685019.20495.0.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=erwan@seanodes.com \
    --cc=jgarzik@pobox.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 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).