From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.zeus03.de (zeus03.de [194.117.254.33]) (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 B0C8818AE2 for ; Tue, 21 Jan 2025 22:18:52 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=194.117.254.33 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737497941; cv=none; b=jFLqVI3lwNhMrjX//myffpVKmaapdkNMuf8a+4TDmRD7LBSMAyAFdX3IE5z6DWiwiJPRPV80Pd7PJ/uFG1+wB3tjHJD0J4OTOeSsIjd41zruoYNrFhe2LZwdtCp7U4BJabIK5ZDRh8CCjoTmGMO7liCH/XNg+zul56GUZF4wppc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737497941; c=relaxed/simple; bh=vF22TcZDK3gDIMGnmR/qxjIwejEAyGibsrd8qdp1Aik=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Az7OKpj6rYxC+Vn1cWO8A1qNSGy7m/9q0psQA9t6YMFabHC5qC/UF8BM0U3g1Ja3g1CriNUUJ3FK7l28LnEktvRQ1Zy6rBMmZWbYhaSKtuAj6IPtK8ygbNw0N4oIMAXT5s33YihSO4gxIwBz5OlXAm/P9uahBn+ZdORWlE5IkFI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com; spf=pass smtp.mailfrom=sang-engineering.com; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b=IF8ZHHBL; arc=none smtp.client-ip=194.117.254.33 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b="IF8ZHHBL" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= sang-engineering.com; h=date:from:to:cc:subject:message-id :references:mime-version:content-type:in-reply-to; s=k1; bh=vF22 TcZDK3gDIMGnmR/qxjIwejEAyGibsrd8qdp1Aik=; b=IF8ZHHBLYXWy0iEGQTM2 tllDDtLZRFbjoG81kYUKsAk9B3IkV4YHYmXN2mukoFnrOTGnCxxWjZd7Wvo5CJSk glOLeN6Jm7g/JmRtliO11zCYWD5FO+K441M681itQRLaZR2zJNUDWBt0sCS++6Es 3lVcnr7GyqfjXNC5EOVROpZwgRMuT7qdB+Y8xbw9H7y1C3p7X05Bdq0MbkcKQ79P k/OKegc8yTMCxlqP2Fg+T00aFyBXD0PcfuiOVLAj9fmk+1GPj+rrXGbWgF6QW8iH 7VaYC0DuBne3hm6rKYvD7pP0l2OCBcBDCNirjEwkB506AnUaUb5DqxDpRMPugSmH Zg== Received: (qmail 2648197 invoked from network); 21 Jan 2025 23:18:43 +0100 Received: by mail.zeus03.de with ESMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 21 Jan 2025 23:18:43 +0100 X-UD-Smtp-Session: l3s3148p1@I6OIwj4sOsYujnvm Date: Tue, 21 Jan 2025 23:18:43 +0100 From: Wolfram Sang To: Billy Tsai Cc: alexandre.belloni@bootlin.com, pgaj@cadence.com, miquel.raynal@bootlin.com, conor.culhane@silvaco.com, aniketmaurya@google.com, Shyam-sundar.S-k@amd.com, jarkko.nikula@linux.intel.com, xiaopei01@kylinos.cn, Guruvendra.Punugupati@amd.com, linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v1 1/2] i3c: Remove the const qualifier from i2c_msg pointer in i2c_xfers API Message-ID: Mail-Followup-To: Wolfram Sang , Billy Tsai , alexandre.belloni@bootlin.com, pgaj@cadence.com, miquel.raynal@bootlin.com, conor.culhane@silvaco.com, aniketmaurya@google.com, Shyam-sundar.S-k@amd.com, jarkko.nikula@linux.intel.com, xiaopei01@kylinos.cn, Guruvendra.Punugupati@amd.com, linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org References: <20250121110756.214714-1-billy_tsai@aspeedtech.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="5F1Lnzx5VCOxxxIV" Content-Disposition: inline In-Reply-To: <20250121110756.214714-1-billy_tsai@aspeedtech.com> --5F1Lnzx5VCOxxxIV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 21, 2025 at 07:07:55PM +0800, Billy Tsai wrote: > The change is necessary to enable the use of the > `i2c_get_dma_safe_msg_buf()` API, which requires a non-const > `struct i2c_msg *` to operate. The `i2c_get_dma_safe_msg_buf()` function > ensures safe handling of I2C messages when using DMA, making it essential > for scenarios where DMA transfers are involved. By removing the `const` > qualifier, this patch allows drivers to prepare and manage DMA-safe > buffers directly. >=20 > Signed-off-by: Billy Tsai Makes sense to me: Reviewed-by: Wolfram Sang --5F1Lnzx5VCOxxxIV Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEOZGx6rniZ1Gk92RdFA3kzBSgKbYFAmeQHUMACgkQFA3kzBSg KbaCVg//Y+R5V62Gbxfxz0ZS264Llbf4olfsib8/cbhlY9NHAQ2mg75Agj5xpL5r bLbcGgWTBTfCBnUPCOPRUz4vcEBbpW+oxjGI7cdeMBMyjRkkIJ3tu6gC0fFCUfq9 uKEMwp+KYEQcNpH+Y8hlq9wwbOth1XkOajp0+AsesBADLGd0BNF4sOk35jYz/a2U /gxL2Ys1ePWvUEjsYhYb0Q6GIrnNh9YL5yQLtIv75MzpSX5AJe15QD4sPhCA6O8Z rqKLFP2D4YnTRjmInCNF7ej62vk+J3OyuthmlSt/lEoJkmssAOJeE8HNW46ObseQ rKxYKnkH/3Z/XKjWFlIIfeonl25uyLTyP0NtL1gDmZwn0XQcIjmGbnJzo2ZRs/mS npVaYtGtRcDyaemMXCV0D4ZQDbcwjeAmA2cKz/bgqbLrORfIb5RoZ1VfUPyxB1AU qoTbvwG6jwF45Md46fx2IRu52O9ekQzTFrwwDOV2zYua5jnJUNiBaGAYdipPh65V 7KP9dwFt+MKSij8eQhwUwDe4uTXtc+FozvoD4ZV0VWojiYigABvnRW4Qi/2AtDu/ dXOv2ks5hYAVwOUWlxpu4KYbkmSYKPFfw9WG1aiiK2xJU38nch/kwScw218f/YSv PdgqYCssHR8JmHZNKddc9vvQK/cKsri3fyQV4dQaHZvRTMiJi0M= =5Fo1 -----END PGP SIGNATURE----- --5F1Lnzx5VCOxxxIV--