From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
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: Sat, 25 Feb 2023 18:40:12 -0500 [thread overview]
Message-ID: <Y/qcXOxTVHTNDQbY@mit.edu> (raw)
In-Reply-To: <CAHk-=wjyFhdR-M7H6JpH7zF0k_z5xj8+qERaHsh5+0c4uOmv+g@mail.gmail.com>
On Fri, Feb 24, 2023 at 01:30:58PM -0800, Linus Torvalds wrote:
>
> It's probably most legacy by now - it's a long time since I saw a
> serial port being used outside of management ports, and even those are
> often ethernet these days.
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....
- Ted
next prev parent reply other threads:[~2023-02-25 23:40 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 [this message]
2023-02-26 2:14 ` Linus Torvalds
2023-02-26 6:50 ` Greg KH
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/qcXOxTVHTNDQbY@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--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 \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).