Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Simona Vetter <simona.vetter@ffwll.ch>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Intel Graphics" <intel-gfx@lists.freedesktop.org>,
	DRI <dri-devel@lists.freedesktop.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the drm-misc tree
Date: Thu, 10 Oct 2024 16:09:42 +1100	[thread overview]
Message-ID: <20241010160942.192caf60@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 529 bytes --]

Hi all,

After merging the drm-misc tree, today's linux-next build (htmldocs)
produced these warnings:

include/drm/ttm/ttm_device.h:255: warning: Incorrect use of kernel-doc format:          * @unevictable Buffer objects which are pinned or swapped and as such
include/drm/ttm/ttm_device.h:270: warning: Function parameter or struct member 'unevictable' not described in 'ttm_device'

Introduced by commit

  fc5d96670eb2 ("drm/ttm: Move swapped objects off the manager's LRU list")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-10-10  5:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10  5:09 Stephen Rothwell [this message]
2024-10-10  8:35 ` linux-next: build warnings after merge of the drm-misc tree Thomas Hellström
  -- strict thread matches above, loose matches on Subject: below --
2025-12-16  0:56 Stephen Rothwell
2025-11-10  2:50 Stephen Rothwell
2025-11-10  2:24 Stephen Rothwell
2025-11-05  5:18 Stephen Rothwell
2025-06-18  5:13 Stephen Rothwell
2025-06-11  4:09 Stephen Rothwell
2025-08-01  4:34 ` Stephen Rothwell
2025-08-01 11:04   ` Dmitry Baryshkov
2025-01-06  6:46 Stephen Rothwell
2025-01-14  5:43 ` Stephen Rothwell
2025-01-14 11:40   ` Dmitry Baryshkov
2025-01-14 12:06     ` Stephen Rothwell
2024-12-20  4:42 Stephen Rothwell
2025-01-14  5:41 ` Stephen Rothwell
2025-01-16 10:34   ` Tomi Valkeinen
2025-01-16 11:50     ` Maxime Ripard
2024-10-10  5:04 Stephen Rothwell
2024-08-01  6:03 Stephen Rothwell
2024-04-16  7:31 Stephen Rothwell
2024-04-16  8:25 ` Jocelyn Falempe
2024-03-26  5:12 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=20241010160942.192caf60@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --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=simona.vetter@ffwll.ch \
    --cc=thomas.hellstrom@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox