From: Jens Kuske <jenskuske@gmail.com>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: "Maxime Ripard" <maxime.ripard@free-electrons.com>,
"Chen-Yu Tsai" <wens@csie.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Emilio López" <emilio@elopez.com.ar>,
"Vishnu Patekar" <vishnupatekar0510@gmail.com>,
"Hans de Goede" <hdegoede@redhat.com>,
devicetree <devicetree@vger.kernel.org>,
"Mailing List, Arm" <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-sunxi <linux-sunxi@googlegroups.com>
Subject: Re: [linux-sunxi] [PATCH 2/6] clk: sunxi: Add H3 clocks support
Date: Thu, 22 Oct 2015 09:32:53 +0200 [thread overview]
Message-ID: <56289125.2060408@gmail.com> (raw)
In-Reply-To: <CAGRGNgWyNEOMVxeDFTAp_wJoaXL471spFjBTn+2s7YuKeJf71g@mail.gmail.com>
On 22/10/15 02:15, Julian Calaby wrote:
>
> This hunk should be in patch 1:
Indeed, Thanks.
Jens
>
>> @@ -1000,9 +1005,8 @@ static void __init sunxi_divs_clk_setup(struct device_node *node,
>>
>> for (i = 0; i < SUNXI_DIVS_BASE_NAME_MAX_LEN - 1 &&
>> clk_name[i] != '_' &&
>> - clk_name[i] != '\0'; i++) {
>> + clk_name[i] != '\0'; i++)
>> base_name[i] = clk_name[i];
>> - }
>>
>> base_name[i] = '\0';
>> factors.name = base_name;
>
> Thanks,
>
next prev parent reply other threads:[~2015-10-22 7:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 16:13 [PATCH 0/6] ARM: sunxi: Introduce Allwinner H3 support Jens Kuske
2015-10-21 16:13 ` [PATCH 1/6] clk: sunxi: Let divs clocks read the base factor clock name from devicetree Jens Kuske
2015-10-21 16:13 ` [PATCH 2/6] clk: sunxi: Add H3 clocks support Jens Kuske
2015-10-22 0:15 ` [linux-sunxi] " Julian Calaby
2015-10-22 7:32 ` Jens Kuske [this message]
2015-10-21 19:18 ` [PATCH 0/6] ARM: sunxi: Introduce Allwinner H3 support Hans de Goede
2015-10-22 7:49 ` Jens Kuske
2015-10-22 8:49 ` [linux-sunxi] " Hans de Goede
2015-10-27 19:24 ` Peter Korsgaard
2015-10-22 7:58 ` Jean-Francois Moine
2015-10-22 9:08 ` Hans de Goede
2015-10-21 19:23 ` Hans de Goede
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=56289125.2060408@gmail.com \
--to=jenskuske@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=emilio@elopez.com.ar \
--cc=hdegoede@redhat.com \
--cc=julian.calaby@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime.ripard@free-electrons.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=vishnupatekar0510@gmail.com \
--cc=wens@csie.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).