public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hank Yang" <hanky@promise.com.tw>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>, <torvalds@transmeta.com>,
	<arjanv@redhat.com>
Subject: Re: [PATCH] Submitting PROMISE IDE Controllers Driver Patch
Date: Wed, 13 Mar 2002 14:52:48 +0800	[thread overview]
Message-ID: <03ca01c1ca5b$b030afe0$59cca8c0@hank> (raw)
In-Reply-To: <E16jKCT-00068v-00@the-village.bc.nu>

Hi, Alan.

    The patch-file 'patch-2.4.19-pre2-ac3' needs be modified for pdc202xx.c.
In pdc202xx.c, pdc202xx_new_tune_chipset()
switch (speed) to set timing only when UDMA 6 drives exist on ATA-133
controller (PDC20269 and PDC20275). If there are no any UDMA 6 drives
exists, we don't need to set timing here.

    Would you please modify this part?

Thanks and Regards
Hank

> >     I saw the 'patch-2.4.19-pre2-ac3' and it has build-in Maxtor 48 bit
lba
> > spec. Is these patch will be build into next kernel version 2.4.19?
> > Do you want us to make a patch for the 'patch-2.4.19-pre2-ac3'?
>
> I've submitted the IDE code in 2.4.19-pre2-ac3 to Marcelo and he has
> accepted it for 2.4.19-pre3. Hopefully that makes your job easier too.
>
> Alan


  reply	other threads:[~2002-03-13  6:54 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-07  9:01 [PATCH] Submitting PROMISE IDE Controllers Driver Patch Hank Yang
2002-03-07 10:23 ` Arjan van de Ven
2002-03-08  1:45   ` Hank Yang
2002-03-08  2:10     ` Alan Cox
2002-03-08  3:01       ` Hank Yang
2002-03-08  8:19         ` Martin Dalecki
2002-03-08  8:23           ` arjan
2002-03-08  8:35             ` Martin Dalecki
2002-03-08  8:50               ` Arjan van de Ven
2002-03-08  9:14                 ` Martin Dalecki
2002-03-08 13:12                 ` Alan Cox
2002-03-08 19:25                 ` Kelsey Hudson
2002-03-09 13:25                   ` Martin Dalecki
2002-03-08 13:25         ` Alan Cox
2002-03-13  7:35           ` Hank Yang
2002-03-13  7:45             ` Arjan van de Ven
2002-03-08  2:54     ` Kelsey Hudson
2002-03-08  7:54     ` Arjan van de Ven
2002-03-08  8:12     ` Martin Dalecki
2002-03-07 13:15 ` Alan Cox
2002-03-08  3:49   ` Hank Yang
2002-03-08 13:14     ` Alan Cox
2002-03-13  6:52       ` Hank Yang [this message]
2002-03-13 16:39         ` Alan Cox
2002-05-22  9:38           ` Hank Yang
     [not found]           ` <039701c20892$3940ca30$c0cca8c0@promise.com.tw>
2002-05-31 14:33             ` [PATCH] Submitting PROMISE IDE " Alan Cox
2002-06-03  3:51               ` [PATCH] 2.4.19pre9 in pdc202xx.c bug Hank Yang
2002-06-03 15:48                 ` Alan Cox
2002-06-06  2:31                   ` Hank Yang
2002-06-06 12:17                     ` Alan Cox
     [not found] ` <3C876199.5000107@evision-ventures.com>
2002-03-08  2:00   ` [PATCH] Submitting PROMISE IDE Controllers Driver Patch Hank Yang
  -- strict thread matches above, loose matches on Subject: below --
2002-03-10 14:23 Ed Tomlinson
2002-03-10 14:47 ` Alan Cox
2002-03-11  9:56   ` benh
     [not found] <200203071331.g27DVi211087@sunrise.pg.gda.pl>
2002-03-07 13:36 ` Andrzej Krzysztofowicz
2002-03-07  6:46 Hank Yang
2002-03-09 21:23 ` Pavel Machek

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='03ca01c1ca5b$b030afe0$59cca8c0@hank' \
    --to=hanky@promise.com.tw \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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