linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
	Wright Feng <wright.feng@cypress.com>,
	Hans de Goede <hdegoede@redhat.com>,
	linux-wireless@vger.kernel.org,
	brcm80211-dev-list.pdl@broadcom.com
Subject: Re: [PATCH] brcmfmac: Add DMI nvram filename quirk for PoV TAB-P1006W-232 tablet
Date: Thu, 10 Jan 2019 11:33:36 +0000 (UTC)	[thread overview]
Message-ID: <20190110113336.F385B608A5@smtp.codeaurora.org> (raw)
In-Reply-To: <20181220164058.19203-1-hdegoede@redhat.com>

Hans de Goede <hdegoede@redhat.com> wrote:

> The Point of View TAB-P1006W-232 tablet contains quite generic names in
> the sys_vendor and product_name DMI strings, without this patch brcmfmac
> will try to load: brcmfmac43340-sdio.Insyde-BayTrail.txt as nvram file
> which is a bit too generic.
> 
> Add a DMI quirk so that a unique and clearly identifiable nvram file
> name is used on the PoV TAB-P1006W-232 tablet.
> 
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>

Patch applied to wireless-drivers-next.git, thanks.

4d95f99c59b8 brcmfmac: Add DMI nvram filename quirk for PoV TAB-P1006W-232 tablet

-- 
https://patchwork.kernel.org/patch/10739171/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


      reply	other threads:[~2019-01-10 11:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20 16:40 [PATCH] brcmfmac: Add DMI nvram filename quirk for PoV TAB-P1006W-232 tablet Hans de Goede
2019-01-10 11:33 ` 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=20190110113336.F385B608A5@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=arend.vanspriel@broadcom.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=chi-hsien.lin@cypress.com \
    --cc=franky.lin@broadcom.com \
    --cc=hante.meuleman@broadcom.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-wireless@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 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).