From: "Sjur Brændeland" <sjurbren@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>, balbi@ti.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
netdev <netdev@vger.kernel.org>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
gregkh@suse.de
Subject: Re: linux-next: Tree for May 26 (drivers/net/caif)
Date: Thu, 26 May 2011 23:15:34 +0200 [thread overview]
Message-ID: <BANLkTikik8+f1D4D_Dv_rFK=QQjdce9rwg@mail.gmail.com> (raw)
In-Reply-To: <20110526120702.fac24de0.randy.dunlap@oracle.com>
Hi Randy,
[Randy]
> (not new)
>
> 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?
The patch introducing this problem is "tty: make receive_buf()
return the amout of bytes received" by Felipe Balbi <balbi@ti.com>.
It seems that this patch has been posted to linux-serial and not to
the netdev list or the gits net-next-2.6 or net-2.6 that I follow.
It's probably no excuse, but this problem is news to me.
Should I post a patch on linux-next anyway for this issue?
Regards,
Sjur
next prev parent reply other threads:[~2011-05-26 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110526163941.7dfcad1a.sfr@canb.auug.org.au>
2011-05-26 19:07 ` linux-next: Tree for May 26 (drivers/net/caif) Randy Dunlap
2011-05-26 21:15 ` Sjur Brændeland [this message]
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 ` linux-next: Tree for May 26 (drivers/net/caif) Stephen Rothwell
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='BANLkTikik8+f1D4D_Dv_rFK=QQjdce9rwg@mail.gmail.com' \
--to=sjurbren@gmail.com \
--cc=balbi@ti.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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).