From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: vme_scc.c breakage (was: Re: linux-next: Tree for November 21)
Date: Sat, 22 Nov 2008 16:07:46 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0811221558340.30025@anakin> (raw)
In-Reply-To: <20081121181948.ee771502.sfr@canb.auug.org.au>
Hi Alan,
drivers/char/vme_scc.c no longer compiles in linux-next:
http://kisskb.ellerman.id.au/kisskb/buildresult/56964/
I get a slightly different error message, though:
| drivers/char/vme_scc.c: In function 'scc_carrier_raised':
| drivers/char/vme_scc.c:634: error: expected identifier or '(' before 'volatile'
| drivers/char/vme_scc.c:634: error: expected ')' before '(' token
| drivers/char/vme_scc.c:634: error: expected statement before ')' token
| drivers/char/vme_scc.c:635: error: 'struct tty_port' has no member named 'channel'
The problem seems to be introduced by commit
e21405cbbaa859c68119b260c0fe43afdb86a385 ("tty-port-extract-cd"). The relevant
part is below:
| diff --git a/drivers/char/vme_scc.c b/drivers/char/vme_scc.c
| index 1718b3c..d4e1534 100644
| --- a/drivers/char/vme_scc.c
| +++ b/drivers/char/vme_scc.c
| @@ -624,9 +629,9 @@ static void scc_enable_rx_interrupts(void *ptr)
| }
|
|
| -static int scc_get_CD(void *ptr)
| +static int scc_carrier_raised(struct tty_port *port)
| {
| - struct scc_port *port = ptr;
| + struct scc_port *scc = container_of(port, struct scc_port, gs.port);
| unsigned channel = port->channel;
|
| return !!(scc_last_status_reg[channel] & SR_DCD);
Issues:
1. When Atari support is enabled, `scc' is defined in
include/asm-m68k/atari.h as:
# define scc ((*(volatile struct SCC*)SCC_BAS))
However, renaming the variable `scc' doesn't help, as
2. the variable `scc' is not used in scc_carrier_raised(),
3. `port->channel' on line 635 still fails as `port' is not longer `struct
scc_port', but a 'struct tty_port', which has no member named 'channel'.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2008-11-22 15:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 7:19 linux-next: Tree for November 21 Stephen Rothwell
2008-11-21 20:02 ` [PATCH linux-next] snd-hda: fix build errors Randy Dunlap
2008-11-21 20:27 ` Takashi Iwai
2008-11-21 20:42 ` Randy Dunlap
2008-11-22 9:48 ` Takashi Iwai
2008-11-22 1:39 ` Wu Fengguang
2008-11-22 15:07 ` Geert Uytterhoeven [this message]
2008-11-22 16:47 ` vme_scc.c breakage (was: Re: linux-next: Tree for November 21) Alan Cox
2008-11-23 2:29 ` Michael Schmitz
2008-11-23 2:59 ` Brad Boyer
2008-11-23 4:40 ` Michael Schmitz
2008-11-23 9:22 ` Brad Boyer
2008-11-24 1:55 ` Michael Schmitz
2008-11-24 6:08 ` Brad Boyer
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=Pine.LNX.4.64.0811221558340.30025@anakin \
--to=geert@linux-m68k.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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