linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: wireless drivers sparse warnings
Date: Tue, 09 Dec 2008 12:34:40 -0500	[thread overview]
Message-ID: <1228844080.4146.4.camel@dv> (raw)
In-Reply-To: <1228823435.22164.216.camel@johannes.berg>

On Tue, 2008-12-09 at 12:50 +0100, Johannes Berg wrote:
> [minus uninteresting ones like "should be static"]

Please don't omit them next time.  Some functions may turn out to be
useless.

> drivers/net/wireless/orinoco/airport.c:282:2: warning: returning void-valued expression

I've just sent a fix for that.  Thanks!

-- 
Regards,
Pavel Roskin

      parent reply	other threads:[~2008-12-09 17:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-09 11:50 wireless drivers sparse warnings Johannes Berg
2008-12-09 13:30 ` Johannes Berg
2008-12-10  9:13   ` Elmer Joandi
2008-12-10  9:23     ` Johannes Berg
2008-12-09 14:51 ` Bob Copeland
2008-12-09 17:34 ` Pavel Roskin [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=1228844080.4146.4.camel@dv \
    --to=proski@gnu.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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).