From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Vivek Natarajan <nataraja@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>,
Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
Subject: Re: [PATCH] ath6kl: Deinitialize wiphy on error.
Date: Thu, 15 Sep 2011 17:02:38 +0300 [thread overview]
Message-ID: <4E72057E.8090306@qca.qualcomm.com> (raw)
In-Reply-To: <1316073466-3971-1-git-send-email-nataraja@qca.qualcomm.com>
Preferable style for the subject is:
ath6kl: deinitialise wiphy on error
On 09/15/2011 10:57 AM, Vivek Natarajan wrote:
> This fixes the panic observed on card removal.
Please add information about the crash. For example, you could copy the
stack trace.
> @@ -853,6 +854,8 @@ static int ath6kl_sdio_probe(struct sdio_func *func,
>
> err_off:
> ath6kl_sdio_power_off(ar_sdio);
> +err_sdio:
> + ath6kl_cfg80211_deinit(ar_sdio->ar);
> err_dma:
> kfree(ar_sdio->dma_buffer);
> err_hif:
err_cfg80211, or something like that, would be a better name for the label.
But this change actually has an architectural issue. The idea is that
sdio.c only calls functions either from hif.h or core.h. It should not
use any functions from cfg80211.c.
A better fix would be to add new set of functions:
ath6kl_core_free() which can be called after ath6kl_core_alloc() is executed
ath6kl_core_cleanup() which can be called after ath6kl_core_init() is
executed. This would replace the current ath6kl_destroy() function.
But I can do the architecture change because it's more work. Please
address the minor issues I commented above and then I can take the patch.
Kalle
prev parent reply other threads:[~2011-09-15 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 7:57 [PATCH] ath6kl: Deinitialize wiphy on error Vivek Natarajan
2011-09-15 14:02 ` Kalle Valo [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=4E72057E.8090306@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nataraja@qca.qualcomm.com \
--cc=vthiagar@qca.qualcomm.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).