All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nicolas de Pesloüan" <nicolas.2p.debian@gmail.com>
To: Alexander Smirnov <alex.bluesman.smirnov@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	linux-zigbee-devel <linux-zigbee-devel@lists.sourceforge.net>,
	Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
	"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>
Subject: Re: [PATCH series v2] IEEE 802.15.4 MAC layer basic implementation
Date: Mon, 26 Dec 2011 18:57:12 +0100	[thread overview]
Message-ID: <4EF8B578.6050201@gmail.com> (raw)
In-Reply-To: <CAJmB2rBMVvw_TV-mT2-jT7=H0adfMWaYFC0Q908pc_ND+PLD_g@mail.gmail.com>

Le 26/12/2011 17:01, Alexander Smirnov a écrit :
> Dear David, colleagues,
>
> I'm very sorry for the flood with my previous messages, problems with
> mail client :-(
>
> This is the second version of patch series which adds basic support for
> IEEE 802.15.4 Medium Access Control layer.
>
> The IEEE 802.15.4 Working Group focuses on the standardization of the
> bottom two layers of ISO/OSI protocol stack: Physical (PHY) and MAC.
> The MAC layer provides access control to a shared channel and reliable
> data delivery.
>
> This series provide only basic features:
>   - interface for drivers registration
>   - RX/TX datapaths
>   - reduced mlme operations
>   - monitor device type support (used by network sniffers, e.g. Wireshark)
>   - IEEE 802.15.4 loopback driver
>   - documentation update

Is the word "slave" used by IEEE 802.15.4 or by the kernel part you expand?

I remember a few years ago someone advocating against the usage of the word "slave", due to its 
meaning outside of IT. I know it is used many time in the kernel (in particular in bonding), but if 
people advocate against this usage, we should use "port" instead, if and when possible.

(Yes, I know, I just posted a patch to document the active_slave option for bonding... :-/ ).

	Nicolas.

      parent reply	other threads:[~2011-12-26 17:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-26 16:01 [PATCH series v2] IEEE 802.15.4 MAC layer basic implementation Alexander Smirnov
2011-12-26 17:05 ` [PATCH 04/14 v2] mac802154: TX data path Alexander Smirnov
2011-12-26 17:06 ` [PATCH 05/14 v2] mac802154: define reduced mlme operations Alexander Smirnov
2011-12-26 17:07 ` [PATCH 06/14 v2] mac802154: slave interfaces definition Alexander Smirnov
2011-12-26 17:09 ` [PATCH 07/14 v2] mac802154: reduced mlme operations Alexander Smirnov
2011-12-26 17:09 ` [PATCH 08/14 v2] mac802154: basic mib support Alexander Smirnov
2011-12-26 17:11 ` [PATCH 10/14 v2] ieee802154: interface type to be added Alexander Smirnov
2011-12-26 17:11 ` [PATCH 11/14 v2] mac802154: slaves manipulation routine Alexander Smirnov
2011-12-26 17:12 ` [PATCH 12/14 v2] mac802154: monitor device support Alexander Smirnov
     [not found] ` <CAJmB2rBMVvw_TV-mT2-jT7=H0adfMWaYFC0Q908pc_ND+PLD_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-12-26 17:02   ` [PATCH 01/14 v2] mac802154: basic ieee802.15.4 device structures Alexander Smirnov
     [not found]     ` <1324918953-14813-1-git-send-email-alex.bluesman.smirnov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-12-26 20:07       ` David Miller
2011-12-26 17:04   ` [PATCH 02/14 v2] mac802154: allocation of ieee802154 device Alexander Smirnov
     [not found]     ` <1324919047-14851-1-git-send-email-alex.bluesman.smirnov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-12-26 20:09       ` David Miller
2011-12-28  7:19         ` Alexander Smirnov
2011-12-28  7:31           ` David Miller
2012-01-05 14:11             ` Alexander Smirnov
2011-12-26 17:04   ` [PATCH 03/14 v2] mac802154: RX data path Alexander Smirnov
2011-12-26 17:10   ` [PATCH 09/14 v2] ieee802154: remove ieee802154 policy from globals Alexander Smirnov
2011-12-26 17:12   ` [PATCH 13/14 v2] drivers/ieee802154: IEEE 802.15.4 loopback driver Alexander Smirnov
2011-12-26 17:13   ` [PATCH 14/14 v2] Documentation/networking/ieee802154: update MAC chapter Alexander Smirnov
2011-12-26 17:57 ` Nicolas de Pesloüan [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=4EF8B578.6050201@gmail.com \
    --to=nicolas.2p.debian@gmail.com \
    --cc=alex.bluesman.smirnov@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dbaryshkov@gmail.com \
    --cc=linux-zigbee-devel@lists.sourceforge.net \
    --cc=netdev@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.