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 V3 0/6] brcmfmac: nvram loading and code rework
Date: Tue, 25 Aug 2015 15:36:39 +0300 [thread overview]
Message-ID: <87egir5yug.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <55D64555.2090207@broadcom.com> (Arend van Spriel's message of "Thu, 20 Aug 2015 23:23:33 +0200")
Arend van Spriel <arend@broadcom.com> writes:
> On 08/20/2015 11:20 PM, Rafał Miłecki wrote:
>> On 20 August 2015 at 22:06, 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.
>>> - PCIe fix for handling queue overflow.
>>> - support more firmware events (for bcm4339 firmware).
>>>
>>> The series is intended for v4.3 kernel and applies to the master branch
>>> of the wireless-drivers-next repository. Removed patch from this series
>>> that reportedly has issue on OpenWrt platform.
>>
>> Tested-by: Rafał Miłecki <zajec5@gmail.com>
>>
>> No regression with this version, getting platform NVRAM works.
>
> Thanks, Rafał
>
> Kalle,
>
> Will you add the "Tested-by:" or should I?
To save time I normally try avoid adding those myself, but what one can
do is to reply to the patch (not to the cover letter) with the
"Tested-by" line. Patchwork should when automatically add that when I
apply the patch.
At least Acked-by works like this, I would assume it's the same with
Tested-by as well. Does anyone know?
--
Kalle Valo
next prev parent reply other threads:[~2015-08-25 12:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 20:06 [PATCH V3 0/6] brcmfmac: nvram loading and code rework Arend van Spriel
2015-08-20 20:06 ` [PATCH V3 1/6] brcmfmac: correct interface combination info Arend van Spriel
2015-08-25 12:33 ` [V3,1/6] " Kalle Valo
2015-08-20 20:06 ` [PATCH V3 2/6] brcmfmac: add debugfs entry for msgbuf statistics Arend van Spriel
2015-08-20 20:06 ` [PATCH V3 3/6] brcmfmac: make use of cfg80211_check_combinations() Arend van Spriel
2015-08-20 20:06 ` [PATCH V3 4/6] brcmfmac: block the correct flowring when backup queue overflow Arend van Spriel
2015-08-20 20:06 ` [PATCH V3 5/6] brcmfmac: bump highest event number for 4339 firmware Arend van Spriel
2015-08-20 20:06 ` [PATCH V3 6/6] brcmfmac: Add support for host platform NVRAM loading Arend van Spriel
2015-08-20 21:20 ` [PATCH V3 0/6] brcmfmac: nvram loading and code rework Rafał Miłecki
2015-08-20 21:23 ` Arend van Spriel
2015-08-20 21:26 ` Rafał Miłecki
2015-08-25 12:36 ` Kalle Valo [this message]
2015-08-25 16:09 ` Rafał Miłecki
2015-08-25 16:42 ` Arend van Spriel
2015-08-25 16:53 ` Kalle Valo
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=87egir5yug.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