public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	alan@linux.intel.com, jirislaby@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/10] TTY: switch flipping functions to tty_port
Date: Wed, 16 Jan 2013 16:59:58 +0100	[thread overview]
Message-ID: <50F6CE7E.4090807@suse.cz> (raw)
In-Reply-To: <1358351064.4068.43.camel@gandalf.local.home>

On 01/16/2013 04:44 PM, Steven Rostedt wrote:
> On Wed, 2013-01-16 at 14:37 +0100, Jiri Slaby wrote:
>> Steven, do you have any plans with the driver? What is its planned destiny?
> 
> Well, I'm currently using the device in my main machine. As it is my
> main box, I don't update the kernel as often.
> 
> Let me know what I need to do to fix it in the current kernel.

Every port in the system has to have its struct tty_port counterpart.

/me looked into the code

OMG. It contains a true copy of serial_core!

In the beginning (to remove the BROKEN flag), what it needs is struct
tty_port to be added to struct sb_uart_info. It obviously needs
tty_port_init + tty_port_destroy at appropriate places. Then it needs
tty_register_device to be switched to tty_port_register_device.

Finally, having the tty_port, all tty flipping functions take the
tty_port, not tty_struct (the build errors reported). This is easy while
you have a tty_port.

In the long term, it needs to get rid of the all the pseudo-uart* stuff
(the copy of serial_core) and use only tty layer+tty_port helpers.

thanks,
-- 
js
suse labs

  reply	other threads:[~2013-01-16 17:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 14:53 [PATCH 00/10] TTY: switch flipping functions to tty_port Jiri Slaby
2013-01-03 14:53 ` [PATCH 01/10] TTY: switch tty_buffer_request_room " Jiri Slaby
2013-01-03 14:53 ` [PATCH 02/10] TTY: convert more flipping functions Jiri Slaby
2013-01-03 14:53 ` [PATCH 03/10] TTY: switch tty_insert_flip_char Jiri Slaby
2013-01-03 14:53 ` [PATCH 04/10] TTY: switch tty_insert_flip_string Jiri Slaby
2013-01-03 14:53 ` [PATCH 05/10] TTY: move low_latency to tty_port Jiri Slaby
2013-01-03 14:53 ` [PATCH 06/10] TTY: switch tty_flip_buffer_push Jiri Slaby
2013-01-03 14:53 ` [PATCH 07/10] TTY: switch tty_schedule_flip Jiri Slaby
2013-02-01 12:37   ` Peter Hurley
2013-02-01 15:06     ` Jiri Slaby
2013-02-01 20:39       ` Peter Hurley
2013-02-05 11:40         ` Jiri Slaby
2013-02-05 14:06           ` Peter Hurley
2013-01-03 14:53 ` [PATCH 08/10] cyclades: push down tty_port_tty_get Jiri Slaby
2013-01-03 14:53 ` [PATCH 09/10] TTY: synclink, remove unneeded tests Jiri Slaby
2013-01-03 14:53 ` [PATCH 10/10] TTY: nozomi, remove dead code Jiri Slaby
2013-01-16  6:47 ` [PATCH 00/10] TTY: switch flipping functions to tty_port Greg KH
2013-01-16 13:37   ` Jiri Slaby
2013-01-16 15:39     ` Greg KH
2013-01-16 15:48       ` Steven Rostedt
2013-01-16 15:44     ` Steven Rostedt
2013-01-16 15:59       ` Jiri Slaby [this message]
2013-01-16 16:23         ` Steven Rostedt
2013-01-16 16:42         ` Alan Cox
2013-01-16 16:49           ` Steven Rostedt
2013-01-19  4:52           ` Steven Rostedt

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=50F6CE7E.4090807@suse.cz \
    --to=jslaby@suse.cz \
    --cc=alan@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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