[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e8fb71ea-84cb-427a-9dc9-9c44ec0db08f@kernel.org>
Date: Mon, 17 Mar 2025 05:59:01 +0100
From: Jiri Slaby <jirislaby@...nel.org>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org,
Alex Elder <elder@...nel.org>, Andrew Lunn <andrew+netdev@...n.ch>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
David Lin <dtwlin@...il.com>, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, greybus-dev@...ts.linaro.org,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
Jakub Kicinski <kuba@...nel.org>, Johan Hovold <johan@...nel.org>,
linux-alpha@...r.kernel.org, linux-staging@...ts.linux.dev,
Matt Turner <mattst88@...il.com>, netdev@...r.kernel.org,
Paolo Abeni <pabeni@...hat.com>,
Richard Henderson <richard.henderson@...aro.org>,
Rob Herring <robh@...nel.org>, sparclinux@...r.kernel.org
Subject: Re: [PATCH 00/29] tty: cleanup no. 99
On 17. 03. 25, 5:28, Greg KH wrote:
> On Thu, Feb 20, 2025 at 12:15:37PM +0100, Jiri Slaby (SUSE) wrote:
>> Hi,
>>
>> this is (again) a series of cleanup in tty. I am trying to rework
>> tty+serial to avoid limitations of devices (so called NR_UART or
>> tty_alloc_driver()'s first parameter). And the below popped up while
>> crawling through the code. So this is only a prep cleanup.
>>
>> * many tty flags are now enums
>> * many functions were improved for readability
>> * quite a few unused or old code dropped
>>
>> In particular, the runtime behaviour of the kernel before and after the
>> changes is supposed to be bug to bug compatible (except moxa's ioctl
>> and ISA evils dropped). That is, noone should notice.
>
> Were you going to do a new respin of this, or do you want me to take
> this as-is and you will send a follow-up ones for the commented-on
> changes?
I planned to send a v2 on Fri, but did not make it. I will today.
thanks,
--
js
suse labs
Powered by blists - more mailing lists