public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@redhat.com>
To: andre@linux-ide.org (Andre Hedrick)
Cc: kasperd@daimi.au.dk (Kasper Dupont), alan@redhat.com (Alan Cox),
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19-rc1-ac5
Date: Tue, 16 Jul 2002 13:13:43 -0400 (EDT)	[thread overview]
Message-ID: <200207161713.g6GHDhw02197@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10207161003300.6509-100000@master.linux-ide.org> from "Andre Hedrick" at Jul 16, 2002 10:07:28 AM

> The problem is not introduced by the patches, is the the hardware
> decoupling the GPIO used for HOST side cable detection.  Worse is they
> reused the GPIO for something else.

So how come it worked before.

  reply	other threads:[~2002-07-16 17:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-15 21:48 Linux 2.4.19-rc1-ac5 Alan Cox
2002-07-15 22:10 ` Rudmer van Dijk
2002-07-15 23:14   ` H. Peter Anvin
2002-07-15 23:25     ` Robert Love
2002-07-16  0:28     ` Alan Cox
2002-07-15 23:21       ` H. Peter Anvin
2002-07-15 23:29         ` Robert Love
2002-07-15 23:47           ` H. Peter Anvin
2002-07-16  6:46             ` Rudmer van Dijk
2002-07-16  4:01 ` Linux 2.4.19-rc1-ac5 -- Build error in mpparse.c Miles Lane
2002-07-16  4:14   ` Brandon Low
2002-07-16  7:54   ` Linux 2.4.19-rc1-ac5 -- Build error in mpparse.c (possible fix) khromy
2002-07-16  8:07     ` khromy
2002-07-16 10:09     ` Alan Cox
2002-07-16 11:45 ` Linux 2.4.19-rc1-ac5 Kasper Dupont
2002-07-16 17:07   ` Andre Hedrick
2002-07-16 17:13     ` Alan Cox [this message]
2002-07-19 20:36       ` Linux 2.4.19-rc2-ac2 Ian Soboroff
2002-07-19 21:02         ` Philippe Gramoullé
2002-07-22 13:03           ` mbs
2002-07-17 17:11   ` Linux 2.4.19-rc1-ac5 Kasper Dupont
2002-07-28 23:06     ` Kasper Dupont
2002-07-29 12:00       ` Alan Cox
2002-07-29 13:58         ` Kasper Dupont

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=200207161713.g6GHDhw02197@devserv.devel.redhat.com \
    --to=alan@redhat.com \
    --cc=andre@linux-ide.org \
    --cc=kasperd@daimi.au.dk \
    --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