linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Vladimir Kondratiev" <qca_vkondrat@qca.qualcomm.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org,
	"Luis R . Rodriguez" <rodrigue@qca.qualcomm.com>,
	"John W . Linville" <linville@tuxdriver.com>,
	"Jouni Malinen" <jouni@qca.qualcomm.com>
Subject: Re: [PATCH v10 1/2] cfg80211: add flags to cfg80211_rx_mgmt
Date: Mon, 24 Jun 2013 15:46:28 +0200	[thread overview]
Message-ID: <51C84DB4.9050703@broadcom.com> (raw)
In-Reply-To: <1372063757-24286-2-git-send-email-qca_vkondrat@qca.qualcomm.com>

On 06/24/2013 10:49 AM, Vladimir Kondratiev wrote:
> diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h
> index 6a43c34..29e733c 100644
> --- a/include/net/cfg80211.h
> +++ b/include/net/cfg80211.h
> @@ -3856,6 +3856,8 @@ void cfg80211_conn_failed(struct net_device *dev, const u8 *mac_addr,
>    * @sig_dbm: signal strength in mBm, or 0 if unknown
>    * @buf: Management frame (header + body)
>    * @len: length of the frame data
> + * @flags: various flags, see NL80211_RXMGMT_FLAG_xxx defined in
> + *	enum nl80211_rxmgmt_flags

It seems sufficient to say:

@flags: flags as defined in enum nl80211_rxmgmt_flags

Regards,
Arend

>    * @gfp: context flags



  reply	other threads:[~2013-06-24 13:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24  8:49 [PATCH v10 0/2] P2P find phase offload Vladimir Kondratiev
2013-06-24  8:49 ` [PATCH v10 1/2] cfg80211: add flags to cfg80211_rx_mgmt Vladimir Kondratiev
2013-06-24 13:46   ` Arend van Spriel [this message]
2013-06-24 14:08   ` Johannes Berg
2013-06-24  8:49 ` [PATCH v10 2/2] cfg80211: P2P find phase offload Vladimir Kondratiev
2013-06-25  7:06   ` Peer, Ilan
2013-06-25  9:25     ` Vladimir Kondratiev

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=51C84DB4.9050703@broadcom.com \
    --to=arend@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --cc=jouni@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=qca_vkondrat@qca.qualcomm.com \
    --cc=rodrigue@qca.qualcomm.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;
as well as URLs for NNTP newsgroup(s).