From: Marcel Holtmann <marcel@holtmann.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Gustavo Padovan <gustavo@padovan.org>,
Mat Martineau <mathewm@codeaurora.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: l2cap_physical_cfm() can be static
Date: Wed, 24 Oct 2012 18:55:34 -0700 [thread overview]
Message-ID: <1351130134.1785.85.camel@aeonflux> (raw)
In-Reply-To: <20121025002608.GA10418@localhost>
Hi Fengguang,
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> ---
> net/bluetooth/l2cap_core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next.orig/net/bluetooth/l2cap_core.c 2012-10-25 08:23:52.456742699 +0800
> +++ linux-next/net/bluetooth/l2cap_core.c 2012-10-25 08:23:55.056742760 +0800
> @@ -4569,7 +4569,7 @@ static void l2cap_do_move_cancel(struct
> l2cap_ertm_send(chan);
> }
>
> -void l2cap_physical_cfm(struct l2cap_chan *chan, int result, u8 local_amp_id,
> +static void l2cap_physical_cfm(struct l2cap_chan *chan, int result, u8 local_amp_id,
> u8 remote_amp_id)
I rather wait for Mat to ACK or NACK this one. Maybe it is an oversight
or we need that later on to be actually public.
Regards
Marcel
next prev parent reply other threads:[~2012-10-25 1:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 21:55 [bluetooth:master 12/33] net/bluetooth/l2cap_core.c:4495:6: sparse: symbol 'l2cap_physical_cfm' was not declared. Should it be static? Fengguang Wu
2012-10-24 22:01 ` Gustavo Padovan
2012-10-25 0:26 ` [PATCH] Bluetooth: l2cap_physical_cfm() can be static Fengguang Wu
2012-10-25 1:55 ` Marcel Holtmann [this message]
2012-10-25 7:13 ` Andrei Emeltchenko
2012-10-25 15:29 ` Mat Martineau
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=1351130134.1785.85.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=fengguang.wu@intel.com \
--cc=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mathewm@codeaurora.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).