From: Sujith <Sujith.Manoharan@atheros.com>
To: "atheros.eng.projects.ath9k-devel@mailman.users.atheros.com"
<atheros.eng.projects.ath9k-devel@mailman.users.atheros.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: [internal-ath9k-devel] [PATCH v2] ath9k: declare MODULE_FIRMWARE for ath9k_htc
Date: Fri, 25 Jun 2010 14:10:02 +0530 [thread overview]
Message-ID: <19492.27490.4534.630253@gargle.gargle.HOWL> (raw)
In-Reply-To: <1277319039-20837-1-git-send-email-linville@tuxdriver.com>
John W. Linville wrote:
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
> ---
> v2 -> avoid duplicate strings for firmware names and simultaneously
> attract attention to MODULE_FIRMWARE section in the even of
> any updates
>
Neat, thanks.
Sujith
prev parent reply other threads:[~2010-06-25 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 18:23 [PATCH] ath9k: declare MODULE_FIRMWARE for ath9k_htc John W. Linville
2010-06-23 18:50 ` [PATCH v2] " John W. Linville
2010-06-25 8:40 ` Sujith [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=19492.27490.4534.630253@gargle.gargle.HOWL \
--to=sujith.manoharan@atheros.com \
--cc=atheros.eng.projects.ath9k-devel@mailman.users.atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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