linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Ian Molton <ian@mnementh.co.uk>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Franky Lin <franky.lin@broadcom.com>,
	brcm80211-dev-list@broadcom.com,
	Hante Meuleman <hante.meuleman@broadcom.com>
Subject: Re: brcmfmac bus level addressing issues.
Date: Wed, 19 Jul 2017 13:47:12 +0200	[thread overview]
Message-ID: <126c9c73-387e-e718-5ac8-e816ec922989@broadcom.com> (raw)
In-Reply-To: <feb0cba3-27da-6cab-316f-164867867cd6@mnementh.co.uk>

On 19-07-17 00:45, Ian Molton wrote:

[...]

> Fair enough - I guess now that its in the kernel it needs fixing before
> 4.13 - but I would argue that no new features should go into the driver
> for the short term once that is done. Lets give it a good spring clean.
> 
> I am, actually, able to put some time into this, and *want* to help - MY
> current employer would benefit greatly from this driver becoming stable.
> 
> (as it stands, back to back wpasuplpicant runs make it keel over, as
> does module unload and reload).

It is good to get such feedback. We should get in details about this.

>> So I am chasing that although I am actually on vacation.
> 
> Dude - enjoy your vacation. Seriously.
> 

[...]

>> That really has to wait until I return as well as running some tests on
>> older 4329 and some newer chipsets.
> 
> Fair. When do you return? No pressure - it just means I know I can hold
> off and do something else on my project until then.

Vacation is only this week.

Regards,
Arend

  parent reply	other threads:[~2017-07-19 11:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18  9:45 RFC: brcmfmac bus level addressing issues Ian Molton
2017-07-18 10:35 ` Hante Meuleman
2017-07-18 11:27   ` Ian Molton
     [not found]     ` <6fe08666ca09bf3c1d4476fdad8ce97a@mail.gmail.com>
     [not found]       ` <222e2bc1-4d8f-8133-4fa7-51a48f3de785@mnementh.co.uk>
2017-07-18 15:14         ` Ian Molton
2017-07-18 20:44           ` Arend van Spriel
2017-07-18 22:45             ` Ian Molton
2017-07-19  8:39               ` Hante Meuleman
2017-07-19  9:33                 ` Ian Molton
2017-07-19 11:47               ` Arend van Spriel [this message]
2017-07-19 19:25                 ` Ian Molton

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=126c9c73-387e-e718-5ac8-e816ec922989@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=brcm80211-dev-list@broadcom.com \
    --cc=franky.lin@broadcom.com \
    --cc=hante.meuleman@broadcom.com \
    --cc=ian@mnementh.co.uk \
    --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).