[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7555a522-b7bf-490c-a3ce-0cebaa821ead@vivo.com>
Date: Sat, 30 Aug 2025 15:49:01 +0800
From: Qianfeng Rong <rongqianfeng@...o.com>
To: Nicolas Dufresne <nicolas@...fresne.ca>,
Markus Elfring <Markus.Elfring@....de>, linux-media@...r.kernel.org,
linux-mediatek@...ts.infradead.org, linux-arm-kernel@...ts.infradead.org
Cc: LKML <linux-kernel@...r.kernel.org>,
Andrew-CT Chen <andrew-ct.chen@...iatek.com>,
Andrzej Pietrasiewicz <andrzejtp2010@...il.com>,
Angelo Gioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
Hans Verkuil <hverkuil@...nel.org>, Matthias Brugger
<matthias.bgg@...il.com>, Mauro Carvalho Chehab <mchehab@...nel.org>,
Neil Armstrong <neil.armstrong@...aro.org>,
Tiffany Lin <tiffany.lin@...iatek.com>,
Yunfei Dong <yunfei.dong@...iatek.com>
Subject: Re: media: mediatek: vcodec: use = { } instead of memset()
在 2025/8/30 2:57, Nicolas Dufresne 写道:
> Le mardi 05 août 2025 à 15:32 +0200, Markus Elfring a écrit :
>>>> …
>>>>> This patch converts …
>>>> See also once more:
>>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.16#n94
>>> I don't think your point is a problem here. …
>> Will any contributors care more for the usage of imperative mood
>> also according to improved change descriptions?
> Markus, its the way you review that does not work. I'm far from perfect, so I
> don't normally give any lesson, but I've seen this this exact interaction too
> often. Try suggesting a rephrase instead.
>
> Qianfeng Rong, the suggestion is that:
>
> This patch converts memset() to = { }, thereby:
>
> Can be rephrased:
>
> Converts memset() to = { }, thereby:
>
> Also, some maintainers may prefer if you swap the two paraphs, so you get to the
> point first, and give context in the remaining. Processing tones of patches is
> improved if you don't have to read the entire message to understand what the
> patch is doing at high level.
Describing patches and making them easily understandable often gives me
a headache. Your suggestion has been particularly helpful, and it has
made me realize that this task is not as difficult as I imagined:
dividing the commit message into two sections. The first section
describes what the main changes are, and the second section provides
background information and motivation.
Thank you very much.
Best regards,
Qianfeng
>
> regards,
> Nicolas
Powered by blists - more mailing lists