From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] bluetooth: fix sparse & gcc warnings
Date: Wed, 1 Jun 2011 16:48:58 -0300 [thread overview]
Message-ID: <20110601194858.GE2564@joana> (raw)
In-Reply-To: <1306911285.3867.6.camel@jlt3.sipsolutions.net>
Hi Johannes,
* Johannes Berg <johannes@sipsolutions.net> [2011-06-01 08:54:45 +0200]:
> From: Johannes Berg <johannes.berg@intel.com>
>
> sparse complains about a few things that should
> be static, and I also noticed another warning
> from gcc about a set but unused variable.
>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
> net/bluetooth/l2cap_core.c | 6 +++---
> net/bluetooth/mgmt.c | 2 +-
> net/bluetooth/rfcomm/sock.c | 3 ---
> 3 files changed, 4 insertions(+), 7 deletions(-)
I applied the sparse part as set but unused variable warnings are all fixed,
thanks for the patch.
--
Gustavo F. Padovan
http://profusion.mobi
prev parent reply other threads:[~2011-06-01 19:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 6:54 [PATCH] bluetooth: fix sparse & gcc warnings Johannes Berg
2011-06-01 19:48 ` Gustavo F. Padovan [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=20110601194858.GE2564@joana \
--to=padovan@profusion.mobi \
--cc=johannes@sipsolutions.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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).