From: Kalle Valo <kvalo@codeaurora•org>
To: Lance Roy <ldr709@gmail•com>
Cc: linux-kernel@vger•kernel.org,
"Paul E. McKenney" <paulmck@linux•ibm.com>,
Daniel Drake <dsd@gentoo•org>,
Ulrich Kunitz <kune@deine-taler•de>,
"David S. Miller" <davem@davemloft•net>,
linux-wireless@vger•kernel.org, netdev@vger•kernel.org
Subject: Re: [PATCH 08/16] wireless: Replace spin_is_locked() with lockdep
Date: Wed, 03 Oct 2018 12:06:48 +0300 [thread overview]
Message-ID: <877eizjt5j.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20181003053902.6910-9-ldr709@gmail.com> (Lance Roy's message of "Tue, 2 Oct 2018 22:38:54 -0700")
Lance Roy <ldr709@gmail•com> writes:
> lockdep_assert_held() is better suited to checking locking requirements,
> since it won't get confused when someone else holds the lock. This is
> also a step towards possibly removing spin_is_locked().
>
> Signed-off-by: Lance Roy <ldr709@gmail•com>
> Cc: Daniel Drake <dsd@gentoo•org>
> Cc: Ulrich Kunitz <kune@deine-taler•de>
> Cc: Kalle Valo <kvalo@codeaurora•org>
> Cc: "David S. Miller" <davem@davemloft•net>
> Cc: <linux-wireless@vger•kernel.org>
> Cc: <netdev@vger•kernel.org>
> ---
> drivers/net/wireless/zydas/zd1211rw/zd_mac.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Should I take this or is it going through some other tree?
If it goes to via some other tree:
Acked-by: Kalle Valo <kvalo@codeaurora•org>
--
Kalle Valo
next prev parent reply other threads:[~2018-10-03 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181003053902.6910-1-ldr709@gmail.com>
2018-10-03 5:38 ` [PATCH 04/16] i40e: Replace spin_is_locked() with lockdep Lance Roy
2018-10-04 18:56 ` [Intel-wired-lan] " Bowers, AndrewX
2018-10-03 5:38 ` [PATCH 05/16] igbvf: " Lance Roy
2018-10-13 0:11 ` Brown, Aaron F
2018-10-03 5:38 ` [PATCH 06/16] sfc: " Lance Roy
2018-10-03 5:38 ` [PATCH 07/16] smsc: " Lance Roy
2018-10-03 5:38 ` [PATCH 08/16] wireless: " Lance Roy
2018-10-03 9:06 ` Kalle Valo [this message]
2018-10-04 6:57 ` Lance Roy
2018-10-04 10:05 ` Kalle Valo
2018-10-05 8:35 ` [PATCH 08/16] zd1211rw: " Kalle Valo
2018-10-03 5:39 ` [PATCH 14/16] netfilter: " Lance Roy
2018-10-03 8:29 ` Jozsef Kadlecsik
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=877eizjt5j.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dsd@gentoo$(echo .)org \
--cc=kune@deine-taler$(echo .)de \
--cc=ldr709@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=paulmck@linux$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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