From: Jiri Slaby <jslaby@suse.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Arnd Bergmann <arnd@arndb.de>, Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 0/5] tty: move stuff around
Date: Tue, 31 Aug 2010 11:19:08 +0200 [thread overview]
Message-ID: <4C7CC90C.2030100@suse.cz> (raw)
In-Reply-To: <20100831103336.42e5f114@lxorguk.ukuu.org.uk>
On 08/31/2010 11:33 AM, Alan Cox wrote:
> On Tue, 31 Aug 2010 08:08:57 +0200
> Jiri Slaby <jslaby@suse.cz> wrote:
>
>> On 08/31/2010 12:28 AM, Alan Cox wrote:
>>>> riscom,isicom -> drivers/staging/tty/*
>>>
>>> isicom has users and gets tested a bit
>>
>> Are you sure about isicom:
>
> There certainly were people using it, which suggests maybe it needs
> looking at not binning.
Ok, thanks. Anyway I'll remove myself as a maintainer, since I'm not
anymore.
--
js
suse labs
next prev parent reply other threads:[~2010-08-31 9:19 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-29 21:06 [RFC 0/5] tty: move stuff around Arnd Bergmann
2010-08-29 21:06 ` [PATCH 1/5] tty: move tty layer code to drivers/tty Arnd Bergmann
2010-08-29 21:06 ` [PATCH 2/5] tty/vt: move files to drivers/tty/vt/ Arnd Bergmann
2010-08-29 21:06 ` [PATCH 3/5] tty/hvc: move files to drivers/tty/hvc Arnd Bergmann
2010-08-29 21:06 ` [PATCH 4/5] tty/hw: move hardware drivers to drivers/tty/hw Arnd Bergmann
2010-08-29 21:51 ` Mike Frysinger
2010-08-30 8:55 ` Arnd Bergmann
2010-08-30 10:54 ` Alan Cox
2010-08-30 12:28 ` Arnd Bergmann
2010-08-30 14:56 ` Mike Frysinger
2010-08-30 15:25 ` Arnd Bergmann
2010-08-30 15:26 ` Mike Frysinger
2010-08-29 21:06 ` [PATCH 5/5] tty: rearrange Kconfig structure Arnd Bergmann
2010-08-29 23:18 ` [RFC 0/5] tty: move stuff around Alan Cox
2010-08-30 11:37 ` Arnd Bergmann
2010-08-30 11:55 ` Jiri Slaby
2010-08-30 12:15 ` Arnd Bergmann
2010-08-30 13:00 ` Alan Cox
2010-08-30 21:04 ` Arnd Bergmann
2010-08-30 18:47 ` Greg KH
2010-08-30 21:33 ` Arnd Bergmann
2010-08-30 21:38 ` Jiri Slaby
2010-08-30 22:28 ` Alan Cox
2010-08-31 6:08 ` Jiri Slaby
2010-08-31 9:33 ` Alan Cox
2010-08-31 9:19 ` Jiri Slaby [this message]
2010-08-31 9:19 ` [PATCH 1/1] MAINTAINERS: remove isicom Jiri Slaby
2010-08-31 15:03 ` Joe Perches
2010-08-31 15:08 ` [PATCH 1/1] MAINTAINERS: orphan isicom Jiri Slaby
2010-08-31 9:26 ` [RFC 0/5] tty: move stuff around Arnd Bergmann
2010-08-31 10:42 ` Rogier Wolff
2010-08-31 11:23 ` Alan Cox
2010-08-31 11:54 ` Arnd Bergmann
2010-08-31 13:32 ` Greg KH
2010-09-02 15:16 ` Michael H. Warfield
2010-09-03 12:13 ` Arnd Bergmann
2010-09-03 12:58 ` Gene Heskett
2010-09-03 13:34 ` Arnd Bergmann
2010-08-31 15:53 ` Mike Frysinger
2010-09-02 20:12 ` Geert Uytterhoeven
2010-09-03 12:01 ` Arnd Bergmann
2010-08-31 4:11 ` Greg KH
2010-09-03 15:29 ` Arnd Bergmann
2010-09-03 16:55 ` Greg KH
2010-09-03 17:42 ` Arnd Bergmann
2010-09-03 22:46 ` Greg KH
2010-09-03 20:08 ` Geert Uytterhoeven
2010-09-03 20:32 ` Alan Cox
2010-09-03 20:23 ` Geert Uytterhoeven
2010-09-21 23:07 ` Greg KH
2010-09-21 23:08 ` [PATCH 1/2] TTY: create /tty and move the tty core files there Greg KH
2010-09-21 23:08 ` [PATCH 2/2] TTY: create tty/vt and move the vt code there Greg KH
2010-09-22 9:10 ` Arnd Bergmann
2010-09-22 9:13 ` [PATCH 1/2] TTY: create /tty and move the tty core files there Arnd Bergmann
2011-02-23 1:12 ` [RFC 0/5] tty: move stuff around Greg KH
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=4C7CC90C.2030100@suse.cz \
--to=jslaby@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.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