netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxim Osipov <maxim.osipov@gmail.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
	netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
	slapin@ossfans.org, maxim.osipov@siemens.com,
	dmitry.baryshkov@siemens.com, oliver.fendt@siemens.com
Subject: Re: [PATCH 2/5] net: add IEEE 802.15.4 partial implementation
Date: Thu, 28 May 2009 10:35:20 +0400	[thread overview]
Message-ID: <6097c490905272335t55d96240j904c6f72438bd7fd@mail.gmail.com> (raw)
In-Reply-To: <1243480131.16597.174.camel@deadeye>

> [...]
>> --- /dev/null
>> +++ b/include/net/ieee802154/nl.h
> [...]
>> +/* commands */
>> +/* REQ should be responded with CONF
>> + * and INDIC with RESP
>> + */
>> +enum {
>> +     __IEEE802154_COMMAND_INVALID,
>> +
>> +     IEEE802154_ASSOCIATE_REQ,
>> +     IEEE802154_ASSOCIATE_CONF,
>> +     IEEE802154_DISASSOCIATE_REQ,
>> +     IEEE802154_DISASSOCIATE_CONF,
>> +     IEEE802154_GET_REQ,
>> +     IEEE802154_GET_CONF,
>> +/*   IEEE802154_GTS_REQ, */
>> +/*   IEEE802154_GTS_CONF, */
>
> Why are some of these commented out?  Since they're apparently exposed
> to user-space you can't insert them later.
>

We are working to define a next version of netlink API for the stack
right now. But taking into account, that iz tool & upper layers of
stack will be the only users of this API at least for next year, and
IEEE802.15.4 spec is evolving, it is probably not necessary to come up
with a very final version.

Kind regards,
Maxim

  reply	other threads:[~2009-05-28  6:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26 11:21 [RFC][WIP] IEEE 802.15.4 implementation for Linux Dmitry Eremin-Solenikov
2009-05-26 11:23 ` [PATCH 1/5] Add constants for the ieee 802.15.4/ZigBee stack Dmitry Eremin-Solenikov
2009-05-26 11:23   ` [PATCH 2/5] net: add IEEE 802.15.4 partial implementation Dmitry Eremin-Solenikov
2009-05-26 11:23     ` [PATCH 3/5] ieee802154: add socket address family code Dmitry Eremin-Solenikov
     [not found]       ` <1243336988-20109-3-git-send-email-dbaryshkov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-05-26 11:23         ` [PATCH 4/5] ieee802154: add virtual loopback driver Dmitry Eremin-Solenikov
2009-05-26 11:23           ` [PATCH 5/5] ieee802154: add serial dongle driver Dmitry Eremin-Solenikov
     [not found]     ` <1243336988-20109-2-git-send-email-dbaryshkov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-05-28  3:08       ` [PATCH 2/5] net: add IEEE 802.15.4 partial implementation Ben Hutchings
2009-05-28  6:35         ` Maxim Osipov [this message]
2009-05-28  8:48         ` Dmitry Eremin-Solenikov
2009-05-30 16:32           ` Ben Hutchings
2009-05-27  9:58 ` [RFC][WIP] IEEE 802.15.4 implementation for Linux Florian Fainelli
2009-05-27 12:46   ` Dmitry Eremin-Solenikov

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=6097c490905272335t55d96240j904c6f72438bd7fd@mail.gmail.com \
    --to=maxim.osipov@gmail.com \
    --cc=ben@decadent.org.uk \
    --cc=dbaryshkov@gmail.com \
    --cc=dmitry.baryshkov@siemens.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maxim.osipov@siemens.com \
    --cc=maxim@mox.ru \
    --cc=netdev@vger.kernel.org \
    --cc=oliver.fendt@siemens.com \
    --cc=slapin@ossfans.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;
as well as URLs for NNTP newsgroup(s).