public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel•org>
To: Greg KH <gregkh@linuxfoundation•org>
Cc: linux-serial@vger•kernel.org, linux-kernel@vger•kernel.org,
	"Alex Elder" <elder@kernel•org>,
	"Andrew Lunn" <andrew+netdev@lunn•ch>,
	"Andy Shevchenko" <andriy.shevchenko@linux•intel.com>,
	"David Lin" <dtwlin@gmail•com>,
	"David S. Miller" <davem@davemloft•net>,
	"Eric Dumazet" <edumazet@google•com>,
	greybus-dev@lists•linaro.org,
	"Ilpo Järvinen" <ilpo.jarvinen@linux•intel.com>,
	"Jakub Kicinski" <kuba@kernel•org>,
	"Johan Hovold" <johan@kernel•org>,
	linux-alpha@vger•kernel.org, linux-staging@lists•linux.dev,
	"Matt Turner" <mattst88@gmail•com>,
	netdev@vger•kernel.org, "Paolo Abeni" <pabeni@redhat•com>,
	"Richard Henderson" <richard.henderson@linaro•org>,
	"Rob Herring" <robh@kernel•org>,
	sparclinux@vger•kernel.org
Subject: Re: [PATCH 00/29] tty: cleanup no. 99
Date: Mon, 17 Mar 2025 05:59:01 +0100	[thread overview]
Message-ID: <e8fb71ea-84cb-427a-9dc9-9c44ec0db08f@kernel.org> (raw)
In-Reply-To: <2025031738-fabric-alright-6a32@gregkh>

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

  reply	other threads:[~2025-03-17  4:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 11:15 [PATCH 00/29] tty: cleanup no. 99 Jiri Slaby (SUSE)
2025-02-20 11:15 ` [PATCH 03/29] tty: caif: do not use N_TTY_BUF_SIZE Jiri Slaby (SUSE)
2025-02-20 14:27   ` Jakub Kicinski
2025-03-17  4:28 ` [PATCH 00/29] tty: cleanup no. 99 Greg KH
2025-03-17  4:59   ` Jiri Slaby [this message]
2025-03-17  7:00     ` Greg KH

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=e8fb71ea-84cb-427a-9dc9-9c44ec0db08f@kernel.org \
    --to=jirislaby@kernel$(echo .)org \
    --cc=andrew+netdev@lunn$(echo .)ch \
    --cc=andriy.shevchenko@linux$(echo .)intel.com \
    --cc=davem@davemloft$(echo .)net \
    --cc=dtwlin@gmail$(echo .)com \
    --cc=edumazet@google$(echo .)com \
    --cc=elder@kernel$(echo .)org \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=greybus-dev@lists$(echo .)linaro.org \
    --cc=ilpo.jarvinen@linux$(echo .)intel.com \
    --cc=johan@kernel$(echo .)org \
    --cc=kuba@kernel$(echo .)org \
    --cc=linux-alpha@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-serial@vger$(echo .)kernel.org \
    --cc=linux-staging@lists$(echo .)linux.dev \
    --cc=mattst88@gmail$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=richard.henderson@linaro$(echo .)org \
    --cc=robh@kernel$(echo .)org \
    --cc=sparclinux@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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