From: Richard Holden <aciddeath@gmail.com>
To: linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: pci_read_config_* functions and uninitialized warnings?
Date: Wed, 19 Nov 2008 11:15:32 -0700 [thread overview]
Message-ID: <E749C9B9-2E83-4F54-A1C8-CBF376ECBD57@gmail.com> (raw)
I'm building linux-next and seeing a lot of uninitialized warnings
that go back to values being set using pci_read_config_* functions.
Does anyone more familiar than I am with that code have any ideas on
how to get GCC to realize that the pci_read_config_* initialize the
vars. I don't want to end up submitting a lot of patches with
uninitialized_var to fix the problems.
gcc --version: gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.1)
-Richard Holden
reply other threads:[~2008-11-19 18:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E749C9B9-2E83-4F54-A1C8-CBF376ECBD57@gmail.com \
--to=aciddeath@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®