All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Theodore Ts'o <tytso@mit.edu>,
	Tharun Kumar P <tharunkumar.pasumarthi@microchip.com>,
	Kumaravel Thiagarajan <kumaravel.thiagarajan@microchip.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Jiri Slaby <jslaby@suse.cz>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [GIT PULL] TTY/Serial driver updates for 6.3-rc1
Date: Sun, 26 Feb 2023 07:50:01 +0100	[thread overview]
Message-ID: <Y/sBGesMZSd188OQ@kroah.com> (raw)
In-Reply-To: <CAHk-=wjPrei8BkaJ3wjGF_fTsehhQZVZppzqYrt76oc+oYXk8w@mail.gmail.com>

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@mit.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

  reply	other threads:[~2023-02-26  6:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24 12:51 [GIT PULL] TTY/Serial driver updates for 6.3-rc1 Greg KH
2023-02-24 21:15 ` pr-tracker-bot
2023-02-24 21:24 ` Linus Torvalds
2023-02-24 21:30   ` Linus Torvalds
2023-02-24 22:32     ` Al Viro
2023-02-24 22:57       ` Linus Torvalds
2023-02-25 23:40     ` Theodore Ts'o
2023-02-26  2:14       ` Linus Torvalds
2023-02-26  6:50         ` Greg KH [this message]
2023-02-27 19:54           ` Tharunkumar.Pasumarthi
2023-02-28  7:35             ` Greg KH
2023-02-26 19:58         ` Theodore Ts'o
2023-02-27 22:33           ` Andy Shevchenko
2023-02-27 22:47             ` Linus Torvalds

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=Y/sBGesMZSd188OQ@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jslaby@suse.cz \
    --cc=kumaravel.thiagarajan@microchip.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tharunkumar.pasumarthi@microchip.com \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.