From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: linux-kernel list <linux-kernel@vger.kernel.org>
Subject: 2.6.9-rc3 compile erros
Date: Sat, 02 Oct 2004 18:48:52 +1000 [thread overview]
Message-ID: <415E6B74.5050100@eyal.emu.id.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 289 bytes --]
I need DVB so I finaly made the move to 2.6[.9-rc3]. I get compile failures in two modules:
drivers/isdn/i4l/isdn_tty.c
drivers/net/wan/pc300_tty.c
Both look like careless typos - is 2,6 really stable by now?
--
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.org/eyal/>
[-- Attachment #2: 2.6.9-rc3.isdn_tty.patch --]
[-- Type: text/x-patch, Size: 466 bytes --]
--- linux/drivers/isdn/i4l/isdn_tty.c.orig 2004-10-02 01:05:10.000000000 +1000
+++ linux/drivers/isdn/i4l/isdn_tty.c 2004-10-02 01:05:27.000000000 +1000
@@ -2673,7 +2673,7 @@
if ((info->flags & ISDN_ASYNC_CLOSING) || (!info->tty)) {
return;
}
- tty_ldisc_flush(tty);
+ tty_ldisc_flush(info->tty);
if ((info->flags & ISDN_ASYNC_CHECK_CD) &&
(!((info->flags & ISDN_ASYNC_CALLOUT_ACTIVE) &&
(info->flags & ISDN_ASYNC_CALLOUT_NOHUP)))) {
[-- Attachment #3: 2.6.9-rc3.pc300_tty.patch --]
[-- Type: text/x-patch, Size: 450 bytes --]
--- linux/drivers/net/wan/pc300_tty.c.orig 2004-10-02 01:13:01.000000000 +1000
+++ linux/drivers/net/wan/pc300_tty.c 2004-10-02 01:13:41.000000000 +1000
@@ -704,7 +704,7 @@
ld = tty_ldisc_ref(cpc_tty);
if(ld)
{
- if (ld->receive_buf)) {
+ if (ld->receive_buf) {
CPC_TTY_DBG("%s: call line disc. receive_buf\n",cpc_tty->name);
ld->receive_buf(cpc_tty->tty, (char *)(buf->data), &flags, buf->size);
}
next reply other threads:[~2004-10-02 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-02 8:48 Eyal Lebedinsky [this message]
2004-10-02 17:24 ` 2.6.9-rc3 compile erros 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=415E6B74.5050100@eyal.emu.id.au \
--to=eyal@eyal.emu.id.au \
--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