From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 51F34101CF for ; Mon, 24 Jul 2023 19:52:50 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id CF1BAC433C7; Mon, 24 Jul 2023 19:52:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1690228370; bh=kP9LFVtRs+Ccd680KNMd/rso4IU7MRNI/s2gQcTn8K8=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=qgSBdgWOM6O8dH0osz4XFlKo9jOWZ6gGAyBSleFY0cnmRksLenDlC26PBXmkn475s 6iD9hEfArzfCxkcjLk6q0oP5NLIVXeUc8djvArC2em9TW/KP4ztJWX1wkoP9sYiJQm iyfLYlYGH2BpSXP6DDFec83DGL9tVYgF6vaJ98nU83TfzlZydgPZ+VBxsNOIyimlac KxXtaEI6gaLpndVzh/s49gopZSdIqPf98IKnG7Kumg+aTQ3BzgNfIwb3L/obEFkYuu mIf+pf6ozPuCmzGRk6NJt7GF0dMBc9ijV01zcbks02tkqYqraJgLm4sr6jIIbg7E/3 14s25cH8SkrCg== Date: Mon, 24 Jul 2023 12:52:49 -0700 From: Jakub Kicinski To: Sagi Grimberg Cc: Hannes Reinecke , Christoph Hellwig , Keith Busch , linux-nvme@lists.infradead.org, Eric Dumazet , Paolo Abeni , netdev@vger.kernel.org Subject: Re: [PATCHv8 0/6] net/tls: fixes for NVMe-over-TLS Message-ID: <20230724125249.319241b7@kernel.org> In-Reply-To: References: <20230721143523.56906-1-hare@suse.de> <20230721190026.25d2f0a5@kernel.org> <3e83c1dd-99bd-4dbd-2f83-4008e7059cfa@suse.de> <9f37941c-b265-7f28-ebec-76c04804b684@grimberg.me> <20230724123546.70775e77@kernel.org> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Mon, 24 Jul 2023 22:44:49 +0300 Sagi Grimberg wrote: > > I'm probably using the wrong word. I mean a branch based on -rc3 that's > > not going to get rebased so the commits IDs match and we can both pull > > it in. Not stable as in Greg KH. > > Are you aiming this for 6.5 ? We are unlikely to get the nvme bits in > this round. I also don't think there is a conflict so the nvme bits > can go in for 6.6 and later the nvme tree will pull the tls updates. Great, less work :) Let's see a v9 with the flushing improved and we'll apply to net-next directly.