linux-kernel - Re: [PATCH v1 01/31] tty: mxser: serial: 8250: replace mxser with 8250-based driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHp75VdsM4d61wRstO_6FAPno+t+yAmYJ-MqikOdqawrVTDyfA@mail.gmail.com>
Date: Sun, 30 Nov 2025 19:07:01 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Crescent Hsieh <crescentcy.hsieh@...a.com>
Cc: gregkh@...uxfoundation.org, jirislaby@...nel.org, 
	ilpo.jarvinen@...ux.intel.com, linux-kernel@...r.kernel.org, 
	linux-serial@...r.kernel.org
Subject: Re: [PATCH v1 01/31] tty: mxser: serial: 8250: replace mxser with
 8250-based driver

On Sun, Nov 30, 2025 at 12:43 PM Crescent Hsieh
<crescentcy.hsieh@...a.com> wrote:
>
> Remove the legacy mxser driver and replace it with 8250-based
> implementation (8250_mxupci) for Moxa UPCI serial devices.
>
> This simplifies maintenance and improves integration with the existing
> 8250 serial infrastructure.

One obvious question (that I found no clear answer to in the commit
message): Does it mean all functionality is kept the same? (I think I
know the answer and this has to be summarised in the commit message.)
And one potential issue with the change: Please, instead of removing
the old option, use transition Kconfig to make sure users will get the
driver compiled when moving from old kernel configurations to a new
one. However, see above. it might be more tricky to achieve a smooth
transition at the end.

-- 
With Best Regards,
Andy Shevchenko