From: Prakash Punnoor <prakash@punnoor.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Matthew Wilcox <matthew@wil.cx>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] PCI fixes for 2.6.29
Date: Thu, 12 Mar 2009 18:23:57 +0100 [thread overview]
Message-ID: <200903121823.57701.prakash@punnoor.de> (raw)
In-Reply-To: <alpine.LFD.2.00.0903111220200.32478@localhost.localdomain>
On Mittwoch 11 März 2009 20:22:56 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.
>
> I'm not happy.
>
> I assume the proper fix is this trivial one-liner, but people should
> double-check.
>
> Not pulled.
As I explained to Matthew Wilcox my small patch was incorrectly applied. It
originally was in
static void __devinit __nv_msi_ht_cap_quirk(struct pci_dev *dev, int all)
I don't know who or how it moved into
static int __devinit ht_check_msi_mapping(struct pci_dev *dev)
where it breaks for obvious reasons.
>
> Linus
>
> ---
> drivers/pci/quirks.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index a13f3d7..4ba55d0 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -2139,7 +2139,7 @@ static int __devinit ht_check_msi_mapping(struct
> pci_dev *dev)
>
> /* Enabling HT MSI mapping on this device breaks MCP51 */
> if (dev->device == 0x270)
> - return;
> + return 0;
>
> /* check if there is HT MSI cap or enabled on this device */
> pos = pci_find_ht_capability(dev, HT_CAPTYPE_MSI_MAPPING);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2009-03-12 17:21 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
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 [this message]
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=200903121823.57701.prakash@punnoor.de \
--to=prakash@punnoor.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--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