From: Marek Lindner <lindner_marek@yahoo.de>
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 2/2] batman-adv: Fix signedness problem in parse_gw_bandwidth
Date: Sun, 5 Jun 2011 22:35:49 +0200 [thread overview]
Message-ID: <201106052235.49274.lindner_marek@yahoo.de> (raw)
In-Reply-To: <1307188849-20156-1-git-send-email-sven@narfation.org>
On Saturday, June 04, 2011 02:00:49 PM Sven Eckelmann wrote:
> strict_strtoul as used in parse_gw_bandwidth is defined for unsigned
> long and strict_strtol should be used instead for long.
Applied in revision 1ad4162.
Thanks,
Marek
next prev parent reply other threads:[~2011-06-05 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 10:40 [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: Don't return value in void function Sven Eckelmann
2011-06-04 10:40 ` [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: Fix signedness problem in parse_gw_bandwidth Sven Eckelmann
2011-06-04 11:44 ` Marek Lindner
2011-06-04 11:59 ` Sven Eckelmann
2011-06-04 12:00 ` [B.A.T.M.A.N.] [PATCHv2 " Sven Eckelmann
2011-06-05 20:35 ` Marek Lindner [this message]
2011-06-05 20:33 ` [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: Don't return value in void function 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=201106052235.49274.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--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;
as well as URLs for NNTP newsgroup(s).