From: Jakob Kemi <jakob.kemi@telia.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.17-pre4
Date: Wed, 5 Dec 2001 22:54:26 +0100 [thread overview]
Message-ID: <200112052155.fB5Ltxa26014@d1o849.telia.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0112051640570.20575-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0112051640570.20575-100000@freak.distro.conectiva>
On Wednesdayen den 5 December 2001 19.41, Marcelo Tosatti wrote:
> Duh. I forgot to add tcp_diag.c and tcp_diag.h in -pre3, which avoid it to
> compile correctly.
>
> Well, here goes -pre4 which fixes that.
>
> - Added missing tcp_diag.c and tcp_diag.h (me)
>
> -
> 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/
Hi Marcelo,
Since 2.4.14 the ieee1284 parport functions have worked improperly for some
drivers (CPiA, W9966 and others). Joe <joeja@mindspring.com> was quick to
find the failure. He said he was going to send the patch to you some week ago
and maybe he already have. If it somehow got lost in an internet black-hole
or something I try to also send it to you. It's just a one-liner which
reverts to pre-2.4.14 behavior.
--- ieee1284_ops.c.orig Tue Nov 6 11:29:26 2001
+++ ieee1284_ops.c Wed Dec 5 22:44:20 2001
@@ -592,7 +592,7 @@
}
/* Event 44: Set HostAck high, acknowledging handshake. */
- parport_write_control (port, ctl);
+ parport_frob_control (port, PARPORT_CONTROL_AUTOFD, 0);
/* Event 45: The peripheral has 35ms to set nAck high. */
if (parport_wait_peripheral (port, PARPORT_STATUS_ACK,
next prev parent reply other threads:[~2001-12-05 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 18:41 Marcelo Tosatti
2001-12-05 21:54 ` Jakob Kemi [this message]
2001-12-05 22:18 ` Tim Waugh
2001-12-06 0:22 ` Jakob Kemi
2001-12-06 7:27 ` Tim Waugh
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=200112052155.fB5Ltxa26014@d1o849.telia.com \
--to=jakob.kemi@telia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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®