From: Johan Hedberg <johan.hedberg@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>,
linux-bluetooth@vger.kernel.org
Subject: Re: Bluetooth: invert locking order in connect path
Date: Wed, 11 Jan 2012 17:01:53 +0200 [thread overview]
Message-ID: <20120111150153.GA889@x220> (raw)
In-Reply-To: <20120103185214.GA30866@joana>
Hi,
On Tue, Jan 03, 2012, Gustavo Padovan wrote:
> * Dan Carpenter <dan.carpenter@oracle.com> [2012-01-03 17:44:33 +0300]:
>
> > 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
>
> Indeed, I'll fix it.
I didn't see the patch for this anywhere so I did it myself and got an
ack from Marcel. It's now part of my bluetooth-next tree.
Johan
prev parent reply other threads:[~2012-01-11 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 14:44 Bluetooth: invert locking order in connect path Dan Carpenter
2012-01-03 19:10 ` Gustavo Padovan
2012-01-11 15:01 ` Johan Hedberg [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=20120111150153.GA889@x220 \
--to=johan.hedberg@gmail.com \
--cc=dan.carpenter@oracle.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 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).