From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: introduce critical protocol indication from user-space
Date: Wed, 10 Apr 2013 15:21:03 +0200 [thread overview]
Message-ID: <1365600063.4235.3.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <516551D7.30302@broadcom.com>
On Wed, 2013-04-10 at 13:49 +0200, Arend van Spriel wrote:
> >> I am a dark-ages guy :-p I think I will rename the BOOTP one and
> >> indicate it should be used for BOOTP and DHCPv6.
> >
> > Might also be worth it to rename ARP to APIPA since ARP is ... well
> > often done :-)
>
> I chose ARP because APIPA is essentially not a protocol. As far as I
> understand it makes use of ARP to make sure the address in unique. I see
> your point and will change it. Then again it all may go away :-)
I see your point too, but I'd argue that APIPA is really more of a
higher-level protocol that uses ARP for its implementation?
> > Well you have to store the nlportid (rather than crit_proto_started) and
> > then check it.
>
> Yeah, I surmised that already. If I would drop crit_proto_started and
> use the portid as a flag as well, I need an invalid portid. Is there a
> definition for that?
I'm pretty sure 0 is invalid for userspace because it means "kernel".
johannes
next prev parent reply other threads:[~2013-04-10 13:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 9:09 [PATCH] cfg80211: introduce critical protocol indication from user-space Arend van Spriel
2013-04-09 10:06 ` Johannes Berg
2013-04-09 19:54 ` Arend van Spriel
2013-04-09 20:42 ` Johannes Berg
2013-04-10 11:49 ` Arend van Spriel
2013-04-10 13:21 ` Johannes Berg [this message]
2013-04-11 10:47 ` Arend van Spriel
2013-04-11 12:34 ` Johannes Berg
2013-04-11 10:39 ` [PATCH V6] " Arend van Spriel
2013-04-16 14:12 ` Johannes Berg
2013-04-16 21:19 ` Arend van Spriel
2013-04-16 21:43 ` Johannes Berg
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=1365600063.4235.3.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.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.