> -----Original Message-----
> From: David Miller <da...@davemloft.net>
> Sent: Wednesday, September 26, 2018 9:10 AM
> To: Vakul Garg <vakul.g...@nxp.com>
> Cc: netdev@vger.kernel.org; bor...@mellanox.com;
> avia...@mellanox.com; davejwat...@fb.com; doro...@fb.com
> Subject: Re: [PATCH net-next] tls: Fix socket mem accounting error under
> async encryption
>
> From: Vakul Garg <vakul.g...@nxp.com>
> Date: Wed, 26 Sep 2018 01:54:25 +0000
>
> > I don't find this patch and one other ("tls: Fixed a memory leak
> > during socket close") in linux-net-next. Could you please kindly
> > check? Regards.
>
> After applying I didn't push out and instead I started a test build, closed my
> laptop, did a lot of other things and just came back to finish the build.
>
> It'll show up momentarily.
>
> Thanks for your patience.
Thanks for explaining the workflow.
BTW, I noticed following build failure.
It gets resolved after reverting d6ab93364734.
CC [M] drivers/net/phy/marvell.o
drivers/net/phy/marvell.c: In function 'm88e1121_config_aneg':
drivers/net/phy/marvell.c:468:25: error: 'autoneg' undeclared (first use in
this function); did you mean 'put_net'?
if (phydev->autoneg != autoneg || changed) {
^~~~~~~
put_net
drivers/net/phy/marvell.c:468:25: note: each undeclared identifier is reported
only once for each function it appears in
