mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ann_pearlstein@mysunrise.ch
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re:Re: libata and the 2.4 kernel
Date: Wed, 21 Apr 2004 09:38:18 +0200 (MEST)	[thread overview]
Message-ID: <31404467.1082533098090.JavaMail.tomcat4@webmail-be-07.sunrise.ch> (raw)

Hello Marcelo and the mailing list,

Thanks for the information.

For anyone else with similar questions, here's a good article on the subject, visit kerneltrap.org - there's an article abou it.  Here's the horrible URL:

http://kerneltrap.org/node/view/2926?PHPSESSID=01eda553525e02042e94270e386a37f6

Cheers,

Ann

Ann Pearlstein
ann_pearlstein@mysunrise.ch


>On Tue, Apr 20, 2004 at 02:21:50PM +0200, ann_pearlstein@mysunrise.ch wrote:
>> Hello,
>> 
>> Does anyone know when (or even if) the libata patch will be native to the 2.4 kernel (e.g., no patch needed)?  
>> 
>> If there are plans to add it to the 2.4 kernel, when (approximately :-)  ) will it be a part of this kernel?
>> 
>> I know it's supported natively in the 2.6 kernel.
>> 
>> The libata patch (2.4.25 kernel and 2.4.25 libata patch) works well for the serial ATA drive I use (in a Dell PowerEdge 750), but I'd like to have a non-patched kernel for this particular project.  
>> 
>> Thank you in advance for any and all info.
>
>Ann, 
>
>libata has been included in the 2.4 BK tree.
>
>You can try 2.4.26-bk patches (www.kernel.org)
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>

                 reply	other threads:[~2004-04-21  7:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=31404467.1082533098090.JavaMail.tomcat4@webmail-be-07.sunrise.ch \
    --to=ann_pearlstein@mysunrise.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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
all inboxes | Powered by JetHome®