From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: <linux-wireless@vger.kernel.org>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<ath10k@lists.infradead.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [1/3] ath10k: use devm_clk_get() instead of clk_get()
Date: Tue, 27 Sep 2016 14:14:33 +0200 [thread overview]
Message-ID: <e4a0ff1bec4b4e88b61c88988a7683d6@euamsexm01a.eu.qualcomm.com> (raw)
In-Reply-To: <1473165598-28683-2-git-send-email-yamada.masahiro@socionext.com>
Masahiro Yamada <yamada.masahiro@socionext.com> wrote:
> Use the managed variant of clk_get() to simplify the failure path
> and the .remove callback.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
3 patches applied to ath-next branch of ath.git, thanks.
828662753d60 ath10k: use devm_clk_get() instead of clk_get()
c5d8a34675d9 ath10k: use devm_reset_control_get() instead of reset_control_get()
65901a9e7058 ath10k: do not check if reset is NULL
--
https://patchwork.kernel.org/patch/9316579/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2016-09-27 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 12:39 [PATCH 0/3] ath10k: a little bit clean-up of ATH10K driver Masahiro Yamada
2016-09-06 12:39 ` [PATCH 1/3] ath10k: use devm_clk_get() instead of clk_get() Masahiro Yamada
2016-09-27 12:14 ` Kalle Valo [this message]
2016-09-06 12:39 ` [PATCH 2/3] ath10k: use devm_reset_control_get() instead of reset_control_get() Masahiro Yamada
2016-09-06 12:39 ` [PATCH 3/3] ath10k: do not check if reset is NULL Masahiro Yamada
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=e4a0ff1bec4b4e88b61c88988a7683d6@euamsexm01a.eu.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=netdev@vger.kernel.org \
--cc=yamada.masahiro@socionext.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).