summaryrefslogtreecommitdiff
path: root/scripts/bin2c.c
diff options
context:
space:
mode:
authorDaniel Borkmann <dborkman@redhat.com>2013-08-29 21:55:05 (GMT)
committerDavid S. Miller <davem@davemloft.net>2013-08-30 21:56:47 (GMT)
commit2d98c29b6fb3de44d9eaa73c09f9cf7209346383 (patch)
tree57d3bc8a2dae4c9a4e87ec14207505cb8db312f1 /scripts/bin2c.c
parent0d63c27d9e879a0b54eb405636d60ab12040ca46 (diff)
downloadlinux-2d98c29b6fb3de44d9eaa73c09f9cf7209346383.tar.xz
net: bridge: convert MLDv2 Query MRC into msecs_to_jiffies for max_delay
While looking into MLDv1/v2 code, I noticed that bridging code does not convert it's max delay into jiffies for MLDv2 messages as we do in core IPv6' multicast code. RFC3810, 5.1.3. Maximum Response Code says: The Maximum Response Code field specifies the maximum time allowed before sending a responding Report. The actual time allowed, called the Maximum Response Delay, is represented in units of milliseconds, and is derived from the Maximum Response Code as follows: [...] As we update timers that work with jiffies, we need to convert it. Signed-off-by: Daniel Borkmann <dborkman@redhat.com> Cc: Linus Lüssing <linus.luessing@web.de> Cc: Hannes Frederic Sowa <hannes@stressinduktion.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'scripts/bin2c.c')
0 files changed, 0 insertions, 0 deletions