From: Johannes Berg <johannes@sipsolutions.net>
To: Rui Paulo <rpaulo@gmail.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: use a structure to hold the mesh config information element
Date: Wed, 18 Nov 2009 19:26:29 +0100 [thread overview]
Message-ID: <1258568789.30511.52.camel@johannes.local> (raw)
In-Reply-To: <1258568579-21900-1-git-send-email-rpaulo@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 260 bytes --]
Cool, thanks.
> case WLAN_EID_MESH_CONFIG:
> elems->mesh_config = pos;
> - elems->mesh_config_len = elen;
> break;
Should there be a length check here?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-11-18 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 18:22 [PATCH] mac80211: use a structure to hold the mesh config information element Rui Paulo
2009-11-18 18:22 ` [PATCH] mac80211: update cfg80211 scan result code for the updated mesh conf IE Rui Paulo
2009-11-18 18:26 ` Johannes Berg [this message]
2009-11-18 18:31 ` [PATCH] mac80211: use a structure to hold the mesh config information element Rui Paulo
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=1258568789.30511.52.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rpaulo@gmail.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