From: Jani Nikula <jani.nikula@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the drm-misc tree
Date: Thu, 20 Jan 2022 11:50:27 +0200 [thread overview]
Message-ID: <87y23aag7w.fsf@intel.com> (raw)
In-Reply-To: <20220120141951.30609ba3@canb.auug.org.au>
On Thu, 20 Jan 2022, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> On Fri, 15 Oct 2021 21:01:04 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> After merging the drm-misc tree, today's linux-next build (htmldocs)
>> produced this warning:
>>
>> include/drm/drm_modeset_lock.h:74: warning: Function parameter or member 'stack_depot' not described in 'drm_modeset_acquire_ctx'
>>
>> Introduced by commit
>>
>> cd06ab2fd48f ("drm/locking: add backtrace for locking contended locks without backoff")
>
> I am still getting this warning.
Sorry about that, patch on the list [1].
Thanks,
Jani.
[1] https://patchwork.freedesktop.org/patch/msgid/20220120094856.3004147-1-jani.nikula@intel.com
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the drm-misc tree
Date: Thu, 20 Jan 2022 11:50:27 +0200 [thread overview]
Message-ID: <87y23aag7w.fsf@intel.com> (raw)
In-Reply-To: <20220120141951.30609ba3@canb.auug.org.au>
On Thu, 20 Jan 2022, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> On Fri, 15 Oct 2021 21:01:04 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> After merging the drm-misc tree, today's linux-next build (htmldocs)
>> produced this warning:
>>
>> include/drm/drm_modeset_lock.h:74: warning: Function parameter or member 'stack_depot' not described in 'drm_modeset_acquire_ctx'
>>
>> Introduced by commit
>>
>> cd06ab2fd48f ("drm/locking: add backtrace for locking contended locks without backoff")
>
> I am still getting this warning.
Sorry about that, patch on the list [1].
Thanks,
Jani.
[1] https://patchwork.freedesktop.org/patch/msgid/20220120094856.3004147-1-jani.nikula@intel.com
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] linux-next: build warning after merge of the drm-misc tree
Date: Thu, 20 Jan 2022 11:50:27 +0200 [thread overview]
Message-ID: <87y23aag7w.fsf@intel.com> (raw)
In-Reply-To: <20220120141951.30609ba3@canb.auug.org.au>
On Thu, 20 Jan 2022, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> On Fri, 15 Oct 2021 21:01:04 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> After merging the drm-misc tree, today's linux-next build (htmldocs)
>> produced this warning:
>>
>> include/drm/drm_modeset_lock.h:74: warning: Function parameter or member 'stack_depot' not described in 'drm_modeset_acquire_ctx'
>>
>> Introduced by commit
>>
>> cd06ab2fd48f ("drm/locking: add backtrace for locking contended locks without backoff")
>
> I am still getting this warning.
Sorry about that, patch on the list [1].
Thanks,
Jani.
[1] https://patchwork.freedesktop.org/patch/msgid/20220120094856.3004147-1-jani.nikula@intel.com
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-01-20 9:50 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 10:01 linux-next: build warning after merge of the drm-misc tree Stephen Rothwell
2021-10-15 10:01 ` [Intel-gfx] " Stephen Rothwell
2022-01-20 3:19 ` Stephen Rothwell
2022-01-20 3:19 ` [Intel-gfx] " Stephen Rothwell
2022-01-20 3:19 ` Stephen Rothwell
2022-01-20 9:50 ` Jani Nikula [this message]
2022-01-20 9:50 ` [Intel-gfx] " Jani Nikula
2022-01-20 9:50 ` Jani Nikula
-- strict thread matches above, loose matches on Subject: below --
2024-04-12 6:58 Stephen Rothwell
2024-04-12 7:01 ` Stephen Rothwell
2024-03-26 5:01 Stephen Rothwell
2023-10-05 3:56 Stephen Rothwell
2023-10-05 3:56 ` Stephen Rothwell
2023-09-26 5:07 Stephen Rothwell
2023-09-26 5:07 ` Stephen Rothwell
2023-09-26 10:56 ` Danilo Krummrich
2023-08-07 1:28 Stephen Rothwell
2023-08-07 1:28 ` Stephen Rothwell
2023-08-02 4:21 Stephen Rothwell
2023-08-02 4:21 ` Stephen Rothwell
2023-08-02 14:49 ` Doug Anderson
2023-08-02 14:49 ` Doug Anderson
2023-08-02 4:17 Stephen Rothwell
2023-08-02 4:17 ` Stephen Rothwell
2023-08-02 14:49 ` Doug Anderson
2023-08-02 14:49 ` Doug Anderson
2022-11-07 3:38 Stephen Rothwell
2022-11-07 3:38 ` Stephen Rothwell
2022-04-20 6:24 Stephen Rothwell
2022-04-20 6:24 ` Stephen Rothwell
2022-04-06 5:50 Stephen Rothwell
2022-04-06 5:50 ` Stephen Rothwell
2022-04-13 0:04 ` Stephen Rothwell
2022-04-13 0:04 ` Stephen Rothwell
2022-04-13 8:23 ` Daniel Vetter
2022-04-13 8:23 ` Daniel Vetter
2022-04-13 8:24 ` Christian König
2022-04-06 0:58 Stephen Rothwell
2022-04-06 0:58 ` Stephen Rothwell
2022-04-06 1:45 ` Marek Vasut
2022-04-06 1:45 ` Marek Vasut
2021-11-17 2:49 Stephen Rothwell
2021-11-17 2:49 ` Stephen Rothwell
2022-01-20 3:26 ` Stephen Rothwell
2022-01-20 3:26 ` Stephen Rothwell
2022-03-02 1:31 ` Stephen Rothwell
2022-03-02 1:31 ` Stephen Rothwell
2022-03-02 3:26 ` Andrey Grodzovsky
2022-03-02 3:26 ` Andrey Grodzovsky
2022-03-02 5:02 ` Stephen Rothwell
2022-03-02 5:02 ` Stephen Rothwell
2022-03-27 23:56 ` Stephen Rothwell
2022-03-27 23:56 ` Stephen Rothwell
2022-03-28 13:26 ` Andrey Grodzovsky
2022-03-28 13:26 ` Andrey Grodzovsky
2021-10-15 9:54 Stephen Rothwell
2022-01-20 3:18 ` Stephen Rothwell
2022-01-20 3:18 ` Stephen Rothwell
2022-01-21 10:42 ` Hans de Goede
2022-01-21 10:42 ` Hans de Goede
2021-10-05 7:59 Stephen Rothwell
2021-10-05 8:23 ` Christian König
2021-10-21 1:27 ` Stephen Rothwell
2021-11-01 9:17 ` Stephen Rothwell
2021-11-01 9:17 ` Stephen Rothwell
2021-09-27 5:44 Stephen Rothwell
2021-09-27 14:42 ` Doug Anderson
2021-09-27 14:42 ` Doug Anderson
2021-02-08 12:39 Stephen Rothwell
2021-02-08 12:39 ` Stephen Rothwell
2020-12-09 10:02 Stephen Rothwell
2020-12-09 10:02 ` Stephen Rothwell
2020-12-09 16:10 ` Luben Tuikov
2020-12-09 16:10 ` Luben Tuikov
2020-11-18 5:23 Stephen Rothwell
2020-11-18 5:23 ` Stephen Rothwell
2020-11-10 2:29 Stephen Rothwell
2020-11-10 2:29 ` Stephen Rothwell
2020-11-02 1:46 Stephen Rothwell
2020-11-02 1:46 ` Stephen Rothwell
2020-11-02 8:05 ` Boris Brezillon
2020-11-02 8:05 ` Boris Brezillon
2020-09-08 4:15 Stephen Rothwell
2020-09-08 4:15 ` Stephen Rothwell
2020-05-07 3:04 Stephen Rothwell
2020-05-07 3:04 ` Stephen Rothwell
2019-10-10 23:45 Stephen Rothwell
2019-08-16 3:31 Stephen Rothwell
2019-08-16 4:48 ` Sam Ravnborg
2019-08-16 6:23 ` Daniel Vetter
2019-08-16 9:47 ` Laurent Pinchart
2019-08-16 12:24 ` Laurent Pinchart
2019-02-08 1:32 Stephen Rothwell
2019-02-08 9:29 ` Maxime Ripard
2019-01-07 23:58 Stephen Rothwell
2019-01-07 23:58 ` Stephen Rothwell
2018-07-12 1:51 Stephen Rothwell
2017-04-05 0:41 Stephen Rothwell
2017-04-05 0:41 ` Stephen Rothwell
2017-04-05 7:26 ` Neil Armstrong
2017-04-05 7:26 ` Neil Armstrong
2017-03-10 0:03 Stephen Rothwell
2016-11-22 1:45 Stephen Rothwell
2016-06-03 1:09 Stephen Rothwell
2016-06-03 1:09 ` Stephen Rothwell
2015-09-23 3:20 Stephen Rothwell
2015-09-23 3:20 ` Stephen Rothwell
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=87y23aag7w.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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.