linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tsuchiya Yuto <kitakar@gmail.com>
To: Amitkumar Karwar <amitkarwar@gmail.com>,
	Ganapathi Bhat <ganapathi.bhat@nxp.com>,
	Xinming Hu <huxinming820@gmail.com>,
	Kalle Valo <kvalo@codeaurora.org>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Maximilian Luz <luzmaximilian@gmail.com>,
	Andy Shevchenko <andriy.shevchenko@intel.com>,
	verdre@v0yd.nl, Tsuchiya Yuto <kitakar@gmail.com>
Subject: [PATCH 0/2] mwifiex: fixes for shutdown_sw() and reinit_sw()
Date: Wed, 28 Oct 2020 23:21:08 +0900	[thread overview]
Message-ID: <20201028142110.18144-1-kitakar@gmail.com> (raw)

Hello all,

This series fixes a software level reset feature. We, Microsoft Surface
devices users observed this issue, where firmware reset requires another
quirk. The other device users might not notice this issue because if
the reset is performed for the firmware level, this issue can't be
observed easily.

While here, update description of shutdown_sw() and reinit_sw() functions
to reflect current state.

Thanks,
Tsuchiya Yuto

Tsuchiya Yuto (2):
  mwifiex: fix mwifiex_shutdown_sw() causing sw reset failure
  mwifiex: update comment for shutdown_sw()/reinit_sw() to reflect
    current state

 drivers/net/wireless/marvell/mwifiex/main.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

-- 
2.29.1


             reply	other threads:[~2020-10-29  2:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28 14:21 Tsuchiya Yuto [this message]
2020-10-28 14:21 ` [PATCH 1/2] mwifiex: fix mwifiex_shutdown_sw() causing sw reset failure Tsuchiya Yuto
2020-11-08 11:31   ` Kalle Valo
2020-11-08 12:19     ` Tsuchiya Yuto
2020-11-10 18:50   ` [1/2] " Kalle Valo
2020-10-28 14:21 ` [PATCH 2/2] mwifiex: update comment for shutdown_sw()/reinit_sw() to reflect current state Tsuchiya Yuto

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=20201028142110.18144-1-kitakar@gmail.com \
    --to=kitakar@gmail.com \
    --cc=amitkarwar@gmail.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=davem@davemloft.net \
    --cc=ganapathi.bhat@nxp.com \
    --cc=huxinming820@gmail.com \
    --cc=kuba@kernel.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luzmaximilian@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=verdre@v0yd.nl \
    /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).