From: Shuah Khan <skhan@linuxfoundation.org>
To: Kalle Valo <kvalo@codeaurora.org>, 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, kuba@kernel.org, will@kernel.org,
davem@davemloft.net, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v3 0/3] Add lockdep_assert_not_held()
Date: Mon, 1 Mar 2021 09:04:53 -0700 [thread overview]
Message-ID: <5a34de30-6de2-8985-ef6f-5873228a3231@linuxfoundation.org> (raw)
In-Reply-To: <87sg5f87df.fsf@codeaurora.org>
On 3/1/21 4:02 AM, Kalle Valo wrote:
> Peter Zijlstra <peterz@infradead.org> writes:
>
>> On Mon, Mar 01, 2021 at 10:45:32AM +0200, Kalle Valo wrote:
>>> 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?
>>
>> I've just queued the lot for locking/core, which will show up in tip
>> when the robots don't hate on it.
>>
>> Does that work for you?
>
> That's perfect, thanks! Just making sure that the patches don't get
> lost.
>
Awesome. Thank you.
thanks,
-- Shuah
prev parent reply other threads:[~2021-03-01 16:11 UTC|newest]
Thread overview: 9+ 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 ` [PATCH v3 1/3] lockdep: add lockdep_assert_not_held() Shuah Khan
2021-02-27 0:06 ` [PATCH v3 2/3] lockdep: add lockdep lock state defines Shuah Khan
2021-02-27 0:07 ` [PATCH v3 3/3] ath10k: detect conf_mutex held ath10k_drain_tx() calls Shuah Khan
2021-03-01 8:38 ` [PATCH v3 0/3] Add lockdep_assert_not_held() Peter Zijlstra
2021-03-01 8:45 ` Kalle Valo
2021-03-01 9:36 ` Peter Zijlstra
2021-03-01 11:02 ` Kalle Valo
2021-03-01 16:04 ` Shuah Khan [this message]
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=5a34de30-6de2-8985-ef6f-5873228a3231@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=ath10k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).