From: Qianfeng Rong <rongqianfeng@vivo.com>
To: Nicolas Dufresne <nicolas@ndufresne.ca>,
Markus Elfring <Markus.Elfring@web.de>,
linux-media@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew-CT Chen <andrew-ct.chen@mediatek.com>,
Andrzej Pietrasiewicz <andrzejtp2010@gmail.com>,
Angelo Gioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Hans Verkuil <hverkuil@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Tiffany Lin <tiffany.lin@mediatek.com>,
Yunfei Dong <yunfei.dong@mediatek.com>
Subject: Re: media: mediatek: vcodec: use = { } instead of memset()
Date: Sat, 30 Aug 2025 15:49:01 +0800 [thread overview]
Message-ID: <7555a522-b7bf-490c-a3ce-0cebaa821ead@vivo.com> (raw)
In-Reply-To: <44aa36a8aaa7da22a4552b910ceb966b3a911691.camel@ndufresne.ca>
在 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
next prev parent reply other threads:[~2025-08-30 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-03 13:55 [PATCH] " Qianfeng Rong
2025-08-05 13:06 ` Markus Elfring
2025-08-05 13:17 ` Qianfeng Rong
2025-08-05 13:32 ` Markus Elfring
2025-08-29 18:57 ` Nicolas Dufresne
2025-08-30 7:49 ` Qianfeng Rong [this message]
2025-08-29 18:49 ` [PATCH] " Nicolas Dufresne
2025-08-30 8:25 ` Qianfeng Rong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7555a522-b7bf-490c-a3ce-0cebaa821ead@vivo.com \
--to=rongqianfeng@vivo.com \
--cc=Markus.Elfring@web.de \
--cc=andrew-ct.chen@mediatek.com \
--cc=andrzejtp2010@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=hverkuil@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=nicolas@ndufresne.ca \
--cc=tiffany.lin@mediatek.com \
--cc=yunfei.dong@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®