lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 10 Mar 2010 01:34:09 -0900
From:	rogerx@....org
To:	linux-kernel@...r.kernel.org
Subject: 'struct uart_port' has no member named 'info

Upgraded from kernel-2.6.32 to kernel-2.6.33, and now get the following
error when compiling ltmodem.

I checked for changes within drivers/serial/serial_core.c, but couldn't
find the specific change.  (I did verify ltmodem compiles fine without
error under 2.6.32.)


/var/tmp/portage/net-dialup/ltmodem-20090420/work/ltmodem/v8250.c: In
function 'receive_chars':
/var/tmp/portage/net-dialup/ltmodem-20090420/work/ltmodem/v8250.c:181:
error: 'struct uart_port' has no member named 'info'
/var/tmp/portage/net-dialup/ltmodem-20090420/work/ltmodem/v8250.c: In
function 'transmit_chars':
/var/tmp/portage/net-dialup/ltmodem-20090420/work/ltmodem/v8250.c:243:
error: 'struct uart_port' has no member named 'info'
/var/tmp/portage/net-dialup/ltmodem-20090420/work/ltmodem/v8250.c: In
function 'check_modem_status':
/var/tmp/portage/net-dialup/ltmodem-20090420/work/ltmodem/v8250.c:284:
error: 'struct uart_port' has no member named 'info'
/var/tmp/portage/net-dialup/ltmodem-20090420/work/ltmodem/v8250.c:294:
error: 'struct uart_port' has no member named 'info'
make[2]: ***
[/var/tmp/portage/net-dialup/ltmodem-20090420/work/ltmodem/v8250.o]
Error 1


-- 
Roger
http://rogerx.freeshell.org/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists