linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chr <chunkeey@web.de>
To: Michael Wu <flamingice@sourmilk.net>
Cc: Hans de Goede <j.w.r.degoede@hhs.nl>, linux-wireless@vger.kernel.org
Subject: Re: Recent linux-wireless git changes have broken my prism54pci card
Date: Thu, 30 Aug 2007 13:16:42 +0200	[thread overview]
Message-ID: <200708301316.42945.chunkeey@web.de> (raw)
In-Reply-To: <200708300152.27736.flamingice@sourmilk.net>

On Thursday, 30. August 2007, Michael Wu wrote:
> On Tuesday 28 August 2007 15:32, Chr wrote:
> > Here we are:
> >
> > series:
> > p54-pull-padding2.diff
> Looks okay, but it seems to do more than just account for padding. I'm okay 
> with those changes too.
> 
Ok!

> > p54-support-older-firmwares.diff
> The new information pulled from parsing the firmware isn't used anywhere but 
> in this function.. no need to keep that information in the private structure.
> 
Yes, the firmware version string could be freed right after the printk...
but I would like to keep the fw_variant for "further" patches, since the
softmac protocol has changed a bit throughout 2.4 - 2.13.1 firmwares. 

> Thanks,
> -Michael Wu


Thanks,
	Chr. 



  reply	other threads:[~2007-08-30 11:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13  5:50 Recent linux-wireless git changes have broken my prism54pci card Hans de Goede
2007-08-13  6:18 ` Michael Wu
2007-08-13  6:33   ` Hans de Goede
2007-08-13  6:46     ` Andy Green
2007-08-13  7:49       ` Hans de Goede
2007-08-13  7:58         ` Michael Wu
2007-08-13  8:05           ` Andy Green
2007-08-13 11:58           ` Hans de Goede
2007-08-13 20:14             ` Michael Wu
2007-08-13 22:25               ` Chr
2007-08-14  8:10                 ` Hans de Goede
2007-08-14 18:29                   ` Chr
2007-08-20  0:44                   ` Chr
2007-08-20  2:32                     ` Larry Finger
2007-08-20  7:52                     ` Hans de Goede
2007-08-20 11:51                       ` Chr
2007-08-20 12:17                         ` Johannes Berg
2007-08-20 22:14                           ` Chr
2007-08-23 11:24                         ` Hans de Goede
2007-08-23 14:43                           ` Chr
2007-08-23 14:36                             ` Hans de Goede
2007-08-23 21:52                             ` Hans de Goede
2007-08-23 23:00                               ` Chr
2007-08-24  9:45                                 ` Hans de Goede
2007-08-28 19:32                                   ` Chr
2007-08-30  5:52                                     ` Michael Wu
2007-08-30 11:16                                       ` Chr [this message]
2007-08-31 21:27                                       ` [PATCH 1/2] p54: various fixes Chr
2007-08-31 21:27                                       ` [PATCH 2/2] p54: disable QoS on older firmwares Chr
2007-09-01  4:58                                         ` Michael Wu
2007-09-01 16:54                                           ` [PATCH 2/2 v2] " Chr
2007-08-13 13:14       ` Recent linux-wireless git changes have broken my prism54pci card Johannes Berg

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=200708301316.42945.chunkeey@web.de \
    --to=chunkeey@web.de \
    --cc=flamingice@sourmilk.net \
    --cc=j.w.r.degoede@hhs.nl \
    --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).