From: Arnd Bergmann <arnd@arndb.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Greg KH <gregkh@suse.de>,
Jiri Slaby <jslaby@suse.cz>,
linux-kernel@vger.kernel.org,
Mike Frysinger <vapier.adi@gmail.com>,
Roger Wolff <R.E.Wolff@bitwizard.nl>,
"Michael H. Warfield" <mhw@wittsend.com>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [RFC 0/5] tty: move stuff around
Date: Fri, 3 Sep 2010 14:01:39 +0200 [thread overview]
Message-ID: <201009031401.39224.arnd@arndb.de> (raw)
In-Reply-To: <AANLkTinUjfWqEdOQoomR=TZnQEsiGj1wxvbv5c_MtZKp@mail.gmail.com>
On Thursday 02 September 2010, Geert Uytterhoeven wrote:
> On Tue, Aug 31, 2010 at 11:26, Arnd Bergmann <arnd@arndb.de> wrote:
> - generic_serial-based:
>
> o MVME147_SCC
> o MVME162_SCC
> o BVME6000_SCC
> o A2232
>
> All of these were marked BROKEN lately due to generic_serial,
> while there's even a
> new ATARI_SCC under "active" development...
Ok, so I'll keep the plan of moving generic_serial to staging.
> - plain drivers/char:
>
> o SERIAL167
> o AMIGA_BUILTIN_SERIAL
Since these are the builtin ports for the Amiga and MVME16x
platforms, I suppose we should keep them around as long as the
platforms themselves are there and the code builds.
> - drivers/serial:
>
> o SERIAL_PMACZILOG (Mac)
>
> Sun 3/3x support might be (re)added to SERIAL_SUNZILOG
Same category I guess.
Thanks for your feedback!
Arnd
prev parent reply other threads:[~2010-09-03 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1283115995-4734-1-git-send-email-arnd@arndb.de>
[not found] ` <201008302333.22447.arnd@arndb.de>
[not found] ` <20100830232800.3cb768fc@lxorguk.ukuu.org.uk>
[not found] ` <201008311126.45190.arnd@arndb.de>
2010-09-02 20:12 ` [RFC 0/5] tty: move stuff around Geert Uytterhoeven
2010-09-03 12:01 ` Arnd Bergmann [this message]
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=201009031401.39224.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=R.E.Wolff@bitwizard.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=geert@linux-m68k.org \
--cc=gregkh@suse.de \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=mhw@wittsend.com \
--cc=vapier.adi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox