From: Michael Buesch <mb@bu3sch.de>
To: bcm43xx-dev@lists.berlios.de
Cc: "Gábor Stefanik" <netrolller.3d@gmail.com>,
"Rafał Miłecki" <zajec5@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/7] b43: N-PHY: implement TX PHY cleanup and setup
Date: Sun, 17 Jan 2010 17:41:00 +0100 [thread overview]
Message-ID: <201001171741.02945.mb@bu3sch.de> (raw)
In-Reply-To: <69e28c911001170837u4ea715ddn4a8e2001f6c1acc3@mail.gmail.com>
On Sunday 17 January 2010 17:37:29 Gábor Stefanik wrote:
> While you are at it, why aren't you programming these table writes?
> The table handling functions are AFAIK already in place...
Because we like small patches.
Please do _not_ increase the patchsize.
--
Greetings, Michael.
next prev parent reply other threads:[~2010-01-17 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 12:03 [PATCH 2/7] b43: N-PHY: implement TX PHY cleanup and setup Rafał Miłecki
2010-01-17 16:37 ` Gábor Stefanik
2010-01-17 16:41 ` Michael Buesch [this message]
2010-01-17 16:44 ` Gábor Stefanik
2010-01-17 16:48 ` Rafał Miłecki
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=201001171741.02945.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@gmail.com \
--cc=zajec5@gmail.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