From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH] fixes a uint32 overflow
Date: Sun, 17 May 2015 11:42:17 +0200 [thread overview]
Message-ID: <16847028.DL9gCQ2dKS@sven-edge> (raw)
In-Reply-To: <20150517112732.48476eac@i3.local>
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
On Sunday 17 May 2015 11:27:32 Ruben Wisniewski wrote:
> Signed-off-by: Ruben Wisniewsi <ruben@vfn-nrw.de>
> ---
> net/batman-adv/gateway_client.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/batman-adv/gateway_client.c
> b/net/batman-adv/gateway_client.c index bb01586..1f50661 100644
> --- a/net/batman-adv/gateway_client.c
> +++ b/net/batman-adv/gateway_client.c
> @@ -153,7 +153,7 @@ batadv_gw_get_best_gw_node(struct batadv_priv *bat_priv)
> struct batadv_neigh_node *router;
> struct batadv_neigh_ifinfo *router_ifinfo;
> struct batadv_gw_node *gw_node, *curr_gw = NULL;
> - uint32_t max_gw_factor = 0, tmp_gw_factor = 0;
> + uint64_t max_gw_factor = 0, tmp_gw_factor = 0;
> uint32_t gw_divisor;
> uint8_t max_tq = 0;
> uint8_t tq_avg;
This patch is not following
* https://www.open-mesh.org/projects/open-mesh/wiki/Contribute
* https://www.kernel.org/doc/Documentation/SubmittingPatches
* https://www.kernel.org/doc/Documentation/CodingStyle
Please add the "batman-adv: " prefix for the Subject.
The summary in the subject itself also needs to be refined. The relevant part
in SubmittingPatches for the subject can be found under "14) The canonical
patch format".
An explanation in the commit message why there is an overflow would be nice.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-05-17 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 9:27 [B.A.T.M.A.N.] [PATCH] fixes a uint32 overflow Ruben Wisniewski
2015-05-17 9:42 ` Sven Eckelmann [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=16847028.DL9gCQ2dKS@sven-edge \
--to=sven@narfation.org \
--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