linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jiri Kosina <jikos@kernel.org>
Cc: Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
	Luca Coelho <luciano.coelho@intel.com>,
	Intel Linux Wireless <linuxwifi@intel.com>,
	Kalle Valo <kvalo@codeaurora.org>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5.1-rc] iwlwifi: make locking in iwl_mvm_tx_mpdu() BH-safe
Date: Mon, 15 Apr 2019 14:08:15 +0200	[thread overview]
Message-ID: <2e48080fa3a44c01c8c045308e77768bb058c952.camel@sipsolutions.net> (raw)
In-Reply-To: <nycvar.YFH.7.76.1904151404430.9803@cbobk.fhfr.pm>


> Given that we don't have a primitive in lockdep to assert this invariant, 
> would you consider queuing the below on top of f5ae2f932e2f in 
> wireless-drivers.git?

I think this would probably go via -next, but sure, I've applied it
internally and we'll let it percolate through the trees as usual.

johannes


  reply	other threads:[~2019-04-15 12:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 11:03 [PATCH v5.1-rc] iwlwifi: make locking in iwl_mvm_tx_mpdu() BH-safe Jiri Kosina
2019-04-15 11:10 ` Johannes Berg
2019-04-15 11:33   ` Jiri Kosina
2019-04-15 11:37     ` Johannes Berg
2019-04-15 12:06       ` Jiri Kosina
2019-04-15 12:08         ` Johannes Berg [this message]
2019-09-11 11:42       ` Jiri Kosina
2019-09-11 12:04         ` Jiri Kosina
2019-09-20 21:34           ` Jiri Kosina
2019-10-01  9:46         ` Johannes Berg
2019-10-01  9:52           ` Johannes Berg

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=2e48080fa3a44c01c8c045308e77768bb058c952.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=davem@davemloft.net \
    --cc=emmanuel.grumbach@intel.com \
    --cc=jikos@kernel.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxwifi@intel.com \
    --cc=luciano.coelho@intel.com \
    --cc=netdev@vger.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).