[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fad86d8c-cbf5-47cd-a144-ad803ee67417@linux.intel.com>
Date: Wed, 5 Feb 2025 13:28:49 +0200
From: Jarkko Nikula <jarkko.nikula@...ux.intel.com>
To: Mukesh Kumar Savaliya <quic_msavaliy@...cinc.com>,
Billy Tsai <billy_tsai@...eedtech.com>, alexandre.belloni@...tlin.com,
pgaj@...ence.com, miquel.raynal@...tlin.com, conor.culhane@...vaco.com,
aniketmaurya@...gle.com, Shyam-sundar.S-k@....com,
wsa+renesas@...g-engineering.com, xiaopei01@...inos.cn,
Guruvendra.Punugupati@....com, linux-i3c@...ts.infradead.org,
linux-kernel@...r.kernel.org, BMC-SW@...eedtech.com
Subject: Re: [PATCH v2 2/2] i3c: mipi-i3c-hci: Use I2C DMA-safe api
On 2/4/25 5:16 PM, Mukesh Kumar Savaliya wrote:
> Looks good to me !
>
> On 2/4/2025 2:47 PM, Billy Tsai wrote:
>> Use the i2c_get/put_dma_safe_msg_buf for I2C transfers instead of using
>> the I3C-specific API.
>>
>> Signed-off-by: Billy Tsai <billy_tsai@...eedtech.com>
> Acked-by: Mukesh Kumar Savaliya <quic_msavaliy@...cinc.com>
Reviewed-by: Jarkko Nikula <jarkko.nikula@...ux.intel.com>
Powered by blists - more mailing lists