All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Sjur Brændeland" <sjurbren@gmail.com>
Cc: balbi@ti.com, 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 14:30:06 -0700	[thread overview]
Message-ID: <20110526143006.2d1ef9f7.randy.dunlap@oracle.com> (raw)
In-Reply-To: <BANLkTikik8+f1D4D_Dv_rFK=QQjdce9rwg@mail.gmail.com>

On Thu, 26 May 2011 23:15:34 +0200 Sjur Brændeland wrote:

> 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.

I see.  Thanks for the explanation.

> Should I post a patch on linux-next anyway for this issue?

You or Felipe should, but he recently sent this note to the USB
mailing list:

"I'll be away until 31st of May on a business travel. Don't expect me to
look into patches during that period."

so it looks like it would better for you to do it, please.

thanks,
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2011-05-26 21:30 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 [this message]
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=20110526143006.2d1ef9f7.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.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=sfr@canb.auug.org.au \
    --cc=sjurbren@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.