From: "John W. Linville" <linville@tuxdriver.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: linux-wireless@vger.kernel.org, mcgrof@qca.qualcomm.com
Subject: Re: [PATCH 3.8 2/2] ath9k_hw: fix RF bank initialization
Date: Mon, 14 Jan 2013 14:58:51 -0500 [thread overview]
Message-ID: <20130114195851.GB12018@tuxdriver.com> (raw)
In-Reply-To: <1358103298-4017-2-git-send-email-nbd@openwrt.org>
On Sun, Jan 13, 2013 at 07:54:58PM +0100, Felix Fietkau wrote:
> ar900*_init_mode_regs needs to be called before RF banks are allocated,
> otherwise the storage size of RF banks isn't known. This patch fixes
> a memory overrun that can show up as a crash on unloading the module.
>
> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
<snip>
> @@ -410,7 +411,10 @@ int ar9002_hw_attach_ops(struct ath_hw *ah)
> struct ath_hw_ops *ops = ath9k_hw_ops(ah);
> int ret;
>
> - priv_ops->init_mode_regs = ar9002_hw_init_mode_regs;
> + ret = ar9002_hw_init_mode_regs(ah);
> + if (ret)
> + return ret;
> +
> priv_ops->init_mode_gain_regs = ar9002_hw_init_mode_gain_regs;
>
> ops->config_pci_powersave = ar9002_hw_configpcipowersave;
This hunk depends on "ath9k_hw: use the devres API for allocations",
which is queue for 3.9. Can you revise this for 3.8? If not, should
I hold just this one for 3.9? Or the earlier patch in the series
as well?
John
--
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-01-14 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 18:54 [PATCH 3.8 1/2] ath9k_hw: clean up RF Bank6 handling on AR5416/AR91xx Felix Fietkau
2013-01-13 18:54 ` [PATCH 3.8 2/2] ath9k_hw: fix RF bank initialization Felix Fietkau
2013-01-14 19:58 ` John W. Linville [this message]
2013-01-14 21:15 ` Felix Fietkau
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=20130114195851.GB12018@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@qca.qualcomm.com \
--cc=nbd@openwrt.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).