From: Felix Fietkau <nbd@openwrt.org>
To: linux-wireless@vger.kernel.org
Cc: linville@tuxdriver.com, mcgrof@qca.qualcomm.com,
rmanohar@qca.qualcomm.com
Subject: Re: [PATCH v6 2/3] ath9k: merge reset related functions
Date: Mon, 29 Aug 2011 19:42:15 +0200 [thread overview]
Message-ID: <4E5BCF77.2030701@openwrt.org> (raw)
In-Reply-To: <1314614783-6133-2-git-send-email-nbd@openwrt.org>
On 2011-08-29 12:46 PM, Felix Fietkau wrote:
> reduces unnecessary code duplication
>
> Signed-off-by: Felix Fietkau<nbd@openwrt.org>
I just found a potential 'scheduling while atomic' issue. Will send a v7
- Felix
prev parent reply other threads:[~2011-08-29 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 10:46 [PATCH v6 1/3] ath9k: eliminate common->{rx,tx}_chainmask Felix Fietkau
2011-08-29 10:46 ` [PATCH v6 2/3] ath9k: merge reset related functions Felix Fietkau
2011-08-29 10:46 ` [PATCH v6 3/3] ath9k: implement .get_antenna and .set_antenna Felix Fietkau
2011-08-29 17:42 ` Felix Fietkau [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=4E5BCF77.2030701@openwrt.org \
--to=nbd@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@qca.qualcomm.com \
--cc=rmanohar@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).