From: Kalle Valo <kvalo@codeaurora.org>
To: matthias.bgg@kernel.org
Cc: arend.vanspriel@broadcom.com, davem@davemloft.net,
kuba@kernel.org, brcm80211-dev-list.pdl@broadcom.com,
mbrugger@suse.com, netdev@vger.kernel.org,
chi-hsien.lin@cypress.com, linux-wireless@vger.kernel.org,
hante.meuleman@broadcom.com, linux-kernel@vger.kernel.org,
hdegoede@redhat.com, wright.feng@cypress.com,
matthias.bgg@kernel.org, brcm80211-dev-list@cypress.com,
franky.lin@broadcom.com
Subject: Re: [PATCH v3] brcmfmac: Transform compatible string for FW loading
Date: Tue, 14 Jul 2020 09:50:58 +0000 (UTC) [thread overview]
Message-ID: <20200714095058.A7004C433AD@smtp.codeaurora.org> (raw)
In-Reply-To: <20200701112201.6449-1-matthias.bgg@kernel.org>
matthias.bgg@kernel.org wrote:
> From: Matthias Brugger <mbrugger@suse.com>
>
> The driver relies on the compatible string from DT to determine which
> FW configuration file it should load. The DTS spec allows for '/' as
> part of the compatible string. We change this to '-' so that we will
> still be able to load the config file, even when the compatible has a
> '/'. This fixes explicitly the firmware loading for
> "solidrun,cubox-i/q".
>
> Signed-off-by: Matthias Brugger <mbrugger@suse.com>
> Reviewed-by: Hans deGoede <hdegoede@redhat.com>
Patch applied to wireless-drivers-next.git, thanks.
29e354ebeeec brcmfmac: Transform compatible string for FW loading
--
https://patchwork.kernel.org/patch/11636153/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2020-07-14 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 11:22 [PATCH v3] brcmfmac: Transform compatible string for FW loading matthias.bgg
2020-07-01 12:12 ` Hans de Goede
2020-07-14 9:50 ` 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=20200714095058.A7004C433AD@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=davem@davemloft.net \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=hdegoede@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=matthias.bgg@kernel.org \
--cc=mbrugger@suse.com \
--cc=netdev@vger.kernel.org \
--cc=wright.feng@cypress.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.