Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	vasanth@atheros.com, Sujith.Manoharan@atheros.com
Subject: Re: [PATCH 1/6] ath9k: move common->debug_mask setting to ath_init_softc()
Date: Thu, 8 Oct 2009 00:58:06 -0400	[thread overview]
Message-ID: <43e72e890910072158p6286f7f2va4954eb870ec9918@mail.gmail.com> (raw)
In-Reply-To: <20091008043426.GA5760@bombadil.infradead.org>

On Thu, Oct 8, 2009 at 12:34 AM, Luis R. Rodriguez
<lrodriguez@atheros.com> wrote:
> On Tue, Oct 06, 2009 at 09:19:06PM -0400, Luis R. Rodriguez wrote:
>> What this means is we can enable now debug prints without
>> requiring CONFIG_ATH9K_DEBUG.
>>
>> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
>
>> +MODULE_PARM_DESC(ath9k_debug, "Debugging mask");
>
> John, as sujith notes, this should be MODULE_PARM_DESC(debug ...
>
> Thanks sujith.
>
> so here's v2:

Oh this is merged already -- either you can take this one or I'll send
a fix now.

  Luis

  reply	other threads:[~2009-10-08  4:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-07  1:19 [PATCH 0/6] ath9k: fix rmmod Luis R. Rodriguez
2009-10-07  1:19 ` [PATCH 1/6] ath9k: move common->debug_mask setting to ath_init_softc() Luis R. Rodriguez
2009-10-08  4:34   ` Luis R. Rodriguez
2009-10-08  4:58     ` Luis R. Rodriguez [this message]
2009-10-07  1:19 ` [PATCH 2/6] ath9k: initialize hw prior to debugfs Luis R. Rodriguez
2009-10-07  1:19 ` [PATCH 3/6] ath9k: add helper to un-init the hw properly Luis R. Rodriguez
2009-10-07  1:19 ` [PATCH 4/6] ath9k: add a helper to clean the core driver upon module unload Luis R. Rodriguez
2009-10-07  1:19 ` [PATCH 5/6] ath9k: move ath_cleanup() below helpers to avoid forward declarations Luis R. Rodriguez
2009-10-07  1:19 ` [PATCH 6/6] ath9k: rename ath_beaconq_setup() to ath9k_hw_beaconq_setup() 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=43e72e890910072158p6286f7f2va4954eb870ec9918@mail.gmail.com \
    --to=lrodriguez@atheros.com \
    --cc=Sujith.Manoharan@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=vasanth@atheros.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