From: Marcel Holtmann <marcel@holtmann.org>
To: akpm@linux-foundation.org
Cc: linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
hidave.darkstar@gmail.com, mingo@elte.hu
Subject: Re: [patch 2/2] bluetooth: CONFIG_DEBUG_LOCK_ALLOC ifdefs remove
Date: Thu, 12 Feb 2009 02:52:38 +0100 [thread overview]
Message-ID: <1234403558.7293.28.camel@violet> (raw)
In-Reply-To: <200902112128.n1BLSCdw000376@imap1.linux-foundation.org>
Hi Andrew,
> Due to lockdep changes the CONFIG_DEBUG_LOCK_ALLOC ifdef is not needed
> now, just remove it here.
>
> The following commit fixed the !lockdep build warnings:
already part of my bluetooth-testing.git tree.
Regards
Marcel
WARNING: multiple messages have this Message-ID (diff)
From: Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
To: akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org
Cc: linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
hidave.darkstar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
mingo-X9Un+BFzKDI@public.gmane.org
Subject: Re: [patch 2/2] bluetooth: CONFIG_DEBUG_LOCK_ALLOC ifdefs remove
Date: Thu, 12 Feb 2009 02:52:38 +0100 [thread overview]
Message-ID: <1234403558.7293.28.camel@violet> (raw)
In-Reply-To: <200902112128.n1BLSCdw000376-AB4EexQrvXRQetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Hi Andrew,
> Due to lockdep changes the CONFIG_DEBUG_LOCK_ALLOC ifdef is not needed
> now, just remove it here.
>
> The following commit fixed the !lockdep build warnings:
already part of my bluetooth-testing.git tree.
Regards
Marcel
next prev parent reply other threads:[~2009-02-12 1:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 21:28 [patch 2/2] bluetooth: CONFIG_DEBUG_LOCK_ALLOC ifdefs remove akpm
2009-02-11 21:28 ` akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b
2009-02-12 1:52 ` Marcel Holtmann [this message]
2009-02-12 1:52 ` Marcel Holtmann
2009-02-12 2:22 ` Andrew Morton
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=1234403558.7293.28.camel@violet \
--to=marcel@holtmann.org \
--cc=akpm@linux-foundation.org \
--cc=hidave.darkstar@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@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.