All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Meelis Roos <mroos@linux.ee>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libATA  PATA status report, new patch
Date: Mon, 06 Feb 2006 22:53:36 +0000	[thread overview]
Message-ID: <1139266416.10437.60.camel@localhost.localdomain> (raw)
In-Reply-To: <20060206200400.E69E8142E2@rhn.tartu-labor>

On Llu, 2006-02-06 at 22:04 +0200, Meelis Roos wrote:
> AC>         http://zeniv.linux.org.uk/~alan/IDE
> AC> 
> AC> for 2.6.16-rc2 patches.
> 
> Should I #define ATA_ENABLE_PATA by hand in include file to get PIIX4
> PATA to wotk with the ata_piix driver, or should it just work?

You should set that define. Actually I should do that by default in the
patch set. I will fix that.


  reply	other threads:[~2006-02-06 22:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 16:46 libATA PATA status report, new patch Alan Cox
2006-02-06 20:04 ` Meelis Roos
2006-02-06 22:53   ` Alan Cox [this message]
2006-02-07  8:43 ` Meelis Roos
2006-02-07 11:05   ` Alan Cox
2006-02-07 11:10     ` Meelis Roos
2006-02-07 11:29       ` Ed Sweetman
2006-02-07 11:32         ` Meelis Roos
2006-02-07 11:38       ` Alan Cox
2006-02-07 15:04         ` Alan Cox
2006-02-07 17:02           ` Meelis Roos
2006-02-07 19:38             ` Duplicated SCSI messages (Was: Re: libATA PATA status report, new patch) Tomasz Kłoczko
2006-02-07 17:30           ` libATA PATA status report, new patch Meelis Roos
2006-02-07 17:50           ` Meelis Roos
2006-02-08 13:31             ` Alan Cox
2006-02-08  7:42           ` Meelis Roos
2006-02-08 18:28           ` Meelis Roos
2006-02-09 15:31             ` Alan Cox
2006-02-09 21:12               ` Meelis Roos
2006-02-10 12:01                 ` Erik Mouw
2006-02-10 15:46                   ` Alan Cox
2006-02-12 18:07 ` Kyle Moffett
2006-07-07 16:29 ` Wakko Warner
2006-07-07 16:52   ` 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=1139266416.10437.60.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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.