Linux wireless drivers development
 help / color / mirror / Atom feed
From: Luciano Coelho <coelho@ti.com>
To: Eliad Peller <eliad@wizery.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH V2 1/2] wl12xx: consider encryption when configuring auto arp template
Date: Tue, 26 Apr 2011 11:54:41 +0300	[thread overview]
Message-ID: <1303808081.2172.0.camel@pimenta> (raw)
In-Reply-To: <BANLkTinN2jZdqeCPi6R+tCoF=318UJ_qyQ@mail.gmail.com>

On Tue, 2011-04-26 at 11:39 +0300, Eliad Peller wrote:
> >> @@ -2749,8 +2764,10 @@ static void
> wl1271_bss_info_changed_sta(struct wl1271 *wl,
> >>                       ret = wl1271_acx_arp_ip_filter(wl,
> >>                               ACX_ARP_FILTER_ARP_FILTERING,
> >>                               addr);
> >> -             } else
> >> +             } else {
> >> +                     wl->ip_addr = 0;
> >>                       ret = wl1271_acx_arp_ip_filter(wl, 0, addr);
> >> +             }
> >
> > This is not important at all, but maybe it's a bit cleaner: you
> could
> > remove the addr argument in wl1271_acx_arp_ip_filter() and always
> use
> > wl->ip_addr instead? You could then also get rid of the local addr
> here.
> >
> in fact, since we are going toward multi-role fw, i do try to avoid
> using the global wl struct as much as possible.
> anyway, i didn't change this function, so i don't think it's the right
> patch to change it.
> (we should probably change a lot of functions after we'll have a
> per-interface data) 

Agreed. :)

-- 
Cheers,
Luca.


      reply	other threads:[~2011-04-26  8:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14  9:47 [PATCH V2 1/2] wl12xx: consider encryption when configuring auto arp template Eliad Peller
2011-04-14  9:47 ` [PATCH V2 2/2] wl12xx: Revert "wl12xx: disable auto-arp" Eliad Peller
2011-04-26  6:53 ` [PATCH V2 1/2] wl12xx: consider encryption when configuring auto arp template Luciano Coelho
2011-04-26  8:39   ` Eliad Peller
2011-04-26  8:54     ` Luciano Coelho [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=1303808081.2172.0.camel@pimenta \
    --to=coelho@ti.com \
    --cc=eliad@wizery.com \
    --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