[PATCH 1/2] examples/ipsec-secgw: fix width of variables

[Akhil Goyal]

> 
> > 'rte_eth_rx_burst' returns uint16_t. The same value need to be passed
> > to 'process_packets' functions which performs further processing. Having
> > this function use 'uint8_t' can result in issues when MAX_PKT_BURST is
> > larger.
> >
> > The route functions (route4_pkts & route6_pkts) take uint8_t as the
> > argument. The caller can pass larger values as the field that is passed
> > is of type uint32_t. And the function can work with uint32_t as it loops
> > through the packets and sends it out. Using uint8_t can result in silent
> > packet drops.
> >
> > Fixes: 4fbfa6c7c921 ("examples/ipsec-secgw: update eth header during route
> lookup")

Cc: stable at dpdk.org

> >
> > Signed-off-by: Anoob Joseph <anoobj at marvell.com>
Acked-by: Akhil Goyal <gakhil at marvell.com>

Applied to dpdk-next-crypto
 
> Acked-by: Konstantin Ananyev <konstantin.ananyev at huawei.com>
Email Id shows warning in mailmap
Contributor name/email mismatch with .mailmap:
        Konstantin Ananyev <konstantin.ananyev at huawei.com> is not the primary email address

I believe Konstantin is using both email ids, but mailmap is taking the first one as primary one.
Konstantin,
Is it possible for you to use a single email ID and update mailmap accordingly?