From: Arend van Spriel <arend@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 0/7] brcmfmac: nvram loading and code rework
Date: Sun, 26 Jul 2015 13:08:44 +0200 [thread overview]
Message-ID: <55B4BFBC.2030107@broadcom.com> (raw)
In-Reply-To: <87bnf2hng8.fsf@kamboji.qca.qualcomm.com>
On 07/23/2015 06:02 PM, Kalle Valo wrote:
> Arend van Spriel <arend@broadcom.com> writes:
>
>> On 07/19/2015 05:05 PM, Rafał Miłecki wrote:
>>> On 10 July 2015 at 20:31, Arend van Spriel <arend@broadcom.com> wrote:
>>>> This series comprises of following changes:
>>>> - support NVRAM loading for bcm47xx platform.
>>>> - revise announced interface combinations and validate against it.
>>>> - new debugfs entry for msgbuf protocol layer used with PCIe devices.
>>>> - couple of PCIe fixes.
>>>> - rework dealing with interface instances.
>>>
>>> I'm not sure which patch has caused this (I applied all of them except
>>> for the 1st one) but now brcmfmac fails totally:
>>>> Unable to handle kernel NULL pointer dereference at virtual address 00000014
>>>
>>> I'm afraid I won't be able to spend any more time of this soon, so can
>>> you try to reproduce this problem, please?
>>
>> So what is your scenario for this issue. Multiple AP interfaces?
>
> Arend, what should I do with this patchset?
>
Let's drop the series. I will resend when getting back to work. The
combination of my sons condition and getting a little baby sister is
quite impacting on our personal life so professional life has to wait.
Regards,
Arend
next prev parent reply other threads:[~2015-07-26 11:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 18:31 [PATCH 0/7] brcmfmac: nvram loading and code rework Arend van Spriel
2015-07-10 18:31 ` [PATCH 1/7] brcmfmac: Add support for host platform NVRAM loading Arend van Spriel
2015-07-11 17:09 ` Rafał Miłecki
2015-08-19 21:21 ` [PATCH v2 " Arend van Spriel
2015-08-19 21:43 ` Arend van Spriel
2015-08-20 15:53 ` Rafał Miłecki
2015-08-20 16:06 ` Arend van Spriel
2015-08-20 16:21 ` Rafał Miłecki
2015-08-20 15:59 ` Rafał Miłecki
2015-08-20 16:14 ` Arend van Spriel
2015-07-10 18:31 ` [PATCH 2/7] brcmfmac: correct interface combination info Arend van Spriel
2015-07-10 18:31 ` [PATCH 3/7] brcmfmac: Increase nr of supported flowrings Arend van Spriel
2015-07-10 18:31 ` [PATCH 4/7] brcmfmac: add debugfs entry for msgbuf statistics Arend van Spriel
2015-07-10 18:31 ` [PATCH 5/7] brcmfmac: make use of cfg80211_check_combinations() Arend van Spriel
2015-07-10 18:31 ` [PATCH 6/7] brcmfmac: consolidate ifp lookup in driver core Arend van Spriel
2015-07-10 18:31 ` [PATCH 7/7] brcmfmac: block the correct flowring when backup queue overflow Arend van Spriel
2015-07-19 15:05 ` [PATCH 0/7] brcmfmac: nvram loading and code rework Rafał Miłecki
2015-07-20 17:14 ` Arend van Spriel
2015-07-23 16:02 ` Kalle Valo
2015-07-26 11:08 ` Arend van Spriel [this message]
2015-07-26 12:08 ` Kalle Valo
2015-07-26 15:40 ` Rafał Miłecki
2015-08-12 8:58 ` Arend van Spriel
2015-08-12 14:07 ` Rafał Miłecki
2015-08-19 14:58 ` Rafał Miłecki
2015-08-19 23:06 ` Rafał Miłecki
2015-08-20 10:23 ` Arend van Spriel
2015-08-20 15:51 ` Rafał Miłecki
2015-08-20 19:41 ` Arend van Spriel
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=55B4BFBC.2030107@broadcom.com \
--to=arend@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.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).