linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: matthias.bgg@kernel.org
Cc: "Jakub Kicinski" <kuba@kernel.org>,
	"David S . Miller" <davem@davemloft.net>,
	hdegoede@redhat.com, "Pali Rohár" <pali@kernel.org>,
	"Guenter Roeck" <linux@roeck-us.net>,
	"Chi-Hsien Lin" <chi-hsien.lin@cypress.com>,
	"Franky Lin" <franky.lin@broadcom.com>,
	"Chung-Hsien Hsu" <stanley.hsu@cypress.com>,
	"Jean-Philippe Brucker" <jean-philippe@linaro.org>,
	"Double Lo" <double.lo@cypress.com>,
	"Frank Kao" <frank.kao@cypress.com>,
	linux-wireless@vger.kernel.org,
	brcm80211-dev-list.pdl@broadcom.com,
	"Arend van Spriel" <arend.vanspriel@broadcom.com>,
	"Gustavo A . R . Silva" <gustavo@embeddedor.com>,
	netdev@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>,
	"Hante Meuleman" <hante.meuleman@broadcom.com>,
	"Wright Feng" <wright.feng@cypress.com>,
	"Matthias Brugger" <mbrugger@suse.com>,
	"Saravanan Shanmugham" <saravanan.shanmugham@cypress.com>,
	brcm80211-dev-list@cypress.com, linux-kernel@vger.kernel.org,
	"Ulf Hansson" <ulf.hansson@linaro.org>,
	"Soeren Moch" <smoch@web.de>
Subject: Re: [PATCH] brcmfmac: expose firmware config files through modinfo
Date: Tue, 14 Jul 2020 09:37:11 +0000 (UTC)	[thread overview]
Message-ID: <20200714093712.0B0C3C433B2@smtp.codeaurora.org> (raw)
In-Reply-To: <20200701153123.25602-1-matthias.bgg@kernel.org>

matthias.bgg@kernel.org wrote:

> From: Matthias Brugger <mbrugger@suse.com>
> 
> Apart from a firmware binary the chip needs a config file used by the
> FW. Add the config files to modinfo so that they can be read by
> userspace.
> 
> Signed-off-by: Matthias Brugger <mbrugger@suse.com>

I agree with Hans, this does not look a good solution for the problem.

Patch set to Changes Requested.

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

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


      parent reply	other threads:[~2020-07-14  9:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-01 15:31 [PATCH] brcmfmac: expose firmware config files through modinfo matthias.bgg
2020-07-01 15:38 ` Hans de Goede
2020-07-01 15:46   ` Matthias Brugger
2020-07-02 18:00     ` Hans de Goede
2020-07-03 14:01       ` Matthias Brugger
2020-07-03 14:10         ` Hans de Goede
2020-07-14  9:37 ` 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=20200714093712.0B0C3C433B2@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=double.lo@cypress.com \
    --cc=frank.kao@cypress.com \
    --cc=franky.lin@broadcom.com \
    --cc=gustavo@embeddedor.com \
    --cc=hante.meuleman@broadcom.com \
    --cc=hdegoede@redhat.com \
    --cc=jean-philippe@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=matthias.bgg@kernel.org \
    --cc=mbrugger@suse.com \
    --cc=netdev@vger.kernel.org \
    --cc=pali@kernel.org \
    --cc=rafal@milecki.pl \
    --cc=saravanan.shanmugham@cypress.com \
    --cc=smoch@web.de \
    --cc=stanley.hsu@cypress.com \
    --cc=ulf.hansson@linaro.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).