From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id CE707C4332F for ; Fri, 2 Dec 2022 19:52:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234433AbiLBTwS (ORCPT ); Fri, 2 Dec 2022 14:52:18 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54214 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234000AbiLBTwR (ORCPT ); Fri, 2 Dec 2022 14:52:17 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B9B04EE94A for ; Fri, 2 Dec 2022 11:52:16 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 6B7CEB82279 for ; Fri, 2 Dec 2022 19:52:15 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id F1609C433D6; Fri, 2 Dec 2022 19:52:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1670010734; bh=LPRdq9V5F9HtS6TkON8cv2elgG+YwRH+FkbNPqRMrOE=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=bciDORSAdFY1ERPFH5j1Tc+yoT4woQWToRP5IXXh4yFsAPP5HtRIpWnjy32JJpsDp yINstEaTnaW9eRaAu+BlVa57/KMqMVh2OO9DhtaLKPjVsnEPJppn78BXRXyis+nbl2 iR2ZquJ3qsxai6E02T1MKDbGlPKbJj2Hydwxl0SlZ5NRlg32yNBbo2T0fuIst1QyMy PJbknEsEuC6A9eZZbHsU8FTvmHYz0pb27unaYaz3zLsoYACk6UwIvizBngOBvjaQnM kJLwLKJrX5WfecnFcm0jPVr6zD9ij8ysemr5Fjke21BF02zaPxIqGMPnka9qznQTUI TIPOCFpB4ygRA== Date: Fri, 2 Dec 2022 11:52:13 -0800 From: Jakub Kicinski To: Leon Romanovsky Cc: Steffen Klassert , "David S. Miller" , Eric Dumazet , Herbert Xu , netdev@vger.kernel.org, Bharat Bhushan Subject: Re: [PATCH xfrm-next v9 0/8] Extend XFRM core to allow packet offload configuration Message-ID: <20221202115213.0055aa4a@kernel.org> In-Reply-To: References: <20221202094243.GA704954@gauss3.secunet.de> <20221202101000.0ece5e81@kernel.org> <20221202112607.5c55033a@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Fri, 2 Dec 2022 21:45:47 +0200 Leon Romanovsky wrote: > > More of a question of whether we can reasonably expect to merge all > > the driver code in a single release cycle. If not then piecemeal > > merging is indeed inevitable. But if Steffen is happy with the core > > changes whether they are in tree for 6.2 or not should not matter. > > An upstream user can't access them anyway, it'd only matter to an > > out-of-tree consumer. > > > > That's just my 2 cents, whatever Steffen prefers matters most. > > There are no out-of-tree users, just ton of mlx5 refactoring to natively > support packet offload. 30 patches is just two series, that's mergeable in a week. You know, if it builds cleanly.. :S Dunno.