From: bintian.wang@huawei•com (Bintian)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v8 4/7] clk: hisilicon: Remove __init for marking function prototypes
Date: Fri, 29 May 2015 10:07:19 +0800 [thread overview]
Message-ID: <5567C9D7.5000004@huawei.com> (raw)
In-Reply-To: <7hr3q0k5nq.fsf@deeprootsystems.com>
Hello Kevin,
On 2015/5/29 0:50, Kevin Hilman wrote:
> Bintian Wang <bintian.wang@huawei•com> writes:
>
>> __init markings on function prototypes are useless, so remove
>> them.
>>
>> Suggested-by: Stephen Boyd <sboyd@codeaurora•org>
>> Signed-off-by: Bintian Wang <bintian.wang@huawei•com>
>
> Can you repost the whole series please?
>
> The number of patches has increased and it's not terribly obvious how to
> combine your v7 or v8 patches with the v8 patches for proper testing.
I have sent the whole series, please help check.
Thanks,
Bintian
>
> Thanks,
>
> Kevin
>
> .
>
next prev parent reply other threads:[~2015-05-29 2:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 4:11 [PATCH v8 4/7] clk: hisilicon: Remove __init for marking function prototypes Bintian Wang
2015-05-24 4:11 ` [PATCH v8 5/7] dt-bindings: Add header file of hi6220 clock driver Bintian Wang
2015-05-24 4:11 ` [PATCH v8 6/7] clk: hi6220: Clock driver support for Hisilicon hi6220 SoC Bintian Wang
2015-05-28 5:26 ` Michael Turquette
2015-05-28 8:17 ` Bintian
2015-05-28 17:32 ` Kevin Hilman
2015-05-29 0:58 ` Bintian
2015-05-29 1:07 ` Michael Turquette
2015-05-29 2:34 ` Bintian
2015-05-28 16:50 ` [PATCH v8 4/7] clk: hisilicon: Remove __init for marking function prototypes Kevin Hilman
2015-05-29 2:07 ` Bintian [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-29 2:08 [PATCH v8 0/7] arm64,hi6220: Enable Hisilicon Hi6220 SoC Bintian Wang
2015-05-29 2:08 ` [PATCH v8 4/7] clk: hisilicon: Remove __init for marking function prototypes Bintian Wang
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=5567C9D7.5000004@huawei.com \
--to=bintian.wang@huawei$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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