From: Randy Dunlap <rdunlap@xenotime.net>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH -next] vgaarb.h: fix build warnings
Date: Tue, 13 Mar 2012 14:25:15 -0700 [thread overview]
Message-ID: <4F5FBB3B.1090800@xenotime.net> (raw)
In-Reply-To: <4F26F2F8.30505@xenotime.net>
On 01/30/2012 11:43 AM, Randy Dunlap wrote:
This patch is still needed in linux-next of 20120313.
> From: Randy Dunlap <rdunlap@xenotime.net>
>
> Fix build warnings by providing a struct stub since no fields of
> the struct are used:
>
> include/linux/vgaarb.h:66:9: warning: 'struct pci_dev' declared inside parameter list
> include/linux/vgaarb.h:66:9: warning: its scope is only this definition or declaration, which is probably not what you want
> include/linux/vgaarb.h:99:34: warning: 'struct pci_dev' declared inside parameter list
> include/linux/vgaarb.h:109:6: warning: 'struct pci_dev' declared inside parameter list
> include/linux/vgaarb.h:121:8: warning: 'struct pci_dev' declared inside parameter list
> include/linux/vgaarb.h:140:37: warning: 'struct pci_dev' declared inside parameter list
>
> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
> Cc: David Airlie <airlied@linux.ie>
> Cc: dri-devel@lists.freedesktop.org
> ---
> include/linux/vgaarb.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> --- linux-next-20120130.orig/include/linux/vgaarb.h
> +++ linux-next-20120130/include/linux/vgaarb.h
> @@ -47,6 +47,8 @@
> */
> #define VGA_DEFAULT_DEVICE (NULL)
>
> +struct pci_dev;
> +
> /* For use by clients */
>
> /**
>
--
~Randy
next prev parent reply other threads:[~2012-03-13 21:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 3:41 linux-next: Tree for Jan 30 Stephen Rothwell
2012-01-30 19:40 ` [PATCH -next] cpufreq: fix gx-suspmod.c build Randy Dunlap
2012-01-30 18:55 ` Dave Jones
2012-01-30 19:42 ` [PATCH -next] sound: fix include/sound/core.h warning Randy Dunlap
2012-01-30 20:15 ` Takashi Iwai
2012-01-30 19:43 ` [PATCH -next] vgaarb.h: fix build warnings Randy Dunlap
2012-03-13 21:25 ` Randy Dunlap [this message]
2012-01-31 3:08 ` [PATCH -next] mtd: fix nand/docg4.c printk format warnings Randy Dunlap
2012-01-31 3:09 ` [PATCH -next] ext4: fix balloc.c printk format warning Randy Dunlap
2012-01-31 3:49 ` [PATCH -next] ramoops: fix printk format warnings Randy Dunlap
2012-01-31 3:50 ` [PATCH -next] cifs: " Randy Dunlap
2012-01-31 10:42 ` Jeff Layton
2012-01-31 13:43 ` Steve French
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=4F5FBB3B.1090800@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).