From: Gustavo Padovan <gustavo@padovan.org>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Do not check func ready existence
Date: Wed, 30 May 2012 04:17:18 -0300 [thread overview]
Message-ID: <20120530071718.GK18069@joana> (raw)
In-Reply-To: <1338360932-29940-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
* Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com> [2012-05-30 09:55:32 +0300]:
> From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
>
> Functions will be always defined and in case not implemented as
> dummy __no_func.
>
> Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> ---
> net/bluetooth/l2cap_core.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
> index 778c0c8..4f65a32 100644
> --- a/net/bluetooth/l2cap_core.c
> +++ b/net/bluetooth/l2cap_core.c
> @@ -937,8 +937,7 @@ static void l2cap_chan_ready(struct l2cap_chan *chan)
>
> chan->state = BT_CONNECTED;
>
> - if (chan->ops->ready)
> - chan->ops->ready(chan);
> + chan->ops->ready(chan);
Patch has been applied to bluetooth-next. Thanks.
Gustavo
next prev parent reply other threads:[~2012-05-30 7:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 21:16 [PATCH 1/5] Bluetooth: Move bt_accept_enqueue() call to l2cap_sock.c Gustavo Padovan
2012-05-28 21:16 ` [PATCH 2/5] Bluetooth: Remove parent socket usage from l2cap_core.c Gustavo Padovan
2012-05-28 21:16 ` [PATCH 3/5] Bluetooth: Do not check if teardown exists Gustavo Padovan
2012-05-29 7:11 ` [PATCH] Bluetooth: Do not check func ready existence Andrei Emeltchenko
2012-05-29 15:23 ` Gustavo Padovan
2012-05-30 6:55 ` Andrei Emeltchenko
2012-05-30 7:17 ` Gustavo Padovan [this message]
2012-05-28 21:16 ` [PATCH 4/5] Bluetooth: Create DEFER_SETUP flag in conf_state Gustavo Padovan
2012-05-28 21:16 ` [PATCH 5/5] Bluetooth: Add chan->ops->defer() Gustavo Padovan
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=20120530071718.GK18069@joana \
--to=gustavo@padovan.org \
--cc=Andrei.Emeltchenko.news@gmail.com \
--cc=linux-bluetooth@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 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.