From: Kalle Valo <kvalo@kernel.org>
To: aspriel@gmail.com
Cc: arend.vanspriel@broadcom.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 7/7] brcmfmac: introduce BRCMFMAC exported symbols namespace
Date: Thu, 28 Jul 2022 12:39:51 +0300 [thread overview]
Message-ID: <87fsilo9so.fsf@kernel.org> (raw)
In-Reply-To: <CAJ65rDwMzF8hhuykrikSdsPMgy4GhLkTUfqTfn-cbHwCL5OE2Q@mail.gmail.com> (aspriel's message of "Mon, 13 Jun 2022 05:19:29 -0400")
aspriel@gmail.com writes:
> Instead of using EXPORT_SYMBOL() use namespace variant and only if
> build vendor-specific code as separate module.
The commit log should always answer to the question "why?".
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-07-28 9:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220613091915.18884-1-arend.vanspriel@broadcom.com>
2022-06-13 9:19 ` [PATCH 1/7] brcmfmac: add function to unbind device to bus layer api aspriel
2022-06-13 9:19 ` [PATCH 2/7] brcmfmac: add firmware vendor info in driver data aspriel
2022-07-28 9:31 ` Kalle Valo
2022-06-13 9:19 ` [PATCH 3/7] brcmfmac: add support for vendor-specific firmware api aspriel
2022-07-28 9:36 ` Kalle Valo
2022-07-29 9:32 ` Arend Van Spriel
2022-10-19 11:58 ` Arend Van Spriel
2022-10-24 10:49 ` Kalle Valo
2022-06-13 9:19 ` [PATCH 4/7] brcmfmac: add support for Cypress " aspriel
2022-07-28 9:38 ` Kalle Valo
2022-06-13 9:19 ` [PATCH 5/7] brcmfmac: add support Broadcom BCA " aspriel
2022-07-28 9:38 ` Kalle Valo
2022-06-13 9:19 ` [PATCH 6/7] brcmfmac: add vendor name in revinfo debugfs file aspriel
2022-06-13 9:19 ` [PATCH 7/7] brcmfmac: introduce BRCMFMAC exported symbols namespace aspriel
2022-07-28 9:39 ` Kalle Valo [this message]
2022-07-29 9:38 ` Arend Van Spriel
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=87fsilo9so.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=arend.vanspriel@broadcom.com \
--cc=aspriel@gmail.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).