From: Kalle Valo <kvalo@codeaurora.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: wcn36xx@lists.infradead.org, linux-wireless@vger.kernel.org,
bryan.odonoghue@linaro.org, shawn.guo@linaro.org,
loic.poulain@linaro.org
Subject: Re: [PATCH v5 1/2] wcn36xx: Mark internal smd functions static
Date: Tue, 22 Sep 2020 07:40:24 +0000 (UTC) [thread overview]
Message-ID: <20200922074024.2650DC433CB@smtp.codeaurora.org> (raw)
In-Reply-To: <20200910150845.2179320-2-bryan.odonoghue@linaro.org>
Bryan O'Donoghue <bryan.odonoghue@linaro.org> wrote:
> This commit marks all smd.c functions that are only used inside of smd.c as
> static. Previous commits added some VHT specific setup functions non-static
> which is the right thing to do in terms of having granular git commits that
> compile warning free. What we really want is for local not global scope on
> those functions.
>
> This patch makes the conversion from global to local scope.
>
> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
2 patches applied to ath-next branch of ath.git, thanks.
7f885b0bdf6f wcn36xx: Mark internal smd functions static
214091517f0c wcn36xx: Ensure spaces between functions
--
https://patchwork.kernel.org/patch/11768913/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-09-22 7:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 15:08 [PATCH v5 0/2] wcn36xx: Miscellaneous updates Bryan O'Donoghue
2020-09-10 15:08 ` [PATCH v5 1/2] wcn36xx: Mark internal smd functions static Bryan O'Donoghue
2020-09-22 7:40 ` Kalle Valo [this message]
2020-09-10 15:08 ` [PATCH v5 2/2] wcn36xx: Ensure spaces between functions Bryan O'Donoghue
2020-09-10 15:55 ` [PATCH v5 0/2] wcn36xx: Miscellaneous updates Bryan O'Donoghue
2020-09-10 16:07 ` Bryan O'Donoghue
2020-09-10 16:22 ` Kalle Valo
[not found] ` <0101017478d3b3af-e0300995-fa17-44ef-b4c2-286469dfeb87-000000@us-west-2.amazonses.com>
2020-09-10 16:28 ` Bryan O'Donoghue
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=20200922074024.2650DC433CB@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=bryan.odonoghue@linaro.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=shawn.guo@linaro.org \
--cc=wcn36xx@lists.infradead.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 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.