From: Michael Buesch <mb@bu3sch.de>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 3/8] b43: remove b43_radio_{read|write}16 from lo.c
Date: Fri, 3 Oct 2008 23:17:19 +0200 [thread overview]
Message-ID: <200810032317.19971.mb@bu3sch.de> (raw)
In-Reply-To: <1223066926.6512.28.camel@brick>
On Friday 03 October 2008 22:48:46 Harvey Harrison wrote:
> Mostly by using the mask/set helpers. Some temporary variables have
> also been eliminated.
I already told you two times that I do not like these patches.
I also explained in great detail why this is the case.
Please drop these patches!
If you send them one more time, I will immediately add your email address to
my exim blacklist.
--
Greetings Michael.
next prev parent reply other threads:[~2008-10-03 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 20:48 [PATCH 3/8] b43: remove b43_radio_{read|write}16 from lo.c Harvey Harrison
2008-10-03 21:17 ` Michael Buesch [this message]
2008-10-03 21:33 ` Harvey Harrison
2008-10-03 21:56 ` Michael Buesch
2008-10-03 22:35 ` Michael Buesch
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=200810032317.19971.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=harvey.harrison@gmail.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;
as well as URLs for NNTP newsgroup(s).