From: Larry Finger <Larry.Finger@lwfinger.net>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: dwmw2@infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rtlwifi: Add new firmware files for rtl8192cu
Date: Sun, 13 Oct 2013 19:15:12 -0500 [thread overview]
Message-ID: <525B3790.8040400@lwfinger.net> (raw)
In-Reply-To: <1381691458.1301.63.camel@deadeye.wl.decadent.org.uk>
On 10/13/2013 02:10 PM, Ben Hutchings wrote:
> On Tue, 2013-10-08 at 10:00 -0500, Larry Finger wrote:
>> On 09/26/2013 05:26 PM, Larry Finger wrote:
>>> The vendor driver rtl8188C_8192C_8192D_usb_linux_v3.4.2_3727.20120404
>>> includes new firmware files. These were extracted from data statements
>>> in that driver to form these files.
>>>
>>> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
>>> ---
>>> WHENCE | 3 +++
>>> rtlwifi/rtl8192cufw_A.bin | Bin 0 -> 16116 bytes
>>> rtlwifi/rtl8192cufw_B.bin | Bin 0 -> 16096 bytes
>>> rtlwifi/rtl8192cufw_TMSC.bin | Bin 0 -> 16116 bytes
>>> 4 files changed, 3 insertions(+)
>>> create mode 100644 rtlwifi/rtl8192cufw_A.bin
>>> create mode 100644 rtlwifi/rtl8192cufw_B.bin
>>> create mode 100644 rtlwifi/rtl8192cufw_TMSC.bin
>>
>> I understand that you probably have too much to do, but I am inquiring about the
>> status of this submission and "[PATCH] rtlwifi: Add new firmware files for
>> rtl8188eu" that I sent on 09/27/2013.
> [...]
>
> I don't seem to have received them, but I assume the patches you sent
> after this are the same again.
Yes. I found the problem that caused you not to receive them.
Thanks,
Larry
next prev parent reply other threads:[~2013-10-14 0:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1380234392-31062-1-git-send-email-Larry.Finger@lwfinger.net>
2013-10-08 15:00 ` [PATCH] rtlwifi: Add new firmware files for rtl8192cu Larry Finger
2013-10-13 19:10 ` Ben Hutchings
2013-10-14 0:15 ` Larry Finger [this message]
[not found] <525494DB.2060301@lwfinger.net>
2013-10-13 20:06 ` Ben Hutchings
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=525B3790.8040400@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=ben@decadent.org.uk \
--cc=dwmw2@infradead.org \
--cc=linux-wireless@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