linux-kernel - Re: [PATCH] drm: Add directive to format code in comment

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <DBUNH9S9HCXH.SIOBPAT3U91N@brighamcampbell.com>
Date: Tue, 05 Aug 2025 10:55:30 -0600
From: "Brigham Campbell" <me@...ghamcampbell.com>
To: "Giant Sand Fans" <rampxxxx@...il.com>, "Dmitry Baryshkov"
 <dmitry.baryshkov@....qualcomm.com>
Cc: <maarten.lankhorst@...ux.intel.com>, <mripard@...nel.org>,
 <tzimmermann@...e.de>, <airlied@...il.com>, <simona@...ll.ch>,
 <dri-devel@...ts.freedesktop.org>, <linux-kernel@...r.kernel.org>,
 "dri-devel" <dri-devel-bounces@...ts.freedesktop.org>
Subject: Re: [PATCH] drm: Add directive to format code in comment

On Tue Aug 5, 2025 at 5:53 AM MDT, Giant Sand Fans wrote:
> On Tue, 5 Aug 2025 at 12:49, Dmitry Baryshkov
> <dmitry.baryshkov@....qualcomm.com> wrote:
>> Fixes tag?
>    Sorry, what do you mean?

Dmitry is looking for a tag in the body of your patch (much like your
"Signed-off-by" tag) which describes the commit which introduced the bad
behavior[1]. In this case, it looks like this block was introduced with
the incorrect kerneldoc code block formatting by commit 471920ce25d5, so
the correct Fixes tag would look like the following:

Fixes: 471920ce25d5 ("drm/gpuvm: Add locking helpers")

[1]: https://docs.kernel.org/process/submitting-patches.html#using-reported-by-tested-by-reviewed-by-suggested-by-and-fixes

Cheers,
Brigham