linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: Tomasz Guszkowski <tsg@o2.pl>
Cc: linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] p54usb: corrected USB ID for T-Com Sinus 154 data II
Date: Tue, 5 Feb 2013 22:43:43 +0100	[thread overview]
Message-ID: <201302052243.43567.chunkeey@googlemail.com> (raw)
In-Reply-To: <20130205221031.05608bc50352b172003ec69e@o2.pl>

(Added John [He takes all the driver patches ;).

John, do you want/need a line-wrapped commit message
of the original patch or is this OK?) 

On Tuesday, February 05, 2013 10:10:31 PM Tomasz Guszkowski wrote:
> Corrected USB ID for T-Com Sinus 154 data II. ISL3887-based.
> The device was tested in managed mode with no security, WEP
> 128 bit and WPA-PSK (TKIP) with firmware 2.13.1.0.lm87.arm
> (md5sum: 7d676323ac60d6e1a3b6d61e8c528248). It works.
> 
> Signed-off-by: Tomasz Guszkowski <tsg@o2.pl>
Cc: <stable@vger.kernel.org>
Acked-By: Christian Lamparter <chunkeey@googlemail.com>
> ---

I'll take care of updating the wireless.kernel.org wiki
<http://wireless.kernel.org/en/users/Drivers/p54/devices>
entry later this week.
 
OT: The latest supported firmware for LM87 is: 2.13.25.0.lm87.arm
Did you experience issues with the new version, or do you simply
stick with the old 2.13.1.0 because it does work just as well?

Regards

Christian

  reply	other threads:[~2013-02-05 21:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-05 21:10 [PATCH] p54usb: corrected USB ID for T-Com Sinus 154 data II Tomasz Guszkowski
2013-02-05 21:43 ` Christian Lamparter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-02-05 22:39 Tomasz Guszkowski
2013-02-06 22:39 Tomasz Guszkowski
2013-02-07 15:20 ` Christian Lamparter

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=201302052243.43567.chunkeey@googlemail.com \
    --to=chunkeey@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=tsg@o2.pl \
    /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).