All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Florian Achleitner <flo@fopen.at>
Cc: linux-wireless@vger.kernel.org,
	Amitkumar Karwar <akarwar@marvell.com>,
	Avinash Patil <patila@marvell.com>,
	Maithili Hinge <maithili@marvell.com>
Subject: Re: [PATCH] mwifiex: Trigger a card reset on "DNLD_CMD: host to card failed".
Date: Mon, 11 May 2015 09:35:35 +0300	[thread overview]
Message-ID: <87fv73liyw.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <5773845.ktey5e8Qlm@flobuntu> (Florian Achleitner's message of "Sat, 09 May 2015 18:18:02 +0200")

Florian Achleitner <flo@fopen.at> writes:

> On Saturday 09 May 2015 16:35:03 Kalle Valo wrote:
>> Florian Achleitner <flo@fopen.at> writes:
>> > Whenever this problem occurs, the driver can not continue. Thus,
>> > trigger a card reset to restart the module firmware. Other firmware
>> > communication issues are resolved by this last resort.
>> > Also dump registers, to eventually allow some diagnostics.
>> > 
>> > Signed-off-by: Florian Achleitner <flo@fopen.at>
>> 
>> Doesn't apply to wireless-drivers-next.git. Can you rebase, please?
>
> Please drop my patch! We agreed that it likely tries to fix a problem actually 
> caused in MMC system.

Sorry, I had missed that as patchwork didn't contain anything. In the
future it's a good idea to reply to the patch and say something like
"Kalle, please drop this because of foo". That way I see it in
patchwork:

https://patchwork.kernel.org/patch/6224961/

-- 
Kalle Valo

  reply	other threads:[~2015-05-11  6:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16  9:10 [RFC/PATCH] mwifiex: Driver - Firmware Glitches Florian Achleitner
2015-04-16  9:14 ` [PATCH] mwifiex: Trigger a card reset on "DNLD_CMD: host to card failed" Florian Achleitner
2015-05-09 13:35   ` Kalle Valo
2015-05-09 16:18     ` Florian Achleitner
2015-05-11  6:35       ` Kalle Valo [this message]
2015-04-16  9:30 ` [RFC/PATCH] mwifiex: Driver - Firmware Glitches Amitkumar Karwar
2015-04-16 10:34   ` Florian Achleitner
2015-04-16 11:21     ` Amitkumar Karwar
2015-04-16 13:19       ` Florian Achleitner
2015-04-17  8:29         ` Florian Achleitner
2015-04-17  9:45           ` Amitkumar Karwar
2015-04-23  8:33             ` Florian Achleitner
2015-04-23  8:43               ` James Cameron
2015-04-23  9:48                 ` Avinash Patil
2015-04-16 10:19 ` James Cameron
2015-04-16 10:43   ` Florian Achleitner
2015-04-16 11:11     ` Avinash Patil

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=87fv73liyw.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=akarwar@marvell.com \
    --cc=flo@fopen.at \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maithili@marvell.com \
    --cc=patila@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.