From: Kalle Valo <kvalo@codeaurora.org>
To: Jiri Kosina <jikos@kernel.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Luca Coelho <luciano.coelho@intel.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iwlwifi: don't call netif_napi_add() with rxq->lock held (was Re: Lockdep warning in iwl_pcie_rx_handle())
Date: Wed, 03 Mar 2021 20:33:09 +0200 [thread overview]
Message-ID: <87y2f46qai.fsf@codeaurora.org> (raw)
In-Reply-To: <nycvar.YFH.7.76.2103031901140.12405@cbobk.fhfr.pm> (Jiri Kosina's message of "Wed, 3 Mar 2021 19:01:45 +0100 (CET)")
Jiri Kosina <jikos@kernel.org> writes:
> On Wed, 3 Mar 2021, Kalle Valo wrote:
>
>> Patch applied to wireless-drivers.git, thanks.
>
> Thanks, but ...
>
>> 295d4cd82b01 iwlwifi: don't call netif_napi_add() with rxq->lock
>> held (was Re: Lockdep warning in iwl_pcie_rx_handle())
>
> ... i believe you want to drop the "(was ...") part from the patch
> subject.
Too late now, it's already applied and pull request sent. Why was it
there in the first place?
--
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-03 20:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 20:44 Lockdep warning in iwl_pcie_rx_handle() Jiri Kosina
2021-03-01 21:09 ` Jiri Kosina
2021-03-01 21:12 ` Johannes Berg
2021-03-02 9:27 ` [PATCH] iwlwifi: don't call netif_napi_add() with rxq->lock held (was Re: Lockdep warning in iwl_pcie_rx_handle()) Jiri Kosina
2021-03-02 10:34 ` [PATCH v2] " Jiri Kosina
2021-03-02 10:49 ` Coelho, Luciano
2021-03-02 12:17 ` Kalle Valo
2021-03-02 14:55 ` Jiri Kosina
2021-03-03 21:39 ` Sedat Dilek
2021-03-03 15:59 ` Kalle Valo
[not found] ` <20210303155941.25521C43463@smtp.codeaurora.org>
2021-03-03 18:01 ` Jiri Kosina
2021-03-03 18:33 ` Kalle Valo [this message]
2021-03-03 19:19 ` Jiri Kosina
2021-03-02 10:48 ` [PATCH] " Coelho, Luciano
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=87y2f46qai.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=hkallweit1@gmail.com \
--cc=jikos@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.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