From: Greg KH <gregkh@linuxfoundation.org>
To: Mathieu OTHACEHE <m.othacehe@gmail.com>
Cc: jslaby@suse.com, akpm@linux-foundation.org, davem@davemloft.net,
mchehab@osg.samsung.com, kvalo@codeaurora.org, joe@perches.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: add Moxa Smartio MUE serial driver
Date: Mon, 1 Feb 2016 12:59:24 -0800 [thread overview]
Message-ID: <20160201205924.GA5210@kroah.com> (raw)
In-Reply-To: <1454358859-5534-1-git-send-email-m.othacehe@gmail.com>
On Mon, Feb 01, 2016 at 09:34:19PM +0100, Mathieu OTHACEHE wrote:
> Add a driver which supports:
>
> - CP-102E: 2 ports RS232 PCIE card
> - CP-102EL: 2 ports RS232 PCIE card
> - CP-132EL: 2 ports RS422/485 PCIE card
> - CP-114EL: 4 ports RS232/422/485 PCIE card
> - CP-104EL-A: 4 ports RS232 PCIE card
> - CP-168EL-A: 8 ports RS232 PCIE card
> - CP-118EL-A: 8 ports RS232/422/485 PCIE card
> - CP-118E-A: 8 ports RS422/485 PCIE card
> - CP-138E-A: 8 ports RS422/485 PCIE card
> - CP-134EL-A: 4 ports RS422/485 PCIE card
> - CP-116E-A (A): 8 ports RS232/422/485 PCIE card
> - CP-116E-A (B): 8 ports RS232/422/485 PCIE card
>
> This driver is based on 1.16.7 GPL MOXA driver written by Eric Lo
> and available on MOXA website. The original driver was based on
> Linux serial driver.
>
> Signed-off-by: Mathieu OTHACEHE <m.othacehe@gmail.com>
> ---
>
> Hi,
>
> Here is a new driver for MOXA Smartio MUE cards. It is based
> on the vendor driver available on MOXA website and on the
> mainline mxser driver.
>
> I was able to test it on a CP-168EL-A card on PC. Some of the
> cards (118E-A, 138E-A, 134EL-A, 116E-A-A et 116E-A-B) have
> a CPLD module programmable via GPIO.
> For now, I dropped all the code related to CPLD/GPIO because I
> can't test it on my card.
>
> Mathieu
>
> MAINTAINERS | 5 +
> drivers/tty/Kconfig | 10 +
> drivers/tty/Makefile | 1 +
> drivers/tty/mxupcie.c | 1874 +++++++++++++++++++++++++++++++++++++++++++++++++
> drivers/tty/mxupcie.h | 129 ++++
Minor nit, but why do you need a .h file here when no one else includes
it? Why not just put it into the .c file to keep things nice and
self-contained?
thanks,
greg k-h
next prev parent reply other threads:[~2016-02-01 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 20:34 [PATCH] tty: add Moxa Smartio MUE serial driver Mathieu OTHACEHE
2016-02-01 20:59 ` Greg KH [this message]
2016-02-01 21:13 ` One Thousand Gnomes
2016-02-03 18:50 ` Mathieu OTHACEHE
2016-02-07 8:32 ` kbuild test robot
2016-02-08 16:18 ` Andy Shevchenko
2016-02-09 12:10 ` Mathieu OTHACEHE
2016-02-10 6:32 ` Andy Shevchenko
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=20160201205924.GA5210@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=jslaby@suse.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.othacehe@gmail.com \
--cc=mchehab@osg.samsung.com \
/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