Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <f27d55ee29ad1f78e5ad47e3c63b6021d6df6895.camel@pengutronix.de>
Subject: Re: [PATCH 1/2] net: tls: add compat for get/setsockopt
From:   Rouven Czerwinski <r.czerwinski@pengutronix.de>
To:     David Miller <davem@davemloft.net>
Cc:     borisp@mellanox.com, aviadye@mellanox.com,
        john.fastabend@gmail.com, daniel@iogearbox.net, kuba@kernel.org,
        netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Date:   Thu, 06 Aug 2020 08:41:50 +0200
In-Reply-To: <20200805.174546.1898874545402901800.davem@davemloft.net>
References: <20200805122501.4856-1-r.czerwinski@pengutronix.de>
         <20200805.174546.1898874545402901800.davem@davemloft.net>
Organization: Pengutronix e.K.
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.4 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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 "[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, and why it is doing it that way.

Since I'm now down to one patch I'll forgo the cover letter and expand
the commit message.

Thanks for the explanation,
Rouven