From: Jiri Slaby <jirislaby@kernel.org>
To: Crescent Hsieh <crescentcy.hsieh@moxa.com>
Cc: "Ethan Nelson-Moore" <enelsonmoore@gmail.com>,
linux-serial@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Ray Chen (陳松昱)" <Ray.Chen@moxa.com>,
linux-m68k@lists.linux-m68k.org,
"Geert Uytterhoeven" <geert@linux-m68k.org>
Subject: Re: [PATCH 1/3] tty: move remaining serial drivers into the serial/ directory
Date: Mon, 3 Aug 2026 08:06:03 +0200 [thread overview]
Message-ID: <2da84e36-7ac6-407d-8e08-edca82f4cbce@kernel.org> (raw)
In-Reply-To: <afqyY8FQ8ZfpH48_@moxa-ThinkCentre-M90t>
On 06. 05. 26, 5:15, Crescent Hsieh wrote:
>> I am not sure even about users of Moxa Intellio. I think I prompted long
>> time ago. Oh yes, Ray Chen (CCed) from Moxa wrote me back in 2021:
>> === 8< ===
>> For the Intellio cards, we phased them out in 2017.
>> You may find the discontinuance notification as attached.
>> We will keep the software support for 5 years, to 2023.
>> === 8< ===
>>
>> I believe we can mark it as BROKEN to let someone convert it to serial_core.
>> Or drop it for good already.
>
> As for Moxa Intellio (moxa.c), I have confirmed internally that both the
> hardware and software support have already been phased out.
>
> Therefore, it would be reasonable to drop it at this point. I can help
> with preparing a removal patch if this is the preferred direction.
Let me revive this one.
I think we should proceed -- so could you remove the intellio driver,
please?
thanks,
--
js
suse labs
prev parent reply other threads:[~2026-08-03 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1777943090.git.enelsonmoore@gmail.com>
[not found] ` <042d993686c87fdfd4130f11b57c3b559944603d.1777943090.git.enelsonmoore@gmail.com>
2026-05-05 5:59 ` [PATCH 1/3] tty: move remaining serial drivers into the serial/ directory Jiri Slaby
2026-05-06 3:15 ` Crescent Hsieh
2026-08-03 6:06 ` Jiri Slaby [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=2da84e36-7ac6-407d-8e08-edca82f4cbce@kernel.org \
--to=jirislaby@kernel.org \
--cc=Ray.Chen@moxa.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=crescentcy.hsieh@moxa.com \
--cc=enelsonmoore@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-m68k@lists.linux-m68k.org \
--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