mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Hank Yang" <hanky@promise.com.tw>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>, <andre@serialata.org>,
	<marcelo@conectiva.com>
Cc: <torvalds@transmeta.com>, <linux-kernel@vger.kernel.org>,
	<arjanv@redhat.com>, "Linus Chen" <linusc@promise.com.tw>,
	<jordanr@promise.com>
Subject: Re: [PATCH] 2.4.19pre9 in pdc202xx.c bug
Date: Thu, 6 Jun 2002 10:31:39 +0800	[thread overview]
Message-ID: <004501c20d02$4ac734a0$c0cca8c0@promise.com.tw> (raw)
In-Reply-To: PI-LINK-449536473d07624bf639264807e919bf9936ab4cPI-LINK-be73a8a5cc435e823b139e8d3c5ea1e7f9cb1b1ePI-LINK-4ae85d2c1094844ccdcde9162790a6fb5a9793d2 <01bd01c20ab1$ece95900$c0cca8c0@promise.com.tw> <1023119309.3439.79.camel@irongate.swansea.linux.org.uk>

Dears.

    I saw the kernel patch 2.4.19pre10 and 2.4.19pre10ac2 release at
3.Jun.2002
The item 1 to 4 bugs still inside in 2.4.19pre10, Alan has fix some in his
tree.
Our latest driver patch is for kernel 2.4.18, you can reference the mail I
sent before.
Someone I don't know always modify our patch code and make things
complicated.

    Andre, only your name list in pdc202xx.c, So I think the problems should
be solved
by you. Could you fix all ASAP? If linux kernel wants our patch code, I
think they should
not modify our patch code and maintains by ourself.
Or do not make troubles for our company.


Thanks in advance
Hank Yang

----- Original Message -----
From: Alan Cox
To: Hank Yang
Cc: andre@linuxdiskcert.org ; marcelo@conectiva.com.br ;
torvalds@transmeta.com ; linux-kernel@vger.kernel.org ; arjanv@redhat.com ;
Linus Chen ; Crimson Hung ; Jenny Liang ; jordanr@promise.com
Sent: 2002年6月3日 下午 11:48
Subject: Re: [PATCH] 2.4.19pre9 in pdc202xx.c bug


On Mon, 2002-06-03 at 04:51, Hank Yang wrote:
>     There is something wrong in drivers/ide/pdc202xx.c ide driver.
> Andre Hedrick has merged ide stuff to 2.4.18 kernel that released for
> RedHat 7.3, SuSE 8.0 and Mandrake 8.2. That has a bug inside to
> harmful our company.

Item 4 is already done in my tree. As I said before the patch you sent
me a while back did not apply and appeared to be for an old 2.4.17/8
tree. I never got an update beyond that so I had assumed the problem had
already been resolved.

Andre - want to go over the rest and send me the bits ? Or Hank do you
want to send me a patch versus 2.4.19pre to fix those bugs

Alan


  reply	other threads:[~2002-06-06  2:30 UTC|newest]

Thread overview: 31+ 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
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 [this message]
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

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='004501c20d02$4ac734a0$c0cca8c0@promise.com.tw' \
    --to=hanky@promise.com.tw \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andre@serialata.org \
    --cc=arjanv@redhat.com \
    --cc=jordanr@promise.com \
    --cc=linusc@promise.com.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com \
    --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

all inboxes | Powered by JetHome®