From: Jiri Kosina <jikos@kernel.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: "Coelho, Luciano" <luciano.coelho@intel.com>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"linux-kernel@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: Tue, 2 Mar 2021 15:55:02 +0100 (CET) [thread overview]
Message-ID: <nycvar.YFH.7.76.2103021554160.12405@cbobk.fhfr.pm> (raw)
In-Reply-To: <87blc192cz.fsf@codeaurora.org>
On Tue, 2 Mar 2021, Kalle Valo wrote:
> > Thanks, Jiri! Let's take your patch since you already sent it out.
> >
> > Kalle, can you please take this directly to wireless-drivers.git?
> >
> > Acked-by: Luca Coelho <luciano.coelho@intel.com>
>
> Ok but I don't see this either in patchwork or lore, hopefully it shows
> up later.
Not sure about patchwork, but vger had hiccup (again) earlier today,
everything depending on the ML traffic is probably slower.
lore has it now though:
https://lore.kernel.org/lkml/nycvar.YFH.7.76.2103021134060.12405@cbobk.fhfr.pm/
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2021-03-02 17:33 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 [this message]
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
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=nycvar.YFH.7.76.2103021554160.12405@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@codeaurora.org \
--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;
as well as URLs for NNTP newsgroup(s).