From: Stephen Boyd <sboyd@codeaurora.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: change the type of clk_hw_onecell_data.num to unsigned int
Date: Fri, 23 Sep 2016 14:44:20 -0700 [thread overview]
Message-ID: <20160923214420.GC21232@codeaurora.org> (raw)
In-Reply-To: <1474633776-11586-1-git-send-email-yamada.masahiro@socionext.com>
On 09/23, Masahiro Yamada wrote:
> The "num" is the number of clk_hw entries in the structure, so
> "unsigned int" would be a better fit. (size_t looks like data
> size we count by byte.)
>
> Besides, struct clk_onecell_data already uses unsigned int for
> "clk_num".
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
Seems fair.
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2016-09-23 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 12:29 [PATCH] clk: change the type of clk_hw_onecell_data.num to unsigned int Masahiro Yamada
2016-09-23 21:44 ` Stephen Boyd [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=20160923214420.GC21232@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--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