From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: netdev@vger.kernel.org, mike.mclagan@linux.org, akpm@osdl.org
Subject: Re: [PATCH] wan/sdla section fixes
Date: Mon, 12 Jun 2006 21:05:29 +0200 [thread overview]
Message-ID: <m34pyq42km.fsf@defiant.localdomain> (raw)
In-Reply-To: <20060612110523.300a3420.rdunlap@xenotime.net> (Randy Dunlap's message of "Mon, 12 Jun 2006 11:05:23 -0700")
"Randy.Dunlap" <rdunlap@xenotime.net> writes:
>> > static const char* version = "SDLA driver v0.30, 12 Sep 1996,
>> > mike.mclagan@linux.org";
>>
>> 1996 doesn't look encouraging but it may be misleading.
>
> Yep. You could ignore it :) or rm drivers/net/wan/slda* :)
I don't know, maybe Mike will say something?
--
Krzysztof Halasa
prev parent reply other threads:[~2006-06-12 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 3:36 [PATCH] wan/sdla section fixes Randy.Dunlap
2006-06-12 17:50 ` Krzysztof Halasa
2006-06-12 18:05 ` Randy.Dunlap
2006-06-12 19:05 ` Krzysztof Halasa [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=m34pyq42km.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=akpm@osdl.org \
--cc=mike.mclagan@linux.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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;
as well as URLs for NNTP newsgroup(s).