From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/4] cfg80211: add and use strongly typed element iteration macros
Date: Fri, 08 Feb 2019 14:02:00 +0100 [thread overview]
Message-ID: <453eddecb74fd814146bcb253a66165556769c16.camel@sipsolutions.net> (raw)
In-Reply-To: <20190208123154.22414-1-johannes@sipsolutions.net> (sfid-20190208_133206_618228_932A8E9D)
On Fri, 2019-02-08 at 13:31 +0100, Johannes Berg wrote:
>
> +static inline bool for_each_element_completed(struct element *element,
> + void *data, size_t datalen)
Those pointer arguments should be const.
johannes
prev parent reply other threads:[~2019-02-08 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 12:31 [PATCH 1/4] cfg80211: add and use strongly typed element iteration macros Johannes Berg
2019-02-08 12:31 ` [PATCH 2/4] mac80211: use element iteration macro in parsing Johannes Berg
2019-02-08 12:31 ` [PATCH 3/4] cfg80211: add various struct element finding helpers Johannes Berg
2019-02-08 12:31 ` [PATCH 4/4] nl80211: use for_each_element() in validate_ie_attr() Johannes Berg
2019-02-08 13:02 ` Johannes Berg [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=453eddecb74fd814146bcb253a66165556769c16.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox