From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.16]) (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 514BE334688 for ; Thu, 5 Mar 2026 16:32:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772728370; cv=none; b=Lav41+odlEzxW5MQ8QV8eeNduIIJLJiw8Z8DBMPWmfhef+E3Ib21Z2ugUv9rQFpwhdVnfTOUCZ2c8yBHOZ2oPdFVyktz3d55EppLvKKxxHCtHnFhMWtbZISclziwPCy5FuYLI4FCSZUp7z1VV3Aet3ltF8SEJYvd8RuwcrNjlq0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772728370; c=relaxed/simple; bh=/j3JWFGvhOct2mNLMxpVlx3tr4B/fG6y4LhAshf9ybM=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=hOxioZNdvJpWJXiNrzUZ8o8owG6RevCBICTzjihfuu5B/mgIGgY/XrKW2TpDz7tsUmRxERuTl/yAn+7jEbcCYfvQckY+2rUQAs3mbsC+rkqycWCT0Wuflb+LwJwunik6vJF3wIbZisqeJdGf1Csq5TAU6fYYjRI/UOM/zda+2g0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=WqekTMVt; arc=none smtp.client-ip=198.175.65.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="WqekTMVt" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1772728369; x=1804264369; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=/j3JWFGvhOct2mNLMxpVlx3tr4B/fG6y4LhAshf9ybM=; b=WqekTMVtpJ5hye/0lEeKBGgk/KDlwPuMhDCpw6gaASJFlpMlHoZ2t8X6 lUkkn0P3Yf0mJX7GMMGdHXTU4PHU9L3kHMwBdB9QaRasZWDHbYfCCWuOv cdZEkOEP5VeFjfUVrdSmvKexgSAnzT4ndsyLSCdL4lBUxEMKyhbgmuyUl JmOf1Xgj4Vy1zWfLWvhVpG7hxHrbzEaXC7vQ4ad1+p/fyvnFGUxJC2SGn Tadu9wZ7H8wCpj9BczNfi+rwrgSZ0mnwmeAVcoQ8lqyAkyWqKnLUrXLzk sysRyTlDfMhKygwW7bxEWmdXMYjlPxDd7rHlMlOjLP3J/3lqLDrkIeU86 w==; X-CSE-ConnectionGUID: enXIRw50TTyB6p5VpgOT8w== X-CSE-MsgGUID: QHNM9+SLRvK/r3Cf12MaUw== X-IronPort-AV: E=McAfee;i="6800,10657,11720"; a="74013264" X-IronPort-AV: E=Sophos;i="6.23,103,1770624000"; d="scan'208";a="74013264" Received: from orviesa002.jf.intel.com ([10.64.159.142]) by orvoesa108.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Mar 2026 08:32:49 -0800 X-CSE-ConnectionGUID: j7tiy0gGT32b/267iuzf/A== X-CSE-MsgGUID: 01QCRghWTeW0NFGR6vwU9Q== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.23,103,1770624000"; d="scan'208";a="249193182" Received: from rchatre-mobl4.amr.corp.intel.com (HELO [10.125.109.42]) ([10.125.109.42]) by orviesa002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Mar 2026 08:32:49 -0800 Message-ID: <17cdfa38-16d5-49cc-ac61-20b606a4308b@intel.com> Date: Thu, 5 Mar 2026 09:32:47 -0700 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 0/2] NTB: Allow drivers to provide DMA mapping device To: Koichiro Den , Jon Mason Cc: Allen Hubbe , Frank Li , Niklas Cassel , ntb@lists.linux.dev, linux-kernel@vger.kernel.org References: <20260302144522.750620-1-den@valinux.co.jp> <3ddba488-6577-4f04-8a50-d64850b7cc5b@intel.com> <2jb2u6hm2u7dcmexzhi45kaclgfysfhr3nxomvqfnxbp5dlwfx@dt7hraa6u52v> <244af3c1-21f4-4023-b465-0ccd85e1eb79@intel.com> Content-Language: en-US From: Dave Jiang In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 3/4/26 8:23 PM, Koichiro Den wrote: > On Wed, Mar 04, 2026 at 09:53:42AM -0700, Dave Jiang wrote: >> Probably should include it with this series if it's small. Having the user with new code is usually preferred. > > I thought that, since the vNTB patch wouldn't work until the NTB changes are in, > asking both the NTB and PCI EP maintainers to coordinate the apply order might > be a bit awkward. > > That said, if preferable, I can include the vNTB change in this series and > explicitly ask the PCI EP maintainers not to pick up (new) Patch 3 until the NTB > maintainers have acked and applied Patch 1-2. Given that most of the patches are PCI EP, I think with acks from NTB, the whole thing can go through PCI EP if that works for you. DJ > > I'd also appreciate any thoughts from Jon or others on this (i.e. keeping > this series NTB tree-only vs. including the vNTB change as well), as well > as any feedback on this v1 series itself. > > P.S. I sent a corrected code snippet a few minutes after my original post. The > original snippet above was wrong, as it would violate the kernel-doc in Patch 1: > > "Drivers that implement .get_dma_dev() must return a non-NULL pointer." > > Best regards, > Koichiro > >>