From: Hans de Goede <hdegoede@redhat.com>
To: Kalle Valo <kvalo@codeaurora.org>,
Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Takashi Iwai <tiwai@suse.de>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com
Subject: Re: [PATCH v2 1/4] brcmfmac: Do not print the firmware version as an error
Date: Wed, 8 Mar 2017 11:08:27 +0100 [thread overview]
Message-ID: <8cd33792-0a44-fbce-f485-218b8c126625@redhat.com> (raw)
In-Reply-To: <87a88w851p.fsf@kamboji.qca.qualcomm.com>
HI,
On 08-03-17 10:57, Kalle Valo wrote:
> Arend Van Spriel <arend.vanspriel@broadcom.com> writes:
>
>> On 8-3-2017 9:23, Hans de Goede wrote:
>>> Hi,
>>>
>>> On 07-03-17 10:59, Arend Van Spriel wrote:
>>>> On 27-2-2017 22:45, Hans de Goede wrote:
>>>>> Using pr_err for things which are not errors is a bad idea. E.g. it
>>>>> will cause the plymouth bootsplash screen to drop back to the text
>>>>> console so that the user can see the error, which is not what we
>>>>> normally want to happen.
>>>>>
>>>>> Instead add a new brcmf_info macro and use that.
>>>>>
>>>>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>>>>> ---
>>>>> Changes in v2:
>>>>> -Fix brcm_err typo (should be brcmf_err) in CONFIG_BRCM_TRACING case
>>>>> ---
>>>>> drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c | 2 +-
>>>>> drivers/net/wireless/broadcom/brcm80211/brcmfmac/debug.h | 3 +++
>>>>> 2 files changed, 4 insertions(+), 1 deletion(-)
>>>>>
>>>>> diff --git
>>>>> a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c
>>>>> b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c
>>>>> index 3e15d64..6d565f1 100644
>>>>> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c
>>>>> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c
>>>>> @@ -161,7 +161,7 @@ int brcmf_c_preinit_dcmds(struct brcmf_if *ifp)
>>>>> strsep(&ptr, "\n");
>>>>>
>>>>> /* Print fw version info */
>>>>> - brcmf_err("Firmware version = %s\n", buf);
>>>>> + brcmf_info("Firmware version = %s\n", buf);
>>>>>
>>>>> /* locate firmware version number for ethtool */
>>>>> ptr = strrchr(buf, ' ') + 1;
>>>>> diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/debug.h
>>>>> b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/debug.h
>>>>> index 6687812..605f260 100644
>>>>> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/debug.h
>>>>> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/debug.h
>>>>> @@ -59,11 +59,14 @@
>>>>> pr_err("%s: " fmt, __func__, ##__VA_ARGS__); \
>>>>> } while (0)
>>>>> #endif
>>>>> +#define brcmf_info(fmt, ...) pr_info("%s: " fmt, __func__,
>>>>> ##__VA_ARGS__)
>>>>
>>>> Prefer using the same style as for brcmf_err, ie. using do {} while (0)
>>>
>>> OK, v3 with this fixed coming up.
>>
>> I think Kalle prefers the whole series to be resubmitted.
>>
>> Kalle,
>>
>> Can you confirm (or deny)?
>
> Exactly, I want to apply the full series (with the highest version
> number). Not waste time guessing what patches I should take and what to
> drop, with the increased risk of guessing wrong.
Ok, so patch 2/4 is still under discussion (and may be so for a while)
shall I send a new version with that patch dropped ? And then send
that patch (or a modified version) separately later ?
Regards,
Hans
>
next prev parent reply other threads:[~2017-03-08 10:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 21:45 [PATCH v2 1/4] brcmfmac: Do not print the firmware version as an error Hans de Goede
2017-02-27 21:45 ` [PATCH v2 2/4] brcmfmac: p2p and normal ap access are not always possible at the same time Hans de Goede
2017-03-07 10:03 ` Arend Van Spriel
2017-03-08 8:24 ` Hans de Goede
2017-03-08 9:26 ` Arend Van Spriel
2017-03-08 10:15 ` Arend Van Spriel
2017-03-08 11:16 ` Hans de Goede
2017-03-10 8:08 ` Hans de Goede
2017-03-10 9:35 ` Arend Van Spriel
2017-03-16 11:51 ` Hans de Goede
2017-02-27 21:45 ` [PATCH v2 3/4] brcmfmac: Do not complain about country code "00" Hans de Goede
2017-03-07 10:04 ` Arend Van Spriel
2017-02-27 21:45 ` [PATCH v2 4/4] brcmfmac: Handle status == BRCMF_E_STATUS_ABORT in cfg80211_escan_handler Hans de Goede
2017-03-07 10:06 ` Arend Van Spriel
2017-03-07 9:59 ` [PATCH v2 1/4] brcmfmac: Do not print the firmware version as an error Arend Van Spriel
2017-03-08 8:23 ` Hans de Goede
2017-03-08 9:28 ` Arend Van Spriel
2017-03-08 9:57 ` Kalle Valo
2017-03-08 10:08 ` Hans de Goede [this message]
2017-03-08 10:13 ` Arend Van Spriel
2017-03-08 10:14 ` Kalle Valo
2017-03-07 14:30 ` 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=8cd33792-0a44-fbce-f485-218b8c126625@redhat.com \
--to=hdegoede@redhat.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tiwai@suse.de \
/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