From: Jani Nikula <jani.nikula@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/locking: fix drm_modeset_acquire_ctx kernel-doc
Date: Thu, 20 Jan 2022 14:42:57 +0200 [thread overview]
Message-ID: <87tudy8tny.fsf@intel.com> (raw)
In-Reply-To: <CAKMK7uHqf_Cn02WuZtx7m4_fe-rDKZ=cz0OoHusvEwYBGmVSiA@mail.gmail.com>
On Thu, 20 Jan 2022, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Thu, Jan 20, 2022 at 10:49 AM Jani Nikula <jani.nikula@intel.com> wrote:
>>
>> The stack_depot member was added without kernel-doc, leading to below
>> warning. Fix it.
>>
>> ./include/drm/drm_modeset_lock.h:74: warning: Function parameter or
>> member 'stack_depot' not described in 'drm_modeset_acquire_ctx'
>>
>> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
>> Fixes: cd06ab2fd48f ("drm/locking: add backtrace for locking contended locks without backoff")
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> include/drm/drm_modeset_lock.h | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/include/drm/drm_modeset_lock.h b/include/drm/drm_modeset_lock.h
>> index b84693fbd2b5..ec4f543c3d95 100644
>> --- a/include/drm/drm_modeset_lock.h
>> +++ b/include/drm/drm_modeset_lock.h
>> @@ -34,6 +34,7 @@ struct drm_modeset_lock;
>> * struct drm_modeset_acquire_ctx - locking context (see ww_acquire_ctx)
>> * @ww_ctx: base acquire ctx
>> * @contended: used internally for -EDEADLK handling
>> + * @stack_depot: used internally for contention debugging
>
> Uh would be nice to switch to the inline style, since we already have
> inline comments (just not kerneldoc). Either way:
>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Thanks for the review and testing, pushed to drm-misc-next.
BR,
Jani.
>
>
>> * @locked: list of held locks
>> * @trylock_only: trylock mode used in atomic contexts/panic notifiers
>> * @interruptible: whether interruptible locking should be used.
>> --
>> 2.30.2
>>
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/locking: fix drm_modeset_acquire_ctx kernel-doc
Date: Thu, 20 Jan 2022 14:42:57 +0200 [thread overview]
Message-ID: <87tudy8tny.fsf@intel.com> (raw)
In-Reply-To: <CAKMK7uHqf_Cn02WuZtx7m4_fe-rDKZ=cz0OoHusvEwYBGmVSiA@mail.gmail.com>
On Thu, 20 Jan 2022, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Thu, Jan 20, 2022 at 10:49 AM Jani Nikula <jani.nikula@intel.com> wrote:
>>
>> The stack_depot member was added without kernel-doc, leading to below
>> warning. Fix it.
>>
>> ./include/drm/drm_modeset_lock.h:74: warning: Function parameter or
>> member 'stack_depot' not described in 'drm_modeset_acquire_ctx'
>>
>> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
>> Fixes: cd06ab2fd48f ("drm/locking: add backtrace for locking contended locks without backoff")
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> include/drm/drm_modeset_lock.h | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/include/drm/drm_modeset_lock.h b/include/drm/drm_modeset_lock.h
>> index b84693fbd2b5..ec4f543c3d95 100644
>> --- a/include/drm/drm_modeset_lock.h
>> +++ b/include/drm/drm_modeset_lock.h
>> @@ -34,6 +34,7 @@ struct drm_modeset_lock;
>> * struct drm_modeset_acquire_ctx - locking context (see ww_acquire_ctx)
>> * @ww_ctx: base acquire ctx
>> * @contended: used internally for -EDEADLK handling
>> + * @stack_depot: used internally for contention debugging
>
> Uh would be nice to switch to the inline style, since we already have
> inline comments (just not kerneldoc). Either way:
>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Thanks for the review and testing, pushed to drm-misc-next.
BR,
Jani.
>
>
>> * @locked: list of held locks
>> * @trylock_only: trylock mode used in atomic contexts/panic notifiers
>> * @interruptible: whether interruptible locking should be used.
>> --
>> 2.30.2
>>
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-01-20 12:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 9:48 [Intel-gfx] [PATCH] drm/locking: fix drm_modeset_acquire_ctx kernel-doc Jani Nikula
2022-01-20 9:48 ` Jani Nikula
2022-01-20 10:13 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-01-20 10:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-01-20 11:29 ` [Intel-gfx] [PATCH] " Daniel Vetter
2022-01-20 11:29 ` Daniel Vetter
2022-01-20 11:48 ` [Intel-gfx] " Jani Nikula
2022-01-20 11:48 ` Jani Nikula
2022-01-20 12:42 ` Jani Nikula [this message]
2022-01-20 12:42 ` Jani Nikula
2022-01-20 11:45 ` [Intel-gfx] " Stephen Rothwell
2022-01-20 11:45 ` Stephen Rothwell
2022-01-20 12:08 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
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=87tudy8tny.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.