[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ff6292c5-037e-4e40-af33-1339812965eb@web.de>
Date: Wed, 26 Jun 2024 13:15:02 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Ma Ke <make24@...as.ac.cn>, dmaengine@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, imx@...ts.linux.dev,
kernel@...gutronix.de, Fabio Estevam <festevam@...il.com>,
Sascha Hauer <s.hauer@...gutronix.de>, Shawn Guo <shawnguo@...nel.org>,
Vinod Koul <vkoul@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] dmaengine: mxs-dma: Add check for dma_set_max_seg_size in
mxs_dma_probe()
> As the possible failure of the dma_set_max_seg_size(), we should better
> check the return value of the dma_set_max_seg_size().
Please avoid the repetition of a function name in such a change description.
Can it be improved with a corresponding imperative wording?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.10-rc5#n94
Regards,
Markus
Powered by blists - more mailing lists