[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d1cc3520-4494-5c3b-e9d5-55e406831430@web.de>
Date: Thu, 27 Jul 2023 20:16:19 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: "Colin King (gmail)" <colin.i.king@...il.com>, netdev@...r.kernel.org,
kernel-janitors@...r.kernel.org, "David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
Lino Sanfilippo <LinoSanfilippo@....de>, Paolo Abeni <pabeni@...hat.com>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH next] net: ethernet: slicoss: remove redundant increment
of pointer data
>>> The pointer data is being incremented but this change to the pointer
>>> is not used afterwards. The increment is redundant and can be removed.
>>
>> Are imperative change descriptions still preferred?
>
> Hrm, I've used this style of commit message for a few thousand commits, I hope it's still fine.
>
>> See also:
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.5-rc3#n94
Will the attention grow anyhow for the desired “imperative mood”?
Regards,
Markus
Powered by blists - more mailing lists