Re: Bluetooth: invert locking order in connect path

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Tue, Jan 03, 2012, Gustavo Padovan wrote:
> * Dan Carpenter <dan.carpenter@xxxxxxxxxx> [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
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux