From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sk98lin: planned removal
Date: Thu, 15 Feb 2007 05:19:24 -0500 [thread overview]
Message-ID: <45D433AC.7030809@pobox.com> (raw)
In-Reply-To: <20070207203215.bdf3908b.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Wed, 7 Feb 2007 09:18:30 -0800 Stephen Hemminger <shemminger@linux-foundation.org> wrote:
>
>> Document planned removal of sk98lin driver.
>>
>> Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org>
>> ---
>> Documentation/feature-removal-schedule.txt | 7 +++++++
>> 1 files changed, 7 insertions(+), 0 deletions(-)
>>
>> diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
>> index 0ba6af0..d08a4af 100644
>> --- a/Documentation/feature-removal-schedule.txt
>> +++ b/Documentation/feature-removal-schedule.txt
>> @@ -325,3 +325,10 @@ Why: Unmaintained for years, superceded
>> Who: Jeff Garzik <jeff@garzik.org>
>>
>> ---------------------------
>> +
>> +What: sk98lin network driver
>> +When: July 2007
>> +Why: In kernel tree version of driver is unmaintained. Sk98lin driver
>> + replaced by the skge driver.
>> +Who: Stephen Hemminger <shemminger@osdl.org>
>> +
>
> People don't read that file. I'd suggest the addition of a warning printk
> to the driver's open() method.
Fine with me. Stephen, wanna cook up a patch?
Jeff
next prev parent reply other threads:[~2007-02-15 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 17:18 [PATCH] sk98lin: planned removal Stephen Hemminger
2007-02-07 22:28 ` Jeff Garzik
2007-02-08 4:32 ` Andrew Morton
2007-02-15 10:19 ` Jeff Garzik [this message]
2007-02-16 23:07 ` Stephen Hemminger
2007-02-17 20:38 ` Jeff Garzik
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=45D433AC.7030809@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@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 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.