From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] compat-2.6: Add AR9170 driver
Date: Mon, 23 Mar 2009 18:11:48 -0700 [thread overview]
Message-ID: <43e72e890903231811t2ecf7f89lb72fc79ffd37a96@mail.gmail.com> (raw)
In-Reply-To: <43e72e890903231740m6b804fa5mfdcfe57ae07702a7@mail.gmail.com>
On Mon, Mar 23, 2009 at 5:40 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> On Mon, Mar 23, 2009 at 5:19 PM, Hauke Mehrtens <hauke@hauke-m.de> wrote:
>> This adds the AR9170 driver to compat-wireless.
>
> Thanks applied and new tarball regenerated.
>
> The patch commit log (which cannot be seen as the patch was attached)
> only enables ar9170 for >= 2.6.28. If someone wants to get this on
> 2.6.27 you'll just have to backport the routines which fail to
> compile. Patches welcomed of course.
I did some quick review on this. One of the routines I had heard fails
on 2.6.27 is usb_poison_anchored_urbs. This was added via 6a2839b.
This just adds the routine, the users are the drivers themselves. To
poison a URB it makes use of the extends the struct usb_anchor, so
directly porting it doesn't seem to make sense. Best bet seems to be
just backporting to not poison and do a replacement call.
Fun enough ar9170 is currently the only driver using this.
Hm, not sure if a no-op would do it.
Luis
prev parent reply other threads:[~2009-03-24 1:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 0:19 [PATCH] compat-2.6: Add AR9170 driver Hauke Mehrtens
2009-03-24 0:40 ` Luis R. Rodriguez
2009-03-24 1:11 ` Luis R. Rodriguez [this message]
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=43e72e890903231811t2ecf7f89lb72fc79ffd37a96@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=hauke@hauke-m.de \
--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;
as well as URLs for NNTP newsgroup(s).