All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Anatoly Pugachev <matorola@gmail.com>
Cc: Pat Gefre <pfg@sgi.com>, Christoph Hellwig <hch@lst.de>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	Joe Perches <joe@perches.com>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>,
	"Linux Kernel list" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] tty/serial: cleanup after ioc*_serial driver removal
Date: Tue, 18 Feb 2020 17:59:11 +0000	[thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F7F57B7D6@ORSMSX115.amr.corp.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2002170950390.11007@felia>

> I do not know if there are more ia64 serial drivers, but the MAINTAINERS 
> entry and commit message suggested there is not another serial driver.

Lukas,

There aren't any other ia64 specific serial drivers. But ia64 does use generic
serial drivers (e.g. my test machine has a couple of serial ports attached to 16550A
devices)

I think some notes in that documentation file still apply. Please don't delete.

-Tony

  parent reply	other threads:[~2020-02-18 17:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17  8:15 [PATCH] tty/serial: cleanup after ioc*_serial driver removal Lukas Bulwahn
2020-02-17  8:15 ` Lukas Bulwahn
2020-02-17  8:45 ` Anatoly Pugachev
2020-02-17  8:45   ` Anatoly Pugachev
2020-02-17  9:09   ` Lukas Bulwahn
2020-02-17  9:09     ` Lukas Bulwahn
2020-02-17 13:08     ` Christoph Hellwig
2020-02-17 13:08       ` Christoph Hellwig
2020-02-17 13:16       ` Lukas Bulwahn
2020-02-17 13:16         ` Lukas Bulwahn
2020-02-18 17:59     ` Luck, Tony [this message]
2020-02-18 20:14       ` Lukas Bulwahn
2020-02-18 20:14         ` Lukas Bulwahn

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=3908561D78D1C84285E8C5FCA982C28F7F57B7D6@ORSMSX115.amr.corp.intel.com \
    --to=tony.luck@intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=hch@lst.de \
    --cc=joe@perches.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=matorola@gmail.com \
    --cc=pfg@sgi.com \
    /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.