From: Tim Waugh <twaugh@redhat.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Uhhuh.. 2.4.12
Date: Thu, 11 Oct 2001 09:41:18 +0100 [thread overview]
Message-ID: <20011011094118.M10562@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0110110058550.1198-100000@penguin.transmeta.com> <9q3lbs$16o$1@penguin.transmeta.com>
In-Reply-To: <9q3lbs$16o$1@penguin.transmeta.com>; from torvalds@transmeta.com on Thu, Oct 11, 2001 at 08:30:52AM +0000
On Thu, Oct 11, 2001 at 08:30:52AM +0000, Linus Torvalds wrote:
> In article <Pine.LNX.4.33.0110110058550.1198-100000@penguin.transmeta.com>,
> Linus Torvalds <torvalds@transmeta.com> wrote:
> >
> >So I made a 2.4.12, and renamed away the sorry excuse for a kernel that
> >2.4.11 was.
> >
> > - Tim Waugh: parport update
>
> .. which is broken.
>
> Not a good week.
Here is the fix:
--- linux/drivers/parport/ieee1284_ops.c.orig Thu Oct 11 09:40:39 2001
+++ linux/drivers/parport/ieee1284_ops.c Thu Oct 11 09:40:42 2001
@@ -362,7 +362,7 @@
} else {
DPRINTK (KERN_DEBUG "%s: ECP direction: failed to reverse\n",
port->name);
- port->ieee1284.phase = IEEE1284_PH_DIR_UNKNOWN;
+ port->ieee1284.phase = IEEE1284_PH_ECP_DIR_UNKNOWN;
}
return retval;
@@ -394,7 +394,7 @@
DPRINTK (KERN_DEBUG
"%s: ECP direction: failed to switch forward\n",
port->name);
- port->ieee1284.phase = IEEE1284_PH_DIR_UNKNOWN;
+ port->ieee1284.phase = IEEE1284_PH_ECP_DIR_UNKNOWN;
}
Sorry guys. *blush*
Tim.
*/
next prev parent reply other threads:[~2001-10-11 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 8:04 Linus Torvalds
2001-10-11 8:30 ` Linus Torvalds
2001-10-11 8:41 ` Tim Waugh [this message]
2001-10-11 8:59 ` J . A . Magallon
2001-10-11 10:14 ` T. A.
2001-10-11 8:42 ` Stefan Smietanowski
2001-10-11 8:50 ` Tim Waugh
2001-10-11 8:51 ` Stefan Smietanowski
2001-10-11 11:35 ` Marco Colombo
2001-10-11 11:54 ` 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=20011011094118.M10562@redhat.com \
--to=twaugh@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
all inboxes | Powered by JetHome®