linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Kalle Valo <kalle.valo@iki.fi>
Cc: "ext John W. Linville" <linville@tuxdriver.com>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: linux-next: Tree for November 2 (wireless/wl1271)
Date: Mon, 09 Nov 2009 13:20:55 +0200	[thread overview]
Message-ID: <4AF7FB17.7020604@nokia.com> (raw)
In-Reply-To: <87ljiifwnc.fsf@purkki.valot.fi>

ext Kalle Valo wrote:
> Luciano Coelho <luciano.coelho@nokia.com> writes:
> 
>> Coelho Luciano (Nokia-D/Helsinki) wrote:
>>> ext John W. Linville wrote:
>>>> Helps if I actually Cc: Luca...
>>> Yes, it does. :) I would see this at some point but CCing me speed
>>> things up quite a lot.
>>
>> BTW, I think we need this for wl1251 as well.  CC'ing Kalle too.
> 
> Thanks, but upstream wl1251 doesn't have ARP filter. There is an
> internal patch but I haven't submitted it, yet.

Oh, okay.  Sorry for not checking.  I just noticed that our wl1271 
implementation was based on the implementation for wl1251, so I just assumed it 
was needed as well.

-- 
Cheers,
Luca.

  reply	other threads:[~2009-11-09 11:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02  6:38 linux-next: Tree for November 2 Stephen Rothwell
2009-11-02  9:12 ` [powerpc] Next tree Nov 2 : kernel BUG at mm/mmap.c:2135! Sachin Sant
2009-11-04 12:38   ` Sachin Sant
2009-11-05  0:16     ` David Gibson
2009-11-05  4:42       ` Sachin Sant
2009-11-12 11:16       ` Sachin Sant
2009-11-13  1:37         ` David Gibson
2009-11-13  2:10           ` David Gibson
2009-11-13  9:35             ` Sachin Sant
2009-11-17  5:25               ` David Gibson
2009-11-17  7:37                 ` Sachin Sant
2009-11-18  2:36                   ` David Gibson
     [not found] ` <20091102173845.210d1c57.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-11-02 17:13   ` linux-next: Tree for November 2 (usb/whci) Randy Dunlap
2009-11-11 17:04     ` Randy Dunlap
     [not found]       ` <20091111090403.5fb0229e.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-11-11 17:30         ` Greg KH
2009-11-17 11:40           ` David Vrabel
2009-11-17 15:51             ` Randy Dunlap
     [not found]               ` <20091117075101.0bf72415.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-11-17 18:49                 ` David Vrabel
2009-11-02 18:01 ` linux-next: Tree for November 2 (wireless/wl1271) Randy Dunlap
2009-11-02 18:44   ` John W. Linville
2009-11-02 18:48     ` John W. Linville
2009-11-02 21:10       ` Luciano Coelho
2009-11-03  6:03         ` Luciano Coelho
2009-11-07 10:37           ` Kalle Valo
2009-11-09 11:20             ` Luciano Coelho [this message]
2009-11-04 21:56 ` [PATCH] staging: RTL8192SU depends on USB Randy Dunlap

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=4AF7FB17.7020604@nokia.com \
    --to=luciano.coelho@nokia.com \
    --cc=kalle.valo@iki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    /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).