From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <cyrus@holtmann.org>
Date: Tue, 3 Jan 2012 17:44:33 +0300
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Gustavo F. Padovan" <padovan@profusion.mobi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Bluetooth: invert locking order in connect path
Message-ID: <20120103144433.GA21712@elgon.mountain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-bluetooth-owner@vger.kernel.org
List-ID: <linux-bluetooth.vger.kernel.org>

Hi Gustavo,

You didn't mean to mark the function inline in 03a001948166 "Bluetooth:
invert locking order in connect path" did you?  It causes a Sparse
warning.

include/net/bluetooth/l2cap.h:837:30 error: marked inline, but without
a definition

regards,
dan carpenter