[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTikik8+f1D4D_Dv_rFK=QQjdce9rwg@mail.gmail.com>
Date: Thu, 26 May 2011 23:15:34 +0200
From: Sjur Brændeland <sjurbren@...il.com>
To: Randy Dunlap <randy.dunlap@...cle.com>, balbi@...com
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
netdev <netdev@...r.kernel.org>, linux-next@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>, gregkh@...e.de
Subject: Re: linux-next: Tree for May 26 (drivers/net/caif)
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@...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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists