[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y/sBGesMZSd188OQ@kroah.com>
Date: Sun, 26 Feb 2023 07:50:01 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Theodore Ts'o <tytso@....edu>,
Tharun Kumar P <tharunkumar.pasumarthi@...rochip.com>,
Kumaravel Thiagarajan <kumaravel.thiagarajan@...rochip.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Jiri Slaby <jslaby@...e.cz>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org
Subject: Re: [GIT PULL] TTY/Serial driver updates for 6.3-rc1
On Sat, Feb 25, 2023 at 06:14:11PM -0800, Linus Torvalds wrote:
> On Sat, Feb 25, 2023 at 3:40 PM Theodore Ts'o <tytso@....edu> wrote:
> >
> > For what it's worth, in the VM world (e.g., qemu, AWS, GCP, Azure,
> > Linode, etc.) serial consoles are quite common way of debugging VM's,
> > and as an emergency login path when the networking has been screwed up
> > for some reason....
>
> Everybody seems to be missing the point.
>
> We don't make new drivers "default y" (or, in this case, "default SERIAL_8250".
>
> It does not matter ONE WHIT if you have a serial device in your
> machine. If your old driver was enabled and worked for you and you
> used it daily, that is ENTIRELY IMMATERIAL to a new driver, even if
> that new driver then happens to use some of the same infrastructure as
> the old one did.
I agree, sorry for the delay, I'll fix this up before -final for this
release.
thanks,
greg k-h
Powered by blists - more mailing lists