From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-10629.protonmail.ch (mail-10629.protonmail.ch [79.135.106.29]) (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 CE0AE1DC9AB for ; Thu, 27 Mar 2025 22:20:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=79.135.106.29 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1743114029; cv=none; b=I78BkD+RPmb/udEWM/VPKBYZvnmMnHxAASCTmLW+Y/REOFMKTQ9mbqAt+sXAOVknOd0Jz5SThghrlPzClMC6nUHnuHbUvAQOsliwDvr+uKLL+kY640HGLJ3GLOscOFNp85QpeCx3rkAWqETVukP8+MrWontu+ZMAuFni9xdzRqw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1743114029; c=relaxed/simple; bh=Qljo7I+h9mG4MlHEOO+aiPISer31QeO35gqjFiAepxM=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=kjpKCjn8PgapNMtfdY01Jv//El+nmtFijPR4eHio42CKsNofCQ4WtE5vzRNV/qdrvgvm29kb8/d1n4TpI7J2/EJcAoZAh0jMtlV5t31MeVUKMe6vP4AwVtrm6ZeytJB4neRZkPxs2CkpEuAnXbEtpZP1QBSQIYR5FPPB5QJ82sg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=proton.me; spf=pass smtp.mailfrom=proton.me; dkim=pass (2048-bit key) header.d=proton.me header.i=@proton.me header.b=bgOvkHzO; arc=none smtp.client-ip=79.135.106.29 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=proton.me Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=proton.me Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=proton.me header.i=@proton.me header.b="bgOvkHzO" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me; s=protonmail; t=1743114025; x=1743373225; bh=/KpF8fnzMUOMSpfBWmOCjM1gtE658ydJ+q9j6uReSoM=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=bgOvkHzOTobtMKvnsusEfRFL3kMDcXd8nj9L4IYcosBjFRogjLbZmEd83oC/vstDA stp6xW4FvEyyk8PciZdjO40vw4daITYpq420TIStPGNc/geKS6nRcPH7JlHcy27M0C KHSNUbkurvwVKNuX+wVUCdcRRHlf1X2Gv3Fi3K21+yS8PoW6paxie/R6SqFe1IUjU+ F4oSW5eys91v7XosivRomzeVG9TiwG6R5yvBL9vaZf9PzhtlJD3179vUMm8P3CNp2F P1Ur5nK8uRoM7Ac/PAIjEipcg2J1SgSnkShCZUgVaBqBV/fKsCvm/7qt5yM2tj3sJB GHJw3yfSaaekw== Date: Thu, 27 Mar 2025 22:20:21 +0000 To: Abdiel Janulgue , a.hindborg@kernel.org, ojeda@kernel.org From: Benno Lossin Cc: Danilo Krummrich , Daniel Almeida , Robin Murphy , Alex Gaynor , Boqun Feng , Gary Guo , =?utf-8?Q?Bj=C3=B6rn_Roy_Baron?= , Alice Ryhl , Trevor Gross , "open list:DMA MAPPING HELPERS DEVICE DRIVER API [RUST]" , Marek Szyprowski , "open list:DMA MAPPING HELPERS" , open list Subject: Re: [PATCH 1/3] rust: dma: be consistent in using the `coherent` nomenclature Message-ID: In-Reply-To: <20250326201230.3193329-2-abdiel.janulgue@gmail.com> References: <20250326201230.3193329-1-abdiel.janulgue@gmail.com> <20250326201230.3193329-2-abdiel.janulgue@gmail.com> Feedback-ID: 71780778:user:proton X-Pm-Message-ID: 119eb6d0acb9c7ccaedb6faf72deb47a1ff902d7 Precedence: bulk X-Mailing-List: rust-for-linux@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Wed Mar 26, 2025 at 9:11 PM CET, Abdiel Janulgue wrote: > In the kernel, `consistent` and `coherent` are used interchangeably for > the region described in this api. Stick with `coherent` nomenclature > to show that dma_alloc_coherent() is being used. > > Signed-off-by: Abdiel Janulgue Reviewed-by: Benno Lossin --- Cheers, Benno > --- > rust/kernel/dma.rs | 12 ++++++------ > 1 file changed, 6 insertions(+), 6 deletions(-)