[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<PAXPR04MB8459999EAA5A46E80CE6AFD088AD2@PAXPR04MB8459.eurprd04.prod.outlook.com>
Date: Fri, 19 Jul 2024 05:51:24 +0000
From: Peng Fan <peng.fan@....com>
To: Mathieu Poirier <mathieu.poirier@...aro.org>, "Peng Fan (OSS)"
<peng.fan@....nxp.com>
CC: Bjorn Andersson <andersson@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>, Pengutronix Kernel Team
<kernel@...gutronix.de>, Fabio Estevam <festevam@...il.com>, Hongxing Zhu
<hongxing.zhu@....com>, "linux-remoteproc@...r.kernel.org"
<linux-remoteproc@...r.kernel.org>, "imx@...ts.linux.dev"
<imx@...ts.linux.dev>, "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, Jacky Bai <ping.bai@....com>
Subject: RE: [PATCH 5/6] remoteproc: imx_rproc: allow tx_block to be set
> Subject: Re: [PATCH 5/6] remoteproc: imx_rproc: allow tx_block to be
> set
>
> On Fri, Jul 12, 2024 at 04:34:58PM +0800, Peng Fan (OSS) wrote:
> > From: Peng Fan <peng.fan@....com>
> >
> > Current tx_block is set to true, but there is case that no need to
> > wait response. Linux just needs to send data to remote processor, so
> > let's allow tx_block could be set to false.
>
> Ok, maybe - but this patch doesn't use the new functionality, i.e
> nothing changes.
>
Will update commit log to add:
"No functional changes"
Thanks,
Peng.
Powered by blists - more mailing lists