From: Larry Finger <Larry.Finger@lwfinger.net>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Ivo Van Doorn <ivdoorn@gmail.com>,
linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: [PATCH] rt2x00: Update rt2860/rt2870 firmware
Date: Thu, 17 Feb 2011 15:49:31 -0600 [thread overview]
Message-ID: <4D5D97EB.9020406@lwfinger.net> (raw)
In-Reply-To: <4D5D9594.7010904@gmail.com>
On 02/17/2011 03:39 PM, Xose Vazquez Perez wrote:
> On 02/17/2011 08:43 PM, Ivo Van Doorn wrote:
>
>> I have already send a patch to update the
>> firmwares some time ago already.
>>
>> If there is another update, feel free to send a new patch
>> to the linux-firmware maintainer.
>
> I did it _ten_ months ago, but no luck. So I asked you to do it.
> Again to /dev/null. Thanks anyway.
>
> next step?
Did your proposed change have a good/strong reference to the license file in
WHENCE? My experience is that the maintainer drops changes that do not, usually
without comment. I also found that "found in hex form in source" did not work
the way it did for your previous versions. Only when I provided a license from
the vendor did I get anywhere. Is LICENCE.ralink-firmware.txt valid for this new
version?
Larry
next prev parent reply other threads:[~2011-02-17 21:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 18:25 [PATCH] rt2x00: Update rt2860/rt2870 firmware Xose Vazquez Perez
2011-02-17 19:42 ` Xose Vazquez Perez
2011-02-17 19:43 ` Ivo Van Doorn
2011-02-17 21:39 ` Xose Vazquez Perez
2011-02-17 21:49 ` Larry Finger [this message]
2011-02-17 22:11 ` Xose Vazquez Perez
-- strict thread matches above, loose matches on Subject: below --
2010-10-30 13:06 Ivo van Doorn
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=4D5D97EB.9020406@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=users@rt2x00.serialmonkey.com \
--cc=xose.vazquez@gmail.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 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).