From: Kalle Valo <kvalo@codeaurora.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Arend van Spriel <arend.vanspriel@broadcom.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com
Subject: Re: [PATCH 0/4] brcmfmac: Remove a bunch of false positive error logs
Date: Tue, 07 Mar 2017 16:27:43 +0200 [thread overview]
Message-ID: <87mvcx88m8.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20170227100140.5190-1-hdegoede@redhat.com> (Hans de Goede's message of "Mon, 27 Feb 2017 11:01:36 +0100")
Hans de Goede <hdegoede@redhat.com> writes:
> Here is a small series to stop brcmfmac from spamming dmesg with errors
> which are not really errors at all.
>
> Note the 4th patch actually contains a small behavior change rather then
> just changing logging, so it needs a bit of extra review attention.
Arend, did you miss these? I don't see an ack from you.
--
Kalle Valo
prev parent reply other threads:[~2017-03-07 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 10:01 [PATCH 0/4] brcmfmac: Remove a bunch of false positive error logs Hans de Goede
2017-02-27 10:01 ` [PATCH 1/4] brcmfmac: Do not print the firmware version as an error Hans de Goede
2017-02-27 10:01 ` [PATCH 2/4] brcmfmac: p2p and normal ap access are not always possible at the same time Hans de Goede
2017-02-27 10:01 ` [PATCH 3/4] brcmfmac: Do not complain about country code "00" Hans de Goede
2017-02-27 10:01 ` [PATCH 4/4] brcmfmac: Handle status == BRCMF_E_STATUS_ABORT in cfg80211_escan_handler Hans de Goede
2017-03-07 14:27 ` Kalle Valo [this message]
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=87mvcx88m8.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=hdegoede@redhat.com \
--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