From: James Hogan <james.hogan@imgtec.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jslaby@suse.cz>, <linux-kernel@vger.kernel.org>,
James Hogan <james.hogan@imgtec.com>
Subject: [PATCH 0/2] tty: metag_da: Add metag DA TTY driver
Date: Wed, 6 Feb 2013 14:45:00 +0000 [thread overview]
Message-ID: <1360161902-25329-1-git-send-email-james.hogan@imgtec.com> (raw)
Greg: is it okay to take this into your tty tree as it depends on Jiri's
tty_flip/tty_port changes? It won't get built until the arch/metag tree
comes along and defines the METAG_DA Kconfig symbol.
This is the same metag_da driver as before, but rebased on tty-next and
omitting all arch/metag bits. Both parts have already been reviewed (and
I squashed the buffer flipping change into the first patch).
Sorry for all the resends by the way. I think I should have just aimed
for the tty tree in the first place :-) I'll know for future.
James Hogan (2):
tty: metag_da: Add metag DA TTY driver
tty: metag_da: avoid getting tty kref in dashtty_timer()
drivers/tty/Kconfig | 13 +
drivers/tty/Makefile | 1 +
drivers/tty/metag_da.c | 677 ++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 691 insertions(+), 0 deletions(-)
create mode 100644 drivers/tty/metag_da.c
--
1.7.7.6
next reply other threads:[~2013-02-06 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 14:45 James Hogan [this message]
2013-02-06 14:45 ` [PATCH 1/2] tty: metag_da: Add metag DA TTY driver James Hogan
2013-02-06 14:45 ` [PATCH 2/2] tty: metag_da: avoid getting tty kref in dashtty_timer() James Hogan
2013-02-06 17:49 ` [PATCH 0/2] tty: metag_da: Add metag DA TTY driver Greg Kroah-Hartman
2013-02-06 17:50 ` Greg Kroah-Hartman
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=1360161902-25329-1-git-send-email-james.hogan@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--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