From: Richard Genoud <richard.genoud@gmail.com>
To: Daniele Venzano <venza@brownhat.org>
Cc: Kernel Janitors <kernel-janitors@vger.kernel.org>,
linux-bluetooth@vger.kernel.org, marcel@holtmann.org
Subject: Re: [PATCH] Fix unused variable warning in rfcomm
Date: Fri, 23 Jan 2009 14:50:13 +0100 [thread overview]
Message-ID: <80b317760901230550u75353e7dw1efed395cc9e6259@mail.gmail.com> (raw)
In-Reply-To: <20090123094149.GA31218@milesteg.arr>
2009/1/23 Daniele Venzano <venza@brownhat.org>:
> The following patch fixes a warning generated when compiling rfcomm.c
> without CONFIG_BT_RFCOMM_DEBUG.
> The warning was:
> net/bluetooth/rfcomm/sock.c: In function 'rfcomm_sock_ioctl':
> net/bluetooth/rfcomm/sock.c:795: warning: unused variable 'sk'
>
> Patch is against 2.6.28.1
>
> Signed-off-by: Daniele Venzano <venza@brownhat.org>
>
> --- a/net/bluetooth/rfcomm/sock.c 2009-01-23 10:30:34.000000000 +0100
> +++ b/net/bluetooth/rfcomm/sock.c 2009-01-23 10:31:25.000000000 +0100
> @@ -792,7 +792,9 @@ static int rfcomm_sock_getsockopt(struct
>
> static int rfcomm_sock_ioctl(struct socket *sock, unsigned int cmd, unsigned long arg)
> {
> +#ifdef CONFIG_BT_RFCOMM_DEBUG
> struct sock *sk = sock->sk;
> +#endif
> int err;
>
> BT_DBG("sk %p cmd %x arg %lx", sk, cmd, arg);
>
if CONFIG_BT_RFCOMM_TTY is set, the compilation will break.
richard.
next prev parent reply other threads:[~2009-01-23 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 9:41 [PATCH] Fix unused variable warning in rfcomm Daniele Venzano
2009-01-23 13:50 ` Richard Genoud [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-23 14:09 Daniele Venzano
2009-01-23 14:22 ` Marcel Holtmann
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=80b317760901230550u75353e7dw1efed395cc9e6259@mail.gmail.com \
--to=richard.genoud@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=venza@brownhat.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