From: Jiri Slaby <jirislaby@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH v2 2/4] ath5k: allocate ath5k_hw prior to initializing hw
Date: Mon, 14 Sep 2009 10:59:27 +0200 [thread overview]
Message-ID: <4AAE05EF.5090105@gmail.com> (raw)
In-Reply-To: <43e72e890909140156jcb1f299i718d0b9fe8ab07a8@mail.gmail.com>
On 09/14/2009 10:56 AM, Luis R. Rodriguez wrote:
> Yeah looks peachy.
Yeah, I realized it would emit a warning if ath9k_common_ops was const
and ath_common->ops wasn't. This way it is OK. Sorry for the noise.
Anyway making ath9k_common_ops const would be good ;).
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Slaby <jirislaby@gmail.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, devel@linuxdriverproject.org,
ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 2/4] ath5k: allocate ath5k_hw prior to initializing hw
Date: Mon, 14 Sep 2009 10:59:27 +0200 [thread overview]
Message-ID: <4AAE05EF.5090105@gmail.com> (raw)
In-Reply-To: <43e72e890909140156jcb1f299i718d0b9fe8ab07a8@mail.gmail.com>
On 09/14/2009 10:56 AM, Luis R. Rodriguez wrote:
> Yeah looks peachy.
Yeah, I realized it would emit a warning if ath9k_common_ops was const
and ath_common->ops wasn't. This way it is OK. Sorry for the noise.
Anyway making ath9k_common_ops const would be good ;).
next prev parent reply other threads:[~2009-09-14 8:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 8:31 [ath9k-devel] [PATCH v2 0/4] atheros: implement common read/write ops Luis R. Rodriguez
2009-09-14 8:31 ` Luis R. Rodriguez
2009-09-14 8:32 ` [ath9k-devel] [PATCH v2 1/4] atheros/ath9k: add common read/write ops and port ath9k to use it Luis R. Rodriguez
2009-09-14 8:32 ` Luis R. Rodriguez
2009-09-14 8:32 ` [ath9k-devel] [PATCH v2 2/4] ath5k: allocate ath5k_hw prior to initializing hw Luis R. Rodriguez
2009-09-14 8:32 ` Luis R. Rodriguez
2009-09-14 8:45 ` [ath9k-devel] " Jiri Slaby
2009-09-14 8:45 ` Jiri Slaby
2009-09-14 8:50 ` [ath9k-devel] " Luis R. Rodriguez
2009-09-14 8:50 ` Luis R. Rodriguez
2009-09-14 8:53 ` [ath9k-devel] " Luis R. Rodriguez
2009-09-14 8:53 ` Luis R. Rodriguez
2009-09-14 8:56 ` [ath9k-devel] " Luis R. Rodriguez
2009-09-14 8:56 ` Luis R. Rodriguez
2009-09-14 8:59 ` Jiri Slaby [this message]
2009-09-14 8:59 ` Jiri Slaby
2009-09-14 8:32 ` [ath9k-devel] [PATCH v2 3/4] ath5k: define ath_common ops Luis R. Rodriguez
2009-09-14 8:32 ` Luis R. Rodriguez
2009-09-14 8:46 ` [ath9k-devel] " Jiri Slaby
2009-09-14 8:46 ` Jiri Slaby
2009-09-14 9:01 ` [ath9k-devel] " Luis R. Rodriguez
2009-09-14 9:01 ` Luis R. Rodriguez
2009-09-14 8:32 ` [ath9k-devel] [PATCH v2 4/4] atheros: define shared bssidmask setting Luis R. Rodriguez
2009-09-14 8:32 ` 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=4AAE05EF.5090105@gmail.com \
--to=jirislaby@gmail.com \
--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.