From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org
Subject: Re: [PATCH] b43legacy: drop invalid IMCFGLO workaround
Date: Thu, 05 May 2011 11:55:48 -0500 [thread overview]
Message-ID: <4DC2D694.3070200@lwfinger.net> (raw)
In-Reply-To: <1304592364-5075-1-git-send-email-zajec5@gmail.com>
On 05/05/2011 05:46 AM, Rafał Miłecki wrote:
> We were performing it on wrong core, it was outdated and is already
> implemented in ssb.
>
> Signed-off-by: Rafał Miłecki<zajec5@gmail.com>
> ---
> drivers/net/wireless/b43legacy/main.c | 32 --------------------------------
> 1 files changed, 0 insertions(+), 32 deletions(-)
Tested-by: Larry Finger <Larry.Finger@lwfinger.net>
and an ACK, of course.
Larry
prev parent reply other threads:[~2011-05-05 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 10:46 [PATCH] b43legacy: drop invalid IMCFGLO workaround Rafał Miłecki
2011-05-05 16:55 ` Larry Finger [this message]
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=4DC2D694.3070200@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).