From: rogerx@sdf.org
To: linux-serial@vger.kernel.org
Subject: Re: 'struct uart_port' has no member named 'info
Date: Wed, 10 Mar 2010 15:49:32 -0900 [thread overview]
Message-ID: <20100311004932.GD7377@localhost2.local> (raw)
In-Reply-To: <20100310113347.GA8342@localhost2.local>
On Wed, Mar 10, 2010 at 02:33:47AM -0900, rogerx@sdf.org wrote:
>Upgraded from kernel-2.6.32 to kernel-2.6.33, and now get the following
>error when compiling ltmodem.
>
>/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'
Sorry. These changes were already found and patched for kernel-2.6.32!
I just happened to spend the last 12 hours finding all the new variable
names and writing a new patch -- while the patch was already written.
:-/
For reference for those doing a Google search:
- struct tty_struct *tty = up->port.info->port.tty;
+ struct tty_struct *tty = up->port.state->port.tty
- struct circ_buf *xmit = &up->port.info->xmit;
+ struct circ_buf *xmit = &up->port.state->xmit;
- wake_up_interruptible(&up->port.info->delta_msr_wait);
+ wake_up_interruptible(&up->port.state->port.delta_msr_wait)
--
Roger
http://rogerx.freeshell.org/
next prev parent reply other threads:[~2010-03-11 0:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 11:33 'struct uart_port' has no member named 'info rogerx
2010-03-11 0:49 ` rogerx [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-10 10:34 rogerx
2010-03-11 3:10 ` Xiaotian Feng
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=20100311004932.GD7377@localhost2.local \
--to=rogerx@sdf.org \
--cc=linux-serial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.