[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4cabce20-b5ff-4586-8492-60d2d198a13b@web.de>
Date: Wed, 31 Jan 2024 08:42:33 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Xu Yilun <yilun.xu@...ux.intel.com>, linux-fpga@...r.kernel.org,
kernel-janitors@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Moritz Fischer <mdf@...nel.org>, Tom Rix <trix@...hat.com>,
Wu Hao <hao.wu@...el.com>, Xu Yilun <yilun.xu@...el.com>,
linux-doc@...r.kernel.org
Cc: LKML <linux-kernel@...r.kernel.org>, Kunwu Chan <chentao@...inos.cn>,
Jonathan Corbet <corbet@....net>
Subject: Re: fpga: dfl: fme: Return directly after a failed devm_kasprintf()
call in fme_perf_pmu_register()
>> There are different preferences involved.
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.8-rc2#n109
>
> Ah, I mean you use 13 chars, but 12 chars is better. Also the doc
> doens't seem to enforce 12 chars, but checkpatch warns on that.
Would the specification “at least” become supported at further places
for such hash lengths?
Regards,
Markus
Powered by blists - more mailing lists