public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: bluez-devel@lists.sourceforge.net, maxk@qualcomm.com
Subject: Re: [PATCH] BLUETOOTH:  Use newer, non-deprecated __RW_LOCK_UNLOCKED macro.
Date: Thu, 20 Mar 2008 10:45:26 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.1.00.0803201043240.3714@localhost.localdomain> (raw)
In-Reply-To: <1206021236.7678.12.camel@californication>

On Thu, 20 Mar 2008, Marcel Holtmann wrote:

> Hi Robert,
>
> > Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
> >
> > ---
> >
> >   not compile tested, but a fairly trivial transformation.
> >
> >
> >  net/bluetooth/hci_sock.c    |    2 +-
> >  net/bluetooth/l2cap.c       |    2 +-
> >  net/bluetooth/rfcomm/sock.c |    2 +-
> >  net/bluetooth/sco.c         |    2 +-
> >  4 files changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/net/bluetooth/hci_sock.c b/net/bluetooth/hci_sock.c
> > index b5d4019..1d36c09 100644
> > --- a/net/bluetooth/hci_sock.c
> > +++ b/net/bluetooth/hci_sock.c
> > @@ -84,7 +84,7 @@ static struct hci_sec_filter hci_sec_filter = {
> >  };
> >
> >  static struct bt_sock_list hci_sk_list = {
> > -	.lock = RW_LOCK_UNLOCKED
> > +	.lock = __RW_LOCK_UNLOCKED(hci_sk_list.lock)
> >  };
>
> is that the way we do init of locks now? I haven't realized that
> RW_LOCK_UNLOCKED is deprecated.

yup, see Documentation/spinlocks.txt:

"SPIN_LOCK_UNLOCKED and RW_LOCK_UNLOCKED defeat lockdep state tracking
and are hence deprecated.

"Please use DEFINE_SPINLOCK()/DEFINE_RWLOCK() or
__SPIN_LOCK_UNLOCKED()/__RW_LOCK_UNLOCKED() as appropriate for static
initialization."

rday
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================

  reply	other threads:[~2008-03-20 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LFD.1.00.0803151348180.24734@localhost.localdomain>
2008-03-20 13:53 ` [Bluez-devel] [PATCH] BLUETOOTH: Use newer, non-deprecated __RW_LOCK_UNLOCKED macro Marcel Holtmann
2008-03-20 14:45   ` Robert P. J. Day [this message]
2008-03-20 14:50     ` Marcel Holtmann

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=alpine.LFD.1.00.0803201043240.3714@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    --cc=maxk@qualcomm.com \
    /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