From: Wolfram Sang <wsa@the-dreams.de>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: linux-wireless@vger.kernel.org,
driverdev-devel@linuxdriverproject.org,
kernelnewbies@kernelnewbies.org
Subject: Re: ks7010 firmware upload fail
Date: Mon, 5 Jun 2017 09:22:12 +0200 [thread overview]
Message-ID: <20170605072212.GB1495@katana> (raw)
In-Reply-To: <20170605025637.GA23011@eros>
[-- Attachment #1: Type: text/plain, Size: 244 bytes --]
Tobin,
> My question is should I be digging further into the MMC code or be doing
> something else with the driver code?
So, you haven't found any branch that worked? No plain v4.9 or the
gen3-sdio branch from my tree?
Regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-05 7:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 2:56 ks7010 firmware upload fail Tobin C. Harding
2017-06-05 7:22 ` Wolfram Sang [this message]
2017-06-05 10:24 ` Tobin C. Harding
2017-06-06 0:07 ` Brian Masney
2017-06-06 2:34 ` Tobin C. Harding
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=20170605072212.GB1495@katana \
--to=wsa@the-dreams.de \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-wireless@vger.kernel.org \
--cc=me@tobin.cc \
/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