From: Mathieu OTHACEHE <m.othacehe@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Kalle Valo <kvalo@codeaurora.org>, Joe Perches <joe@perches.com>,
gnomes@lxorguk.ukuu.org.uk,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tty: add Moxa Smartio MUE serial driver
Date: Tue, 9 Feb 2016 13:10:00 +0100 [thread overview]
Message-ID: <20160209121000.GA3136@gmail.com> (raw)
In-Reply-To: <CAHp75VevkaVnuJP4=Jc7Sq7RmX=x7BGfqRL+VY9+13wjG0JxPg@mail.gmail.com>
> I'm sorry, but it looks like 8250 based driver if I'm not mistaken. In
> which case why not to use 8250_core.c / 8250_port.c and entire 8250/
> infrastructure?
Well, the vendor is providing two drivers for his serial pci cards : mxser and mxupcie.
The mxser driver has been cleaned up and integrated to mainline a long time ago (drivers/tty/mxser.c).
I'm trying to do the same thing with the mxupcie driver.
mxser and mxupcie are quite similar, maybe both should use 8250 infrastructure and not
have independant drivers ?
Mathieu
next prev parent reply other threads:[~2016-02-09 12:10 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
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 [this message]
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=20160209121000.GA3136@gmail.com \
--to=m.othacehe@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=davem@davemloft.net \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=jslaby@suse.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.