From: Michael Buesch <mb@bu3sch.de>
To: John W Linville <linville@tuxdriver.com>
Cc: bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: [PATCH 0/6] b43: Use spatch to convert register accesses
Date: Fri, 20 Feb 2009 19:19:15 +0100 [thread overview]
Message-ID: <200902201854.22114.mb@bu3sch.de> (raw)
Some time ago I rejected a bunch of patches that converted the
PHY/radio register accesses to the new API. That was due to the patches
being created manually. This introduces a huge potential to add new bugs.
However, this is an excellent task for coccinelle/spatch.
So here's a series of patches, to convert the API usage, that were generated
with spatch. This should keep the chances of breaking something as low as possible.
This reduces the .ko size by about 6 kiB.
The used semantic patches will be included in the patch headers.
John, please queue these patches for the next feature release.
--
Greetings, Michael.
next reply other threads:[~2009-02-20 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 18:19 Michael Buesch [this message]
2009-02-20 19:10 ` [PATCH 0/6] b43: Use spatch to convert register accesses Michael Buesch
2009-02-20 20:10 ` Larry Finger
2009-02-20 20:12 ` Michael Buesch
2009-02-21 0:33 ` Harvey Harrison
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=200902201854.22114.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).