From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Randy Dunlap <randy.dunlap@oracle•com>
Cc: netdev <netdev@vger•kernel.org>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Sjur Braendeland <sjur.brandeland@stericsson•com>
Subject: Re: linux-next: Tree for May 26 (drivers/net/caif)
Date: Fri, 27 May 2011 11:01:23 +1000 [thread overview]
Message-ID: <20110527110123.aa7bbf38.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20110526120702.fac24de0.randy.dunlap@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
Hi Randy,
On Thu, 26 May 2011 12:07:02 -0700 Randy Dunlap <randy.dunlap@oracle•com> wrote:
>
> drivers/net/caif/caif_serial.c:194: warning: 'return' with no value, in function returning non-void
> drivers/net/caif/caif_serial.c:202: warning: 'return' with no value, in function returning non-void
>
> I'm curious: how do warnings like this get overlooked?
> too much noise in the build messages? or it wasn't overlooked, just ignored?
For me, too much noise :-( I catch some, but not all.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2011-05-27 1:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 6:39 linux-next: Tree for May 26 Stephen Rothwell
2011-05-26 19:01 ` linux-next: Tree for May 26 (drivers/base/node.c) Randy Dunlap
2011-06-10 15:44 ` Randy Dunlap
2011-06-10 18:31 ` Greg KH
2011-06-10 19:53 ` Randy Dunlap
2011-05-26 19:07 ` linux-next: Tree for May 26 (drivers/net/caif) Randy Dunlap
2011-05-26 21:15 ` Sjur Brændeland
2011-05-26 21:30 ` Randy Dunlap
2011-05-27 8:09 ` [PATCH] caif: Fix compile warning in caif_serial.c Sjur Brændeland
2011-05-27 15:37 ` Randy Dunlap
2011-05-27 1:01 ` Stephen Rothwell [this message]
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=20110527110123.aa7bbf38.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=randy.dunlap@oracle$(echo .)com \
--cc=sjur.brandeland@stericsson$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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