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>,
Hans de Goede <hdegoede@redhat.com>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com
Subject: Re: [resend] brcmfmac: p2p and normal ap access are not always possible at the same time
Date: Tue, 13 Jun 2017 05:58:59 +0000 (UTC) [thread overview]
Message-ID: <20170613055859.3BEBF607DC@smtp.codeaurora.org> (raw)
In-Reply-To: <20170526105747.16874-2-hdegoede@redhat.com>
Hans de Goede <hdegoede@redhat.com> wrote:
> The firmware responding with -EBUSY when trying to add an extra virtual-if
> is a normal thing, do not print an error for this.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Arend, what should I do with this patch? Take it?
--
https://patchwork.kernel.org/patch/9750341/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2017-06-13 5:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 10:57 [PATCH resend 0/1] brcmfmac: p2p and normal ap access are not always possible at the same time Hans de Goede
2017-05-26 10:57 ` [PATCH resend] " Hans de Goede
2017-06-13 5:58 ` Kalle Valo [this message]
2017-08-04 12:35 ` Arend van Spriel
2017-08-30 10:24 ` Hans de Goede
2017-08-30 10:30 ` Hans de Goede
2017-10-19 11:20 ` Hans de Goede
2018-02-25 14:52 ` Hans de Goede
2018-02-26 10:22 ` Arend van Spriel
2018-02-26 10:29 ` Hans de Goede
2018-02-26 11:01 ` Arend van Spriel
2018-02-26 11:22 ` Hans de Goede
2018-02-26 11:36 ` Arend van Spriel
2018-02-26 23:04 ` Arend van Spriel
2018-02-28 14:52 ` Hans de Goede
2018-02-28 19:43 ` Arend van Spriel
2018-03-01 8:35 ` Hans de Goede
2018-03-01 19:54 ` Arend van Spriel
2018-03-01 22:37 ` Hans de Goede
2018-03-02 9:53 ` Arend van Spriel
2017-05-26 11:08 ` [PATCH resend 0/1] " 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=20170613055859.3BEBF607DC@smtp.codeaurora.org \
--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;
as well as URLs for NNTP newsgroup(s).