All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Anderson <dianders@chromium.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	 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: Re: [Intel-gfx] linux-next: build warning after merge of the drm-misc tree
Date: Mon, 27 Sep 2021 07:42:26 -0700	[thread overview]
Message-ID: <CAD=FV=VrkmTDA-zLFW=1f1RAAVB_P=kJDQtAx+tng6+ZkhkCSA@mail.gmail.com> (raw)
In-Reply-To: <20210927154422.605920fd@canb.auug.org.au>

Hi,

On Sun, Sep 26, 2021 at 10:44 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the drm-misc tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> include/drm/drm_edid.h:530: warning: Function parameter or member 'vend_chr_1' not described in 'drm_edid_encode_panel_id'
> include/drm/drm_edid.h:530: warning: Excess function parameter 'vend_chr_3' description in 'drm_edid_encode_panel_id'
>
>
> Introduced by commit
>
>   7d1be0a09fa6 ("drm/edid: Fix EDID quirk compile error on older compilers")

Thanks for the report! Fix posted.

https://lore.kernel.org/r/20210927074104.1.Ibf22f2a0b75287a5d636c0570c11498648bf61c6@changeid

WARNING: multiple messages have this Message-ID (diff)
From: Doug Anderson <dianders@chromium.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	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: Re: linux-next: build warning after merge of the drm-misc tree
Date: Mon, 27 Sep 2021 07:42:26 -0700	[thread overview]
Message-ID: <CAD=FV=VrkmTDA-zLFW=1f1RAAVB_P=kJDQtAx+tng6+ZkhkCSA@mail.gmail.com> (raw)
In-Reply-To: <20210927154422.605920fd@canb.auug.org.au>

Hi,

On Sun, Sep 26, 2021 at 10:44 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the drm-misc tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> include/drm/drm_edid.h:530: warning: Function parameter or member 'vend_chr_1' not described in 'drm_edid_encode_panel_id'
> include/drm/drm_edid.h:530: warning: Excess function parameter 'vend_chr_3' description in 'drm_edid_encode_panel_id'
>
>
> Introduced by commit
>
>   7d1be0a09fa6 ("drm/edid: Fix EDID quirk compile error on older compilers")

Thanks for the report! Fix posted.

https://lore.kernel.org/r/20210927074104.1.Ibf22f2a0b75287a5d636c0570c11498648bf61c6@changeid

WARNING: multiple messages have this Message-ID (diff)
From: Doug Anderson <dianders@chromium.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	 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: Re: linux-next: build warning after merge of the drm-misc tree
Date: Mon, 27 Sep 2021 07:42:26 -0700	[thread overview]
Message-ID: <CAD=FV=VrkmTDA-zLFW=1f1RAAVB_P=kJDQtAx+tng6+ZkhkCSA@mail.gmail.com> (raw)
In-Reply-To: <20210927154422.605920fd@canb.auug.org.au>

Hi,

On Sun, Sep 26, 2021 at 10:44 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the drm-misc tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> include/drm/drm_edid.h:530: warning: Function parameter or member 'vend_chr_1' not described in 'drm_edid_encode_panel_id'
> include/drm/drm_edid.h:530: warning: Excess function parameter 'vend_chr_3' description in 'drm_edid_encode_panel_id'
>
>
> Introduced by commit
>
>   7d1be0a09fa6 ("drm/edid: Fix EDID quirk compile error on older compilers")

Thanks for the report! Fix posted.

https://lore.kernel.org/r/20210927074104.1.Ibf22f2a0b75287a5d636c0570c11498648bf61c6@changeid

  reply	other threads:[~2021-09-27 14:42 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27  5:44 linux-next: build warning after merge of the drm-misc tree Stephen Rothwell
2021-09-27  5:44 ` [Intel-gfx] " Stephen Rothwell
2021-09-27 14:42 ` Doug Anderson [this message]
2021-09-27 14:42   ` Doug Anderson
2021-09-27 14:42   ` Doug Anderson
  -- strict thread matches above, loose matches on Subject: below --
2023-10-05  3:56 [Intel-gfx] " 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-02  4:21 Stephen Rothwell
2023-08-02 14:49 ` Doug Anderson
2023-08-02  4:17 Stephen Rothwell
2023-08-02 14:49 ` Doug Anderson
2022-11-07  3:38 Stephen Rothwell
2022-04-20  6:24 Stephen Rothwell
2022-04-06  5:50 Stephen Rothwell
2022-04-13  0:04 ` Stephen Rothwell
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  1:45 ` Marek Vasut
2021-11-17  2:49 Stephen Rothwell
2022-01-20  3:26 ` Stephen Rothwell
2022-03-02  1:31   ` Stephen Rothwell
2022-03-02  3:26     ` Andrey Grodzovsky
2022-03-02  5:02       ` Stephen Rothwell
2022-03-27 23:56       ` Stephen Rothwell
2022-03-28 13:26         ` Andrey Grodzovsky
2021-10-15 10:01 Stephen Rothwell
2022-01-20  3:19 ` Stephen Rothwell
2022-01-20  9:50   ` Jani Nikula
2021-10-15  9:54 Stephen Rothwell
2022-01-20  3:18 ` Stephen Rothwell
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-02-08 12:39 Stephen Rothwell
2020-12-09 10:02 Stephen Rothwell
2020-12-09 16:10 ` Luben Tuikov
2020-11-18  5:23 Stephen Rothwell
2020-11-10  2:29 Stephen Rothwell
2020-11-02  1:46 Stephen Rothwell
2020-11-02  8:05 ` Boris Brezillon
2020-09-08  4:15 Stephen Rothwell
2020-05-07  3:04 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='CAD=FV=VrkmTDA-zLFW=1f1RAAVB_P=kJDQtAx+tng6+ZkhkCSA@mail.gmail.com' \
    --to=dianders@chromium.org \
    --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.