From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: linux-next: build warning after merge of the suspend tree
Date: Fri, 12 Feb 2010 12:32:45 +0100 [thread overview]
Message-ID: <201002121232.45343.rjw@sisk.pl> (raw)
In-Reply-To: <20100212155750.3f95932f.sfr@canb.auug.org.au>
On Friday 12 February 2010, Stephen Rothwell wrote:
> Hi Rafael,
>
> After merging the suspend tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> drivers/usb/core/hcd-pci.c:153: warning: return type defaults to 'int'
> drivers/usb/core/hcd-pci.c: In function 'clear_hs_companion':
> drivers/usb/core/hcd-pci.c:153: warning: control reaches end of non-void function
>
> Introduced by commit 708efd3eb95d318442da39ad6e5c01d5c9b85dbf ("USB:
> implement non-tree resume ordering constraints for PCI host controllers").
Ah, missing "void", sorry about that. Should be fixed now.
Rafael
next prev parent reply other threads:[~2010-02-12 11:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 4:57 linux-next: build warning after merge of the suspend tree Stephen Rothwell
2010-02-12 11:32 ` Rafael J. Wysocki [this message]
2010-02-12 12:25 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2011-05-23 5:06 Stephen Rothwell
2011-05-23 14:18 ` mark gross
2011-05-23 15:24 ` Randy Dunlap
2011-05-23 16:21 ` Milton Miller
2011-05-23 17:42 ` Milton Miller
2011-05-24 6:13 ` mark gross
2011-05-23 18:57 ` Rafael J. Wysocki
2011-05-23 19:54 ` Rafael J. Wysocki
2011-05-24 6:34 ` mark gross
2011-05-24 21:30 ` Rafael J. Wysocki
2011-05-26 1:58 ` mark gross
2010-02-11 6:10 Stephen Rothwell
2010-02-11 13:11 ` Rafael J. Wysocki
2010-02-11 15:32 ` Alan Stern
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=201002121232.45343.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=stern@rowland.harvard.edu \
/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).