From: Jiri Slaby <jirislaby@gmail.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] mxser, remove it
Date: Thu, 27 Dec 2007 21:54:17 +0100 [thread overview]
Message-ID: <477410F9.5030903@gmail.com> (raw)
In-Reply-To: <20071227172101.GA18199@does.not.exist>
On 12/27/2007 06:21 PM, Adrian Bunk wrote:
> On Thu, Dec 27, 2007 at 06:19:31PM +0300, Michael Tokarev wrote:
>> Jiri Slaby wrote:
>>> (Old) mxser is obsoleted by mxser_new and scheduled for removal on Dec 2007.
>>> Remove it.
>>>
>>> Signed-off-by: Jiri Slaby <jirislaby@gmail.com>
>>> ---
>>> Documentation/feature-removal-schedule.txt | 8 -
>>> drivers/char/Kconfig | 11 -
>>> drivers/char/Makefile | 1 -
>>> drivers/char/mxser.c | 3141 ----------------------------
>>> drivers/char/mxser.h | 441 ----
>>> 5 files changed, 0 insertions(+), 3602 deletions(-)
>>> delete mode 100644 drivers/char/mxser.c
>>> delete mode 100644 drivers/char/mxser.h
>> While we're at it, how about adding a modalias for mxser_new
>> module with old (being removed) name, so that users who're
>> using the old module will not scream? I mean, in order for
>> `modprobe mxser' to load mxser_new module.
>
> It might even make sense to rename the mxser_new module to mxser and do
> it the other way round - it's e.g. not clear whether a _new driver is
> for new hardware or a new driver for old hardware.
Makes sense, if no other suggestions, I will post v2 tomorrow.
thanks,
--js
next prev parent reply other threads:[~2007-12-27 20:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 13:38 [PATCH 1/1] mxser, remove it Jiri Slaby
2007-12-27 15:19 ` Michael Tokarev
2007-12-27 17:21 ` Adrian Bunk
2007-12-27 20:54 ` Jiri Slaby [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-28 10:09 Jiri Slaby
2007-12-29 1:29 ` Jan Engelhardt
2007-12-29 2:23 ` Alan Cox
2007-12-29 16:09 ` Jiri Slaby
2007-12-29 2:29 ` Alan Cox
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=477410F9.5030903@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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.