From: Matthew Wilcox <matthew@wil.cx>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] PCI fixes for 2.6.29
Date: Wed, 11 Mar 2009 14:13:38 -0600 [thread overview]
Message-ID: <20090311201337.GI25995@parisc-linux.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0903111220200.32478@localhost.localdomain>
On Wed, Mar 11, 2009 at 12:22:56PM -0700, Linus Torvalds wrote:
> On Tue, 10 Mar 2009, Matthew Wilcox wrote:
> > These are the PCI fixes that have been piling up for the last week while
> > Jesse's been on vacation. I don't think there's anything questionable
> > here. All the patches have been posted to linux-pci.
>
> Grrr. It doesn't even compile cleanly:
>
> drivers/pci/quirks.c: In function ?ht_check_msi_mapping?:
> drivers/pci/quirks.c:2142: warning: ?return? with no value, in function returning non-void
>
> and yes, it's a real bug.
Agreed, it's a real bug. I also think it should return 0, but I want
Prakash to verify that, since I don't have a system of this nature.
I wish this warning were an error. According to the GCC docs,
-Werror=return-type should do this, but it seems to have no effect.
> I'm not happy.
Me neither. I'm sorry I didn't catch the warning.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2009-03-11 20:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 4:36 [GIT PULL] PCI fixes for 2.6.29 Matthew Wilcox
2009-03-11 19:22 ` Linus Torvalds
2009-03-11 20:13 ` Matthew Wilcox [this message]
2009-03-11 20:36 ` Yinghai Lu
2009-03-11 20:48 ` Matthew Wilcox
2009-03-11 20:59 ` Yinghai Lu
2009-03-12 17:23 ` Prakash Punnoor
2009-03-12 23:09 ` Matthew Wilcox
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=20090311201337.GI25995@parisc-linux.org \
--to=matthew@wil.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=torvalds@linux-foundation.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