On Wed, 2020-08-05 at 17:45 -0700, David Miller wrote:
> Neither of these patches apply cleanly to net-next. The compat handling
> and TLS code has been changed quite a bit lately.
Indeed, Patch 1 is no longer required on net-next. I'll drop the patch.
> ALso, you must provide a proper header "[
Hi Rouven,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.8]
[cannot apply to next-20200805]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as do
Neither of these patches apply cleanly to net-next. The compat handling
and TLS code has been changed quite a bit lately.
ALso, you must provide a proper header "[PATCH 0/N] ..." posting for your
patch series which explains at a high level what your patch series is doing,
how it is doing it, an
If compat_{s,g}etsockopt for TLS are not implemented, the TLS layer will
never be called on a system where CONFIG_COMPAT is enabled and userspace
is 32bit. Implement both to support CONFIG_COMPAT.
Signed-off-by: Rouven Czerwinski
---
net/tls/tls_main.c | 28
1 file c
