Linux-Next Archive on lore.kernel.org
 help / color / 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: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Gustavo Padovan <gustavo.padovan@collabora.com>
Subject: linux-next: build warning after merge of the drm-misc tree
Date: Fri, 10 Mar 2017 11:03:14 +1100
Message-ID: <20170310110314.1f74dfe0@canb.auug.org.au> (raw)

Hi all,

After merging the drm-misc tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

In file included from drivers/gpu/drm/drm_pci.c:29:0:
include/drm/drm_pci.h:76:64: warning: 'struct platform_device' declared inside parameter list
 extern int drm_platform_init(struct drm_driver *driver, struct platform_device *platform_device);
                                                                ^
include/drm/drm_pci.h:76:64: warning: its scope is only this definition or declaration, which is probably not what you want

Introduced by commit

  23ef59ef6dcc ("drm: Extract drm_pci.h")

A forgotten include file (or maybe just a forward declaration of the struct).

-- 
Cheers,
Stephen Rothwell

             reply index

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10  0:03 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2018-07-12  1:51 Stephen Rothwell
2017-04-05  0:41 Stephen Rothwell
2017-04-05  7:26 ` Neil Armstrong
2016-11-22  1:45 Stephen Rothwell
2016-06-03  1:09 Stephen Rothwell
2015-09-23  3:20 Stephen Rothwell

Reply instructions:

You may reply publically 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=20170310110314.1f74dfe0@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gustavo.padovan@collabora.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git