All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Jouni Malinen <jouni@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 4/4] ath6kl: Allow enabling of P2P support
Date: Tue, 6 Sep 2011 10:51:55 +0300	[thread overview]
Message-ID: <4E65D11B.3080904@qca.qualcomm.com> (raw)
In-Reply-To: <20110906072138.GA3125@jouni.qca.qualcomm.com>

On 09/06/2011 10:21 AM, Jouni Malinen wrote:
> On Tue, Sep 06, 2011 at 09:58:35AM +0300, Kalle Valo wrote:
>> On 09/05/2011 05:38 PM, Jouni Malinen wrote:
>>> --- a/drivers/net/wireless/ath/ath6kl/cfg80211.c +++
>>> b/drivers/net/wireless/ath/ath6kl/cfg80211.c +static unsigned int
>>> ath6kl_p2p; + +module_param(ath6kl_p2p, uint, 0644);
>> 
>> Currently all module parameters are in init.c. It's not the best
>> place and most likely will move to core.c soon, but I still would
>> prefer to have them all in one place. I think moving this to init.c
>> would make sense.
> 
> I started with this in init.c, but that causes checkpatch warnings
> when the variable needs to be accessed as extern in cfg80211.c. Or
> well, I guess I could hide that by defining the extern in a header
> file, but this parameter should not really be used in any other file
> than cfg80211.c to initialize the flag in struct ath6kl. As such, I
> would prefer not to make its visibility any larger that necessary.

I was more thinking that ath6kl_p2p would not be exposed outside init.c,
instead you would set the appropriate conf_flag in ath6kl_core_init() or
similar function. But leave the module_param as it is for now, I will
cleanup the module parameters anyway soon.

> Why would all module parameters need to be defined in the same C
> file?

Just for consistency so that people don't need to grep different locations.

>> Can we combine this if block with the first one?
> 
> Sure, but that would add extra indentation level for the following
> code, so this separate check-if-P2P-is-supported followed by 
> if-P2P-is-supported looks cleaner to me.

Yeah, you are right. My original comment was bogus.

>> If it's ok for you, I'll commit the first three patches and we can
>> talk more about this patch.
> 
> Yes, please do.

Ok, I have applied the first three now.

Kalle

  reply	other threads:[~2011-09-06  7:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-05 14:38 [PATCH 0/4] ath6kl: Fix AP mode PS buffering and enable AP/P2P Jouni Malinen
2011-09-05 14:38 ` [PATCH 1/4] ath6kl: Fix WMI message structure for AP_SET_PVB Jouni Malinen
2011-09-05 14:38 ` [PATCH 2/4] ath6kl: Fix AP mode connect event parsing and TIM updates Jouni Malinen
2011-09-05 14:38 ` [PATCH 3/4] ath6kl: Allow AP mode to be configured Jouni Malinen
2011-09-05 14:38 ` [PATCH 4/4] ath6kl: Allow enabling of P2P support Jouni Malinen
2011-09-06  6:58   ` Kalle Valo
2011-09-06  7:16     ` Kalle Valo
2011-09-06  7:21     ` Jouni Malinen
2011-09-06  7:51       ` Kalle Valo [this message]
2011-09-06  9:35         ` Jouni Malinen
2011-09-07  7:16           ` Kalle Valo

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=4E65D11B.3080904@qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=jouni@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.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.