From: John W. Linville <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org,
Stable <stable@vger.kernel.org>
Subject: [FIX 3.3+][PATCH] ssb: implement spurious tone avoidance
Date: Mon, 1 Apr 2013 16:01:56 -0400 [thread overview]
Message-ID: <20130401200156.GF3526@tuxdriver.com> (raw)
In-Reply-To: <1364487482-14642-1-git-send-email-zajec5@gmail.com>
On Thu, Mar 28, 2013 at 05:18:02PM +0100, Rafa? Mi?ecki wrote:
> And make use of it in b43. This fixes a regression introduced with
> 49d55cef5b1925a5c1efb6aaddaa40fc7c693335
> b43: N-PHY: implement spurious tone avoidance
> This commit made BCM4322 use only MCS 0 on channel 13, which of course
> resulted in performance drop (down to 0.7Mb/s).
>
> Reported-by: Stefan Br?ns <stefan.bruens@rwth-aachen.de>
> Signed-off-by: Rafa? Mi?ecki <zajec5@gmail.com>
> Cc: Stable <stable@vger.kernel.org>
> ---
> John:
> While this is fix, unfortunately it's not a one-liner. I wish to see it
> in 3.9 and backported to stable kernels, but if you think it's too big,
> well, just take it for the next.
CC drivers/ssb/driver_chipcommon_pmu.o
drivers/ssb/driver_chipcommon_pmu.c: In function ?ssb_pmu_spuravoid_pllupdate?:
drivers/ssb/driver_chipcommon_pmu.c:695:3: error: implicit declaration of function ?ssb_err? [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[1]: *** [drivers/ssb/driver_chipcommon_pmu.o] Error 1
make: *** [drivers/ssb/] Error 2
When building in wireless.git...
--
John W. Linville Someday the world will need a hero, and you
linville at tuxdriver.com might be all we have. Be ready.
WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org,
Stable <stable@vger.kernel.org>
Subject: Re: [FIX 3.3+][PATCH] ssb: implement spurious tone avoidance
Date: Mon, 1 Apr 2013 16:01:56 -0400 [thread overview]
Message-ID: <20130401200156.GF3526@tuxdriver.com> (raw)
In-Reply-To: <1364487482-14642-1-git-send-email-zajec5@gmail.com>
On Thu, Mar 28, 2013 at 05:18:02PM +0100, Rafał Miłecki wrote:
> And make use of it in b43. This fixes a regression introduced with
> 49d55cef5b1925a5c1efb6aaddaa40fc7c693335
> b43: N-PHY: implement spurious tone avoidance
> This commit made BCM4322 use only MCS 0 on channel 13, which of course
> resulted in performance drop (down to 0.7Mb/s).
>
> Reported-by: Stefan Brüns <stefan.bruens@rwth-aachen.de>
> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
> Cc: Stable <stable@vger.kernel.org>
> ---
> John:
> While this is fix, unfortunately it's not a one-liner. I wish to see it
> in 3.9 and backported to stable kernels, but if you think it's too big,
> well, just take it for the next.
CC drivers/ssb/driver_chipcommon_pmu.o
drivers/ssb/driver_chipcommon_pmu.c: In function ‘ssb_pmu_spuravoid_pllupdate’:
drivers/ssb/driver_chipcommon_pmu.c:695:3: error: implicit declaration of function ‘ssb_err’ [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[1]: *** [drivers/ssb/driver_chipcommon_pmu.o] Error 1
make: *** [drivers/ssb/] Error 2
When building in wireless.git...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2013-04-01 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 16:18 [FIX 3.3+][PATCH] ssb: implement spurious tone avoidance Rafał Miłecki
2013-03-28 16:18 ` Rafał Miłecki
2013-04-01 20:01 ` John W. Linville [this message]
2013-04-01 20:01 ` John W. Linville
2013-04-01 21:36 ` Hauke Mehrtens
2013-04-01 21:36 ` Hauke Mehrtens
2013-04-02 13:56 ` Rafał Miłecki
2013-04-02 13:56 ` Rafał Miłecki
2013-04-02 13:57 ` [PATCH V2] " Rafał Miłecki
2013-04-02 13:57 ` 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=20130401200156.GF3526@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.