From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: [PATCH] wireless: rename d80211 -> mac80211
Date: Mon, 26 Feb 2007 22:27:57 -0500 [thread overview]
Message-ID: <20070227032756.GA6569@tuxdriver.com> (raw)
I've been threatening to do this for a while. Since I've recently
pulled from everyone, the incoming patch rate is slow this week,
and we are getting close to being in -mm, now seems as good a time
as any to do it...
I've changed all references in wireless-dev from d80211 to mac80211
and from D80211 to MAC80211, including renaming files and directories
appropriately. If you have outstanding patches, please account for
this change. Filtering them through sed should do the job nicely:
cat old.patch | sed -e 's/d80211/mac80211/g' \
-e 's/D80211/MAC80211/g' > new.patch
I don't think it would have been appropriate to keep the old name,
with its veiled reference to its origin but no real meaning to the
uninitiated. I think the mac80211 name is more indicative of the
component's function, and it matches the naming motif we are using
for cfg80211 and nl80211.
I apologize if this seems sudden, but I don't really think doing
it with a lot of warning would have been any better. So, I made
the decision and did it. Please don't complain unless it is just
unbearable for you. :-)
The patch has been pushed to wireless-dev, and hopefully will be
available by the time you read this.
Thanks,
John
P.S. The actual patch is too large to post here. It is available
on www.kernel.org:
http://www.kernel.org/pub/linux/kernel/people/linville/wireless-dev/master/0738-wireless-rename-d80211-mac80211.patch
--
John W. Linville
linville@tuxdriver.com
next reply other threads:[~2007-02-27 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 3:27 John W. Linville [this message]
2007-02-27 10:28 ` [PATCH] wireless: rename d80211 -> mac80211 Jiri Benc
2007-02-27 10:39 ` Johannes Berg
2007-02-27 11:05 ` Jiri Benc
2007-02-27 10:56 ` Johannes Berg
2007-02-27 13:16 ` John W. Linville
2007-02-27 13:58 ` Michael Wu
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=20070227032756.GA6569@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@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