From: Kalle Valo <kvalo@codeaurora.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, ath10k@lists.infradead.org,
mingo@redhat.com, Shuah Khan <skhan@linuxfoundation.org>,
kuba@kernel.org, will@kernel.org, davem@davemloft.net
Subject: Re: [PATCH v3 0/3] Add lockdep_assert_not_held()
Date: Mon, 01 Mar 2021 10:45:32 +0200 [thread overview]
Message-ID: <878s779s9f.fsf@codeaurora.org> (raw)
In-Reply-To: <YDyn+6N6EfgWJ5GV@hirez.programming.kicks-ass.net> (Peter Zijlstra's message of "Mon, 1 Mar 2021 09:38:19 +0100")
Peter Zijlstra <peterz@infradead.org> writes:
> On Fri, Feb 26, 2021 at 05:06:57PM -0700, Shuah Khan wrote:
>> Shuah Khan (3):
>> lockdep: add lockdep_assert_not_held()
>> lockdep: add lockdep lock state defines
>> ath10k: detect conf_mutex held ath10k_drain_tx() calls
>
> Thanks!
Via which tree should these go?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, ath10k@lists.infradead.org,
mingo@redhat.com, kuba@kernel.org, will@kernel.org,
davem@davemloft.net
Subject: Re: [PATCH v3 0/3] Add lockdep_assert_not_held()
Date: Mon, 01 Mar 2021 10:45:32 +0200 [thread overview]
Message-ID: <878s779s9f.fsf@codeaurora.org> (raw)
In-Reply-To: <YDyn+6N6EfgWJ5GV@hirez.programming.kicks-ass.net> (Peter Zijlstra's message of "Mon, 1 Mar 2021 09:38:19 +0100")
Peter Zijlstra <peterz@infradead.org> writes:
> On Fri, Feb 26, 2021 at 05:06:57PM -0700, Shuah Khan wrote:
>> Shuah Khan (3):
>> lockdep: add lockdep_assert_not_held()
>> lockdep: add lockdep lock state defines
>> ath10k: detect conf_mutex held ath10k_drain_tx() calls
>
> Thanks!
Via which tree should these go?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-03-01 8:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 0:06 [PATCH v3 0/3] Add lockdep_assert_not_held() Shuah Khan
2021-02-27 0:06 ` Shuah Khan
2021-02-27 0:06 ` [PATCH v3 1/3] lockdep: add lockdep_assert_not_held() Shuah Khan
2021-02-27 0:06 ` Shuah Khan
2021-02-27 0:06 ` [PATCH v3 2/3] lockdep: add lockdep lock state defines Shuah Khan
2021-02-27 0:06 ` Shuah Khan
2021-02-27 0:07 ` [PATCH v3 3/3] ath10k: detect conf_mutex held ath10k_drain_tx() calls Shuah Khan
2021-02-27 0:07 ` Shuah Khan
2021-03-01 8:38 ` [PATCH v3 0/3] Add lockdep_assert_not_held() Peter Zijlstra
2021-03-01 8:38 ` Peter Zijlstra
2021-03-01 8:45 ` Kalle Valo [this message]
2021-03-01 8:45 ` Kalle Valo
2021-03-01 9:36 ` Peter Zijlstra
2021-03-01 9:36 ` Peter Zijlstra
2021-03-01 11:02 ` Kalle Valo
2021-03-01 11:02 ` Kalle Valo
2021-03-01 16:04 ` Shuah Khan
2021-03-01 16:04 ` Shuah Khan
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=878s779s9f.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=will@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.