From: Alexander Shiyan <shc_work@mail.ru>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: linux-serial@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>
Subject: Re: [PATCH 0/3] serial: max310x: Add support for MAX3109 & MAX14830
Date: Fri, 26 Jul 2013 21:05:23 +0400 [thread overview]
Message-ID: <20130726210523.08bcb38b1589a67ba9bae6d1@mail.ru> (raw)
In-Reply-To: <1372483459-11836-1-git-send-email-shc_work@mail.ru>
On Sat, 29 Jun 2013 09:24:16 +0400
Alexander Shiyan <shc_work@mail.ru> wrote:
> This series adds support for dual (MAX3109) and quad (MAX14830) ICs
> into the max310x driver.
> There are lot of changes in the code, as we had to change almost every
> function to achieve the required functionality. Because of this
> the first part of the patch can not be divided into smaller parts.
> Result was checked for a long time:
> MAX3107 with SPI on Cirrus Logic EP7312,
> MAX14830 with SPI on Freescale i.MX51 (two ports simultaneously).
>
> Alexander Shiyan (3):
> serial: max310x: Driver rework
> serial: max310x: Add MAX3109 support
> serial: max310x: Add MAX14830 support
>
> drivers/tty/serial/Kconfig | 6 +-
> drivers/tty/serial/max310x.c | 996 ++++++++++++++++++----------------
> include/linux/platform_data/max310x.h | 9 +-
> 3 files changed, 531 insertions(+), 480 deletions(-)
>
> --
> 1.8.1.5
Ping.
--
Alexander Shiyan <shc_work@mail.ru>
prev parent reply other threads:[~2013-07-26 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 5:24 [PATCH 0/3] serial: max310x: Add support for MAX3109 & MAX14830 Alexander Shiyan
2013-06-29 5:24 ` [PATCH 1/3] serial: max310x: Driver rework Alexander Shiyan
2013-06-29 5:24 ` [PATCH 2/3] serial: max310x: Add MAX3109 support Alexander Shiyan
2013-06-29 5:24 ` [PATCH 3/3] serial: max310x: Add MAX14830 support Alexander Shiyan
2013-06-29 6:44 ` [PATCH 0/3] serial: max310x: Add support for MAX3109 & MAX14830 Alexander Shiyan
2013-07-26 17:05 ` Alexander Shiyan [this message]
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=20130726210523.08bcb38b1589a67ba9bae6d1@mail.ru \
--to=shc_work@mail.ru \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).