From: Pavel Roskin <proski@gnu.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [RFC PATCH 2/2] ath9k: fix mixing of interrupt masks, remove ah->mask_reg
Date: Wed, 31 Mar 2010 17:54:37 -0400 [thread overview]
Message-ID: <1270072477.6059.18.camel@mj> (raw)
In-Reply-To: <20100330165219.GA25095@tux>
On Tue, 2010-03-30 at 09:52 -0700, Luis R. Rodriguez wrote:
> This is exactly what I was trying to prevent, lets please try to figure out
> another way, NACK for now.
>
> Consider
>
> struct ath9k_htc_priv *priv = (struct ath9k_htc_priv *) common->priv;
OK, then let's move imask from sc to ah. It looks like ah->mask_reg was
misused exactly because sc->imask wasn't available in some files.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-03-31 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 3:39 [ath9k-devel] [RFC PATCH 1/2] ath9k: rename symbols in enum ath9k_internal_frame_type to avoid confusion Pavel Roskin
2010-03-30 3:39 ` [ath9k-devel] [RFC PATCH 2/2] ath9k: fix mixing of interrupt masks, remove ah->mask_reg Pavel Roskin
2010-03-30 16:52 ` Luis R. Rodriguez
2010-03-31 21:54 ` Pavel Roskin [this message]
2010-03-30 16:57 ` [ath9k-devel] [RFC PATCH 1/2] ath9k: rename symbols in enum ath9k_internal_frame_type to avoid confusion Luis R. Rodriguez
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=1270072477.6059.18.camel@mj \
--to=proski@gnu.org \
--cc=ath9k-devel@lists.ath9k.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 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.