Home
last modified time | relevance | path

Searched hist:"13378 cad" (Results 1 – 2 of 2) sorted by relevance

/openbmc/linux/include/net/
H A Droute.h13378cad Mon Jul 23 15:57:45 CDT 2012 David S. Miller <davem@davemloft.net> ipv4: Change rt->rt_iif encoding.

On input packet processing, rt->rt_iif will be zero if we should
use skb->dev->ifindex.

Since we access rt->rt_iif consistently via inet_iif(), that is
the only spot whose interpretation have to adjust.

Signed-off-by: David S. Miller <davem@davemloft.net>
13378cad Mon Jul 23 15:57:45 CDT 2012 David S. Miller <davem@davemloft.net> ipv4: Change rt->rt_iif encoding.

On input packet processing, rt->rt_iif will be zero if we should
use skb->dev->ifindex.

Since we access rt->rt_iif consistently via inet_iif(), that is
the only spot whose interpretation have to adjust.

Signed-off-by: David S. Miller <davem@davemloft.net>
/openbmc/linux/net/ipv4/
H A Droute.c13378cad Mon Jul 23 15:57:45 CDT 2012 David S. Miller <davem@davemloft.net> ipv4: Change rt->rt_iif encoding.

On input packet processing, rt->rt_iif will be zero if we should
use skb->dev->ifindex.

Since we access rt->rt_iif consistently via inet_iif(), that is
the only spot whose interpretation have to adjust.

Signed-off-by: David S. Miller <davem@davemloft.net>
13378cad Mon Jul 23 15:57:45 CDT 2012 David S. Miller <davem@davemloft.net> ipv4: Change rt->rt_iif encoding.

On input packet processing, rt->rt_iif will be zero if we should
use skb->dev->ifindex.

Since we access rt->rt_iif consistently via inet_iif(), that is
the only spot whose interpretation have to adjust.

Signed-off-by: David S. Miller <davem@davemloft.net>