All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	DRI <dri-devel@lists.freedesktop.org>
Cc: Jani Nikula <jani.nikula@intel.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warnings after merge of the drm-misc tree
Date: Wed, 6 Apr 2022 15:44:31 +1000	[thread overview]
Message-ID: <20220406154431.567414c3@canb.auug.org.au> (raw)

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

Hi all,

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

drivers/gpu/drm/drm_edid.c:1589: warning: Function parameter or member '_edid' not described in 'drm_edid_header_is_valid'
drivers/gpu/drm/drm_edid.c:1589: warning: Excess function parameter 'raw_edid' description in 'drm_edid_header_is_valid'
drivers/gpu/drm/drm_edid.c:1737: warning: Function parameter or member '_block' not described in 'drm_edid_block_valid'
drivers/gpu/drm/drm_edid.c:1737: warning: Excess function parameter 'raw_edid' description in 'drm_edid_block_valid'

Introduced by commits

  6d987ddd6843 ("drm/edid: make drm_edid_header_is_valid() accept void pointer")
  1f221284ab63 ("drm/edid: split drm_edid_block_valid() to check and act parts")

-- 
Cheers,
Stephen Rothwell

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

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	DRI <dri-devel@lists.freedesktop.org>
Cc: Jani Nikula <jani.nikula@intel.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [Intel-gfx] linux-next: build warnings after merge of the drm-misc tree
Date: Wed, 6 Apr 2022 15:44:31 +1000	[thread overview]
Message-ID: <20220406154431.567414c3@canb.auug.org.au> (raw)

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

Hi all,

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

drivers/gpu/drm/drm_edid.c:1589: warning: Function parameter or member '_edid' not described in 'drm_edid_header_is_valid'
drivers/gpu/drm/drm_edid.c:1589: warning: Excess function parameter 'raw_edid' description in 'drm_edid_header_is_valid'
drivers/gpu/drm/drm_edid.c:1737: warning: Function parameter or member '_block' not described in 'drm_edid_block_valid'
drivers/gpu/drm/drm_edid.c:1737: warning: Excess function parameter 'raw_edid' description in 'drm_edid_block_valid'

Introduced by commits

  6d987ddd6843 ("drm/edid: make drm_edid_header_is_valid() accept void pointer")
  1f221284ab63 ("drm/edid: split drm_edid_block_valid() to check and act parts")

-- 
Cheers,
Stephen Rothwell

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

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	DRI <dri-devel@lists.freedesktop.org>
Cc: Jani Nikula <jani.nikula@intel.com>,
	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: Wed, 6 Apr 2022 15:44:31 +1000	[thread overview]
Message-ID: <20220406154431.567414c3@canb.auug.org.au> (raw)

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

Hi all,

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

drivers/gpu/drm/drm_edid.c:1589: warning: Function parameter or member '_edid' not described in 'drm_edid_header_is_valid'
drivers/gpu/drm/drm_edid.c:1589: warning: Excess function parameter 'raw_edid' description in 'drm_edid_header_is_valid'
drivers/gpu/drm/drm_edid.c:1737: warning: Function parameter or member '_block' not described in 'drm_edid_block_valid'
drivers/gpu/drm/drm_edid.c:1737: warning: Excess function parameter 'raw_edid' description in 'drm_edid_block_valid'

Introduced by commits

  6d987ddd6843 ("drm/edid: make drm_edid_header_is_valid() accept void pointer")
  1f221284ab63 ("drm/edid: split drm_edid_block_valid() to check and act parts")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2022-04-06  5:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  5:44 Stephen Rothwell [this message]
2022-04-06  5:44 ` linux-next: build warnings after merge of the drm-misc tree Stephen Rothwell
2022-04-06  5:44 ` [Intel-gfx] " Stephen Rothwell
2022-04-06  5:51 ` Stephen Rothwell
2022-04-06  5:51   ` Stephen Rothwell
2022-04-06  5:51   ` [Intel-gfx] " Stephen Rothwell
2022-04-13  0:07 ` Stephen Rothwell
2022-04-13  0:07   ` [Intel-gfx] " Stephen Rothwell
2022-04-13  0:07   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2024-04-16  7:31 Stephen Rothwell
2024-04-16  8:25 ` Jocelyn Falempe
2024-03-26  5:12 Stephen Rothwell
2023-12-04  4:53 Stephen Rothwell
2023-12-04  4:53 ` Stephen Rothwell
2023-03-14  3:15 Stephen Rothwell
2023-03-14  3:15 ` Stephen Rothwell
2022-06-11  8:21 Stephen Rothwell
2022-06-11  8:21 ` Stephen Rothwell
2022-06-11 16:57 ` Doug Anderson
2022-06-11 16:57   ` Doug Anderson
2021-01-15  1:23 Stephen Rothwell
2021-01-15  1:23 ` Stephen Rothwell
2021-01-15 15:03 ` Nirmoy
2021-01-15 15:03   ` Nirmoy
2015-08-14  5:35 Stephen Rothwell
2015-08-14  5:35 ` Stephen Rothwell
2015-08-14 12:51 ` Thierry Reding
2015-08-14 12:51   ` Thierry Reding
2015-07-14  3:05 Stephen Rothwell
2015-07-14  3:05 ` 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=20220406154431.567414c3@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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.