linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Arend van Spriel <arend@broadcom.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 00/16] brcmfmac: new device support and P2P fixes
Date: Mon, 21 Sep 2015 15:17:51 +0300	[thread overview]
Message-ID: <871tdsq840.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <55FD8E39.2010104@broadcom.com> (Arend van Spriel's message of "Sat, 19 Sep 2015 18:32:57 +0200")

Arend van Spriel <arend@broadcom.com> writes:

> On 09/19/2015 05:05 PM, Rafał Miłecki wrote:
>> On 19 September 2015 at 16:24, Arend van Spriel <arend@broadcom.com> wrote:
>>
>>> I replied to first and last patch so you are acknowledged for testing. Doing
>>> it for each patch in the series was too much trouble for me :-p
>>
>> Sure. I didn't really bother because of old patchwork installed on
>> kernel.org. It doesn't understand UTF and malforms my name forcing
>> Kalle to fixup patches manually:
>> https://patchwork.kernel.org/patch/7220471/
>> https://patchwork.kernel.org/patch/7220401/
>
> So the patchwork upgrade request did not get through yet ;-)

At least I haven't heard anything and the ticket is still open :/

-- 
Kalle Valo

  reply	other threads:[~2015-09-21 12:17 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18 20:08 [PATCH 00/16] brcmfmac: new device support and P2P fixes Arend van Spriel
2015-09-18 20:08 ` [PATCH 01/16] brcmfmac: Fix exception handling Arend van Spriel
2015-09-19  9:43   ` Arend van Spriel
2015-09-29  7:57   ` [01/16] " Kalle Valo
2015-09-18 20:08 ` [PATCH 02/16] brcmfmac: Add support for the BCM4350 PCIE device Arend van Spriel
2015-09-18 20:08 ` [PATCH 03/16] brcmfmac: Fix set and get tx-power functions Arend van Spriel
2015-09-18 20:08 ` [PATCH 04/16] brcmfmac: Only assign primary netdev to if2bss array Arend van Spriel
2015-09-18 20:08 ` [PATCH 05/16] brcmfmac: Inform p2p module about p2pon through API Arend van Spriel
2015-09-18 20:08 ` [PATCH 06/16] brcmfmac: Fix bug in flowring management Arend van Spriel
2015-09-18 20:08 ` [PATCH 07/16] brcmfmac: Make p2pon module param always available Arend van Spriel
2015-09-18 20:08 ` [PATCH 08/16] brcmfmac: Workaround in change vif for wpa_supplicant support Arend van Spriel
2015-09-18 20:08 ` [PATCH 09/16] brcmfmac: Deleting of p2p device is leaking memory Arend van Spriel
2015-09-18 20:08 ` [PATCH 10/16] brcmfmac: Only handle p2p_stop_device if vif is valid Arend van Spriel
2015-09-18 20:08 ` [PATCH 11/16] brcmfmac: Fix p2p bug for older firmwares Arend van Spriel
2015-09-18 20:08 ` [PATCH 12/16] brcmfmac: Add module parameter to disable features Arend van Spriel
2015-09-18 20:08 ` [PATCH 13/16] brcmfmac: Fix race condition bug when deleting p2p interface Arend van Spriel
2015-09-18 20:08 ` [PATCH 14/16] brcmfmac: Add support for the BCM4365 and BCM4366 PCIE devices Arend van Spriel
2015-09-18 20:08 ` [PATCH 15/16] brcmfmac: Fix TDLS setup by properly handling p2p noif Arend van Spriel
2015-09-18 20:08 ` [PATCH 16/16] brcmfmac: Accept events when TDLS is used in combination with p2p Arend van Spriel
2015-09-19  9:43   ` Arend van Spriel
2015-09-18 21:29 ` [PATCH 00/16] brcmfmac: new device support and P2P fixes Rafał Miłecki
2015-09-19  9:40   ` Arend van Spriel
2015-09-19 14:24   ` Arend van Spriel
2015-09-19 15:05     ` Rafał Miłecki
2015-09-19 16:32       ` Arend van Spriel
2015-09-21 12:17         ` Kalle Valo [this message]
2015-09-28 17:48 ` Arend van Spriel
2015-09-28 18:14   ` Pending patches in patchwork and their states Kalle Valo
2016-01-09 23:48 ` [PATCH 00/16] brcmfmac: new device support and P2P fixes Rafał Miłecki
2016-01-10 20:59   ` Arend van Spriel
2016-01-10 21:12     ` Rafał Miłecki
2016-01-11  8:33       ` 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=871tdsq840.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=arend@broadcom.com \
    --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).