Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-wireless@vger.kernel.org, libertas-dev@lists.infradead.org
Subject: Re: [PATCH] move wlan_*_association_work from header to c file
Date: Mon, 22 Oct 2007 13:20:20 -0400	[thread overview]
Message-ID: <1193073620.4325.7.camel@localhost.localdomain> (raw)
In-Reply-To: <1192466593.15225.28.camel@localhost.localdomain>

On Mon, 2007-10-15 at 12:43 -0400, Dan Williams wrote:
> On Mon, 2007-10-15 at 16:49 +0200, Holger Schurig wrote:
> > > I assume you've been running it for a few days or so?
> > 
> > No. I just made this patch 6 hours ago.
> > 
> > I've used it so far only with WEP and no encryption at all, 
> > always as STA (no ad-hoc, no wpa-supplicant).
> > 
> > After all, the patch was created using "perl -pi -e" :-)
> > 
> > 
> > So far I found two quirks:
> > 
> > a) it's no longer /lib/modules/libertas/parameters/libertas_debug 
> > but /lib/modules/libertas/parameters/lbs_debug. As this is an 
> > ABI change, we might not want it.
> 
> Should keep ABI compat here.
> 
> > b) it's no longer <debugfs>/libertas_wireless/XXXX but 
> > <debugfs>/lbs_wireless/XXXX. Also an ABI change.
> 
> Should keep ABI compat here.
> 
> > 
> > I could make a "take 2" patch, but because of the size of the 
> > patch and the hassle to export it in an external git tree I'd 
> > rather create a fixup patch. But let's see what you un-earth.
> 
> Yeah, I'll keep looking through it.

So, I think the debugfs thing is fine to keep in sync with the driver
prefix.  But for now, lets keep the module name the same.  Can you
repost (with a link since it's so huge)?

I ran the driver for a while and nothing appears to have regressed
horribly from light testing a few large transfers.  Seems OK to push
into 2.6.25 to me.

Dan


  reply	other threads:[~2007-10-22 17:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11  9:51 [PATCH] move wlan_*_association_work from header to c file Holger Schurig
2007-10-11 11:05 ` Dan Williams
2007-10-11 12:57 ` John W. Linville
2007-10-11 14:16 ` Christoph Hellwig
2007-10-11 14:50   ` Dan Williams
2007-10-15  7:18     ` Holger Schurig
     [not found]       ` <200710151247.31049.hs4233@mail.mn-solutions.de>
2007-10-15 10:58         ` [PATCH] libertas: move to uniform lbs_/LBS_ namespace Holger Schurig
2007-10-15 11:07           ` Holger Schurig
2007-10-15 11:21             ` Johannes Berg
2007-10-15 12:26               ` Holger Schurig
2007-10-15 14:13       ` [PATCH] move wlan_*_association_work from header to c file Dan Williams
2007-10-15 14:28         ` Holger Schurig
2007-10-15 14:42           ` Dan Williams
2007-10-15 14:49             ` Holger Schurig
2007-10-15 16:43               ` Dan Williams
2007-10-22 17:20                 ` Dan Williams [this message]
2007-10-25  8:37                   ` Holger Schurig
2007-10-25 13:55                     ` Dan Williams
2007-10-26 11:43                     ` Holger Schurig
2007-11-06  1:16                       ` John W. Linville
2007-11-06 12:51                         ` Holger Schurig
2007-11-06 14:20                           ` Dan Williams
2007-10-22 17:17 ` Dan Williams

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=1193073620.4325.7.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=libertas-dev@lists.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