linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ipw3945-devel@lists.sourceforge.net"
	<ipw3945-devel@lists.sourceforge.net>
Subject: Re: [PATCH 6/6] iwlagn: define 130 series of WiFi/BT combo devices
Date: Wed, 06 Oct 2010 16:32:02 -0700	[thread overview]
Message-ID: <1286407922.12594.27.camel@wwguy-ubuntu> (raw)
In-Reply-To: <AANLkTin6wQzKn885CWxbaX2o1ERXWsu73iZVHhcuB5z1@mail.gmail.com>

Hi Julian,

On Wed, 2010-10-06 at 16:28 -0700, Julian Calaby wrote:
> On Thu, Oct 7, 2010 at 02:23, Wey-Yi Guy <wey-yi.w.guy@intel.com> wrote:
> > add new structures and defines need to identify 130 devices.
> >
> > Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> > ---
> >  drivers/net/wireless/iwlwifi/iwl-6000.c |   44 +++++++++++++++++++++++++++++++
> >  drivers/net/wireless/iwlwifi/iwl-agn.c  |   10 +++++++
> >  drivers/net/wireless/iwlwifi/iwl-agn.h  |    2 +
> >  3 files changed, 56 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/net/wireless/iwlwifi/iwl-6000.c b/drivers/net/wireless/iwlwifi/iwl-6000.c
> > index 5866ad8..43ec898 100644
> > --- a/drivers/net/wireless/iwlwifi/iwl-6000.c
> > +++ b/drivers/net/wireless/iwlwifi/iwl-6000.c
> > @@ -75,6 +77,9 @@
> >  #define _IWL6000G2B_MODULE_FIRMWARE(api) IWL6000G2B_FW_PRE #api ".ucode"
> >  #define IWL6000G2B_MODULE_FIRMWARE(api) _IWL6000G2B_MODULE_FIRMWARE(api)
> >
> > +#define IWL130_FW_PRE "iwlwifi-130-"
> > +#define _IWL100_MODULE_FIRMWARE(api) IWL130_FW_PRE #api ".ucode"
> > +#define IWL100_MODULE_FIRMWARE(api) _IWL130_MODULE_FIRMWARE(api)
> 
> I haven't looked at the rest of the file, but is this correct: you're
> defining IWL100_MODULE_FIRMWARE using the IWL1*3*0 definitions, which
> don't seem to be defined.
> 
> (I note that these definitions aren't used, but still.....)
> 
Good catch, you are correct. I will push another patch to fix it.

Thanks
Wey



      reply	other threads:[~2010-10-06 23:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06 15:23 [PATCH 0/6] update for 2.6.37 Wey-Yi Guy
2010-10-06 15:23 ` [PATCH 1/6] iwlwifi: schedule to deprecate software scan support Wey-Yi Guy
2010-10-06 17:36   ` John W. Linville
2010-10-06 17:48     ` Johannes Berg
2010-10-06 17:51     ` Guy, Wey-Yi
2010-10-06 19:03       ` John W. Linville
2010-10-06 19:43         ` Guy, Wey-Yi
2010-10-07  8:39         ` Johannes Berg
2010-10-07 18:04           ` John W. Linville
2010-10-07 18:31           ` [ipw3945-devel] " Daniel Halperin
2010-10-07 18:36             ` Johannes Berg
2010-10-06 15:23 ` [PATCH 2/6] iwlagn: reduce redundant parameter definitions Wey-Yi Guy
2010-10-06 15:23 ` [PATCH 3/6] iwlagn: rename iwl5000_tx_power_dbm_cmd Wey-Yi Guy
2010-10-06 15:23 ` [PATCH 4/6] iwlwifi: remove uncorrect comments Wey-Yi Guy
2010-10-06 15:23 ` [PATCH 5/6] iwlagn: rename iwl5000_tx_resp Wey-Yi Guy
2010-10-06 15:23 ` [PATCH 6/6] iwlagn: define 130 series of WiFi/BT combo devices Wey-Yi Guy
2010-10-06 23:28   ` Julian Calaby
2010-10-06 23:32     ` Guy, Wey-Yi [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=1286407922.12594.27.camel@wwguy-ubuntu \
    --to=wey-yi.w.guy@intel.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=julian.calaby@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).