[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CABPJ0vgOMQk8aBUvtR5FhXzUJ1itF_mvXYiTw9gG8+0=5ipkyQ@mail.gmail.com>
Date: Tue, 5 Aug 2025 19:55:22 +0200
From: Giant Sand Fans <rampxxxx@...il.com>
To: Brigham Campbell <me@...ghamcampbell.com>
Cc: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>, 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, 5 Aug 2025 at 18:55, Brigham Campbell <me@...ghamcampbell.com> wrote:
>
> 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:
oh, thank you .
>
> Fixes: 471920ce25d5 ("drm/gpuvm: Add locking helpers")
Yes, this is it.
>
> [1]: https://docs.kernel.org/process/submitting-patches.html#using-reported-by-tested-by-reviewed-by-suggested-by-and-fixes
>
> Cheers,
> Brigham
Powered by blists - more mailing lists