public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <a@unstable.cc>
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.] [PATCH] batman-adv: B.A.T.M.A.N V - make sure iface is reactivated upon NETDEV_UP event
Date: Thu, 14 Apr 2016 09:39:15 +0800	[thread overview]
Message-ID: <20160414013915.GA28908@prodigo.lan> (raw)
In-Reply-To: <1891393.XZXRhtYPY0@sven-edge>

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

On Wed, Apr 13, 2016 at 10:32:43PM +0200, Sven Eckelmann wrote:
> On Thursday 14 April 2016 03:34:47 Antonio Quartulli wrote:
> [...]
> > diff --git a/net/batman-adv/types.h b/net/batman-adv/types.h
> > index 9abfb3e..316af66 100644
> > --- a/net/batman-adv/types.h
> > +++ b/net/batman-adv/types.h
> > @@ -1277,6 +1277,7 @@ struct batadv_forw_packet {
> >  struct batadv_algo_ops {
> >  	struct hlist_node list;
> >  	char *name;
> > +	void (*bat_iface_activate)(struct batadv_hard_iface *hard_iface);
> >  	int (*bat_iface_enable)(struct batadv_hard_iface *hard_iface);
> >  	void (*bat_iface_disable)(struct batadv_hard_iface *hard_iface);
> >  	void (*bat_iface_update_mac)(struct batadv_hard_iface *hard_iface);
> 
> kernel-doc is missing for @bat_iface_activate

Thanks Sven, I sent v2 with the kerneldoc

Cheers,


-- 
Antonio Quartulli

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

      reply	other threads:[~2016-04-14  1:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13 19:34 [B.A.T.M.A.N.] [PATCH] batman-adv: B.A.T.M.A.N V - make sure iface is reactivated upon NETDEV_UP event Antonio Quartulli
2016-04-13 20:32 ` Sven Eckelmann
2016-04-14  1:39   ` 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=20160414013915.GA28908@prodigo.lan \
    --to=a@unstable.cc \
    --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