public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <antonio@meshcoding.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCHv2] batman-adv: introduce capability initialization bitfield
Date: Sun, 10 Nov 2013 20:18:53 +0100	[thread overview]
Message-ID: <20131110191853.GP970@neomailbox.net> (raw)
In-Reply-To: <1384061349-17901-1-git-send-email-linus.luessing@web.de>

[-- Attachment #1: Type: text/plain, Size: 766 bytes --]

On Sun, Nov 10, 2013 at 06:29:09AM +0100, Linus Lüssing wrote:
> @@ -251,10 +251,12 @@ struct batadv_orig_node {
>   * enum batadv_orig_capabilities - orig node capabilities
>   * @BATADV_ORIG_CAPA_HAS_DAT: orig node has distributed arp table enabled
>   * @BATADV_ORIG_CAPA_HAS_NC: orig node has network coding enabled
> + * @BATADV_ORIG_CAPA_HAS_TVLV: orig node has tvlv capability
>   */
>  enum batadv_orig_capabilities {
>  	BATADV_ORIG_CAPA_HAS_DAT = BIT(0),
>  	BATADV_ORIG_CAPA_HAS_NC = BIT(1),
> +	BATADV_ORIG_CAPA_HAS_TVLV = BIT(2),


Hi Linus,

why did you name the flag BATADV_ORIG_CAPA_HAS_TVLV instead of
BATADV_ORIG_CAPA_HAS_TT ?

Am I missing something or you picked up the wrong name? :)


Cheers,


-- 
Antonio Quartulli

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2013-11-10 19:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-10  5:29 [B.A.T.M.A.N.] [PATCHv2] batman-adv: introduce capability initialization bitfield Linus Lüssing
2013-11-10 19:18 ` Antonio Quartulli [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=20131110191853.GP970@neomailbox.net \
    --to=antonio@meshcoding.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.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