From: Ellie Reeves <ellierevves@gmail.com>
To: Ganapathi Bhat <gbhat@marvell.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"amitkarwar@gmail.com" <amitkarwar@gmail.com>,
Nishant Sarmukadam <nishants@marvell.com>,
Xinming Hu <huxm@marvell.com>
Subject: Re: [EXT] Marvell Mwifiex wireless driver: mwifiex_pcie broken on Marvell ESPRESSOBin
Date: Thu, 30 Nov 2017 05:57:33 -0500 [thread overview]
Message-ID: <44a8b2b8-d798-0e5d-0da1-c2bea52463bc@gmail.com> (raw)
In-Reply-To: <6e26f5b1-10a7-b7fc-1518-f0d0f66a50e9@gmail.com>
Hi again,
I tried the few patch that made it to this list without any real
success... I suppose the issue isn't that easy to reproduce on your side
so... Shall I try a git bisect, building only that module and see if I
can narrow it down a bit ? I'm no expert with git or git bisect for that
matter, but I'm guessing building the module will be less time consuming
than building the entire kernel... Unless you want me to do something
else to help in debugging. I want to help as much as I can to solve
this, heh, even despite me annoying my father because his wifi access
point goes poof. :)
Thanks,
--
Ellie Reeves
next prev parent reply other threads:[~2017-11-30 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 15:15 Marvell Mwifiex wireless driver: mwifiex_pcie broken on Marvell ESPRESSOBin Ellie Reeves
2017-11-20 13:53 ` [EXT] " Ganapathi Bhat
2017-11-20 20:51 ` Ellie Reeves
2017-11-22 10:13 ` Ellie Reeves
2017-11-22 12:34 ` Ganapathi Bhat
2017-11-22 13:14 ` Ellie Reeves
2017-11-30 10:57 ` Ellie Reeves [this message]
2017-12-01 15:37 ` Ellie Reeves
2017-12-13 10:34 ` Ganapathi Bhat
2017-12-13 10:46 ` Ellie Reeves
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=44a8b2b8-d798-0e5d-0da1-c2bea52463bc@gmail.com \
--to=ellierevves@gmail.com \
--cc=amitkarwar@gmail.com \
--cc=gbhat@marvell.com \
--cc=huxm@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@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.