linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Matwey V. Kornilov" <matwey.kornilov@gmail.com>
To: Mathieu OTHACEHE <m.othacehe@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.com>,
	andriy.shevchenko@linux.intel.com, anton.wuerfel@fau.de,
	phillip.raffeck@fau.de, heikki.krogerus@linux.intel.com,
	Peter H <hpeter@gmail.com>,
	Soeren Grunewald <soeren.grunewald@desy.de>,
	Wang YanQing <udknight@gmail.com>,
	Jan Beulich <JBeulich@suse.com>,
	linux-serial@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] tty: serial: 8250: add MOXA Smartio MUE boards support
Date: Sat, 19 Mar 2016 12:13:39 +0300	[thread overview]
Message-ID: <CAJs94Eah9uXVMuXDb-Upd=v-ZTGkXivBD8c0Zbzg5UWDcU9r_g@mail.gmail.com> (raw)
In-Reply-To: <20160319090723.GA8678@gmail.com>

2016-03-19 12:07 GMT+03:00 Mathieu OTHACEHE <m.othacehe@gmail.com>:
> Hi,
>
> Sorry about late reply.
>
> No I haven't planned to do it soon. Your board is supported by mxser driver (drivers/tty/mxser.c).
> I think it would be nice to move everything from mxser.c to 8250_moxa.c.

Last time when I tried to run my moxa PCI board with 3.1(?) and mxser
it deadlocked my PC from time to time.
8250_moxa implementation is much more cleaner.

>
> The problem is mxser supports ISA and PCI boards and I don't have the hardware to test it.
>
> Mathieu



-- 
With best regards,
Matwey V. Kornilov
http://blog.matwey.name
xmpp://0x2207@jabber.ru

  reply	other threads:[~2016-03-19  9:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 19:10 [PATCH v3] tty: serial: 8250: add MOXA Smartio MUE boards support Mathieu OTHACEHE
2016-02-25 13:25 ` Andy Shevchenko
2016-03-14  9:36 ` Matwey V. Kornilov
2016-03-19  9:07   ` Mathieu OTHACEHE
2016-03-19  9:13     ` Matwey V. Kornilov [this message]
2017-01-14 18:38     ` Matwey V. Kornilov

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='CAJs94Eah9uXVMuXDb-Upd=v-ZTGkXivBD8c0Zbzg5UWDcU9r_g@mail.gmail.com' \
    --to=matwey.kornilov@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=anton.wuerfel@fau.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=hpeter@gmail.com \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=m.othacehe@gmail.com \
    --cc=phillip.raffeck@fau.de \
    --cc=soeren.grunewald@desy.de \
    --cc=udknight@gmail.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;
as well as URLs for NNTP newsgroup(s).