[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <DB7PR04MB42529BA4D52D105DBE9223318B280@DB7PR04MB4252.eurprd04.prod.outlook.com>
Date: Sun, 29 Jul 2018 06:20:30 +0000
From: Vakul Garg <vakul.garg@....com>
To: David Miller <davem@...emloft.net>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"borisp@...lanox.com" <borisp@...lanox.com>,
"aviadye@...lanox.com" <aviadye@...lanox.com>,
"davejwatson@...com" <davejwatson@...com>
Subject: RE: [net-next v6 1/2] net/tls: Use socket data_ready callback on
record availability
> -----Original Message-----
> From: David Miller [mailto:davem@...emloft.net]
> Sent: Sunday, July 29, 2018 11:48 AM
> To: Vakul Garg <vakul.garg@....com>
> Cc: netdev@...r.kernel.org; borisp@...lanox.com;
> aviadye@...lanox.com; davejwatson@...com
> Subject: Re: [net-next v6 1/2] net/tls: Use socket data_ready callback on
> record availability
>
> From: Vakul Garg <vakul.garg@....com>
> Date: Sun, 29 Jul 2018 06:01:29 +0000
>
> > Could you please correct me if my counter-reasoning behind changing
> > the socket callback is wrong?
>
> Ok, after stufying the code a bit I agree with your analysis.
Thanks.
Kindly advise, if I need to resubmit/rebase the patch.
Powered by blists - more mailing lists