linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Denis Vlasenko <vda@ilport.com.ua>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Adrian Bunk <bunk@stusta.de>,
	acx100-devel@lists.sourceforge.net,
	"John W. Linville" <linville@tuxdriver.com>,
	jgarzik@pobox.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [-mm patch] drivers/net/wireless/tiacx/: remove code for WIRELESS_EXT < 18
Date: Fri, 27 Jan 2006 14:49:49 +0200	[thread overview]
Message-ID: <200601271449.49226.vda@ilport.com.ua> (raw)
In-Reply-To: <1138362557.5983.26.camel@localhost>

On Friday 27 January 2006 13:49, Johannes Berg wrote:
> On Fri, 2006-01-27 at 12:19 +0200, Denis Vlasenko wrote:
> 
> > I very much want to get rid of all remaining compat cruft, and
> > I plan to do it as soon as acx will be present in mainline kernel.
> 
> I doubt you'll get it merged with the compat cruft.

What cruft? This?

# grep -r WIRELESS_EXT .
./pci.c:                ndev->name, WIRELESS_EXT, UTS_RELEASE);
./common.c:             "Wireless extension version:\t" STRING(WIRELESS_EXT) "\n"
./acx_struct.h:#ifdef WIRELESS_EXT
./acx_struct.h:#if WIRELESS_EXT > 15
./ioctl.c:      range->we_version_compiled = WIRELESS_EXT;

I consider this to be a really modest amount of compat code
which makes driver users happy (that fraction of it which is not
willing to run -mm).

However, I would remove even that at Jeff's or Andrew's request,
or without anyone's request if acx will be merged to Linus tree.
--
vda

  reply	other threads:[~2006-01-27 12:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-22 17:11 [-mm patch] drivers/net/wireless/tiacx/: remove code for WIRELESS_EXT < 18 Adrian Bunk
2006-01-27 10:19 ` Denis Vlasenko
2006-01-27 11:49   ` Johannes Berg
2006-01-27 12:49     ` Denis Vlasenko [this message]
2006-01-27 14:46       ` [Acx100-devel] " Andreas Mohr
  -- strict thread matches above, loose matches on Subject: below --
2006-01-14 15:21 Adrian Bunk

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=200601271449.49226.vda@ilport.com.ua \
    --to=vda@ilport.com.ua \
    --cc=acx100-devel@lists.sourceforge.net \
    --cc=bunk@stusta.de \
    --cc=jgarzik@pobox.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).