mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] b43: support new RX header, noticed to be used in 598.314+ fw
Date: Mon, 26 Dec 2011 16:29:19 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.00.1112261608140.12108@axis700.grange> (raw)

Hi

Sorry for "simulating" a reply - I'm not subscribed to linux-wireless, so,
cannot (easily) reply.
   
The commit in subject line

commit 17030f48e31adde5b043741c91ba143f5f7db0fd
From: Rafał Miłecki <zajec5@gmail.com>
Date: Thu, 11 Aug 2011 17:16:27 +0200
Subject: [PATCH] b43: support new RX header, noticed to be used in 598.314+ fw

breaks my b43 SDIO card in 3.2-ish kernels. Given the approaching 
3.2-final release, would be nice to have it fixed before that. The card 
I've got is marked with some "SD-Link11g" from some "C-guys, Inc." from 
Taiwan:-) Using firmware version 410.31754. Do I really _have_ to update 
or is the driver supposed to handle "all" firmware versions, or at least 
not drop ones, it used to support before?

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/

             reply	other threads:[~2011-12-26 15:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-26 15:29 Guennadi Liakhovetski [this message]
2011-12-26 17:18 ` Larry Finger
2011-12-26 17:28 ` [PATCH] b43: fix regression in PIO case Guennadi Liakhovetski
2011-12-26 17:51   ` Larry Finger
2011-12-26 18:17     ` Guennadi Liakhovetski
2011-12-26 18:32       ` Larry Finger
2011-12-27 18:47   ` Rafał Miłecki
2011-12-27 23:05     ` Guennadi Liakhovetski
2011-12-27 23:47       ` Larry Finger
2011-12-28  0:00         ` Guennadi Liakhovetski
2011-12-28  0:11           ` Larry Finger
2011-12-28 16:37             ` Guennadi Liakhovetski

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=alpine.DEB.2.00.1112261608140.12108@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=zajec5@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

all inboxes | Powered by JetHome®