From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: "Martin Hundebøll" <martin@hundeboll.net>
Subject: Re: [B.A.T.M.A.N.] [PATCH 1/3] batman-adv: Remove old fragmentation code
Date: Wed, 24 Apr 2013 01:32:00 +0800 [thread overview]
Message-ID: <201304240132.00926.lindner_marek@yahoo.de> (raw)
In-Reply-To: <1366474654-26361-2-git-send-email-martin@hundeboll.net>
On Sunday, April 21, 2013 00:17:32 Martin Hundebøll wrote:
> @@ -592,9 +591,9 @@ static bool batadv_dat_send_data(struct batadv_priv
> *bat_priv, goto free_orig;
>
> tmp_skb = pskb_copy(skb, GFP_ATOMIC);
> - if (!batadv_unicast_4addr_prepare_skb(bat_priv, tmp_skb,
> - cand[i].orig_node,
> - packet_subtype)) {
> + if (!batadv_send_skb_4addr_prepare_unicast(bat_priv, tmp_skb,
> + cand[i].orig_node,
> + packet_subtype)) {
I think you mangled the "unicast_4addr" name a little. Afaik "4addr" was meant
to follow "unicast" to diffirentiate between "unicast" and "unicast_4addr".
However, I'd have no problem if you simply dropped the "unicast" part. For
example: batadv_send_skb_4addr_prepare()
> @@ -977,10 +976,10 @@ bool batadv_dat_snoop_incoming_arp_request(struct
> batadv_priv *bat_priv, * that a node not using the 4addr packet format
> doesn't support it. */
> if (hdr_size == sizeof(struct batadv_unicast_4addr_packet))
> - err = batadv_unicast_4addr_send_skb(bat_priv, skb_new,
> + err = batadv_send_skb_4addr_unicast(bat_priv, skb_new,
> BATADV_P_DAT_CACHE_REPLY);
If you decide to skip the "unicast" part above feel free to drop it here too.
> +/**
> + * batadv_send_generic_unicast_skb - send an skb as unicast
> + * @bat_priv: the bat priv with all the soft interface information
> + * @skb: payload to send
> + * @packet_type: the batman unicast packet type to use
> + * @packet_subtype: the batman packet subtype. It is ignored if packet_type
> + * not BATADV_UNICAT_4ADDR
> + *
> + * Returns 1 in case of error or 0 otherwise
> + */
Multi-line kernel doc explanations should be indented by one space.
If the function returns 0 or 1 only it should be made boolean or the return
value should use a readable define.
Cheers,
Marek
next prev parent reply other threads:[~2013-04-23 17:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 16:17 [B.A.T.M.A.N.] [PATCH 0/3] Fragmentation version 2 Martin Hundebøll
2013-04-20 16:17 ` [B.A.T.M.A.N.] [PATCH 1/3] batman-adv: Remove old fragmentation code Martin Hundebøll
2013-04-23 17:32 ` Marek Lindner [this message]
2013-04-20 16:17 ` [B.A.T.M.A.N.] [PATCH 2/3] batman-adv: Receive fragmented packets and merge Martin Hundebøll
2013-04-23 19:17 ` Marek Lindner
2013-04-23 19:30 ` Antonio Quartulli
2013-04-23 19:43 ` Marek Lindner
2013-04-23 19:47 ` Antonio Quartulli
2013-04-20 16:17 ` [B.A.T.M.A.N.] [PATCH 3/3] batman-adv: Fragment and send skbs larger than mtu Martin Hundebøll
2013-04-23 19:35 ` Marek Lindner
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=201304240132.00926.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=martin@hundeboll.net \
/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