From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: mturquette@linaro.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, gregkh@linuxfoundation.org,
linux@arm.linux.org.uk, robh+dt@kernel.org,
grant.likely@linaro.org, mark.rutland@arm.com,
galak@codeaurora.org, kyungmin.park@samsung.com,
sw0312.kim@samsung.com, m.szyprowski@samsung.com,
t.figa@samsung.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC v3 1/2] clk: Add function parsing arbitrary clock list DT property
Date: Thu, 27 Mar 2014 19:02:47 +0100 [thread overview]
Message-ID: <533467C7.7020804@samsung.com> (raw)
In-Reply-To: <3164460.aT5tTxdc17@amdc1032>
Hi Bart,
On 27/03/14 18:17, Bartlomiej Zolnierkiewicz wrote:
>> +struct clk *of_clk_get_by_property(struct device_node *np,
>
> This causes build brake with s3c6400_defconfig
> (it should be 'static inline').
Thanks for reporting it, I assume you meant "build break"? ;)
Will fix that and similar issue in patch 2/2 for next iteration.
--
Regards,
Sylwester
next prev parent reply other threads:[~2014-03-27 18:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 12:16 [PATCH RFC v3 0/2] clk: Support for DT assigned clock parents and rates Sylwester Nawrocki
2014-03-27 12:16 ` [PATCH RFC v3 1/2] clk: Add function parsing arbitrary clock list DT property Sylwester Nawrocki
2014-03-27 17:17 ` Bartlomiej Zolnierkiewicz
2014-03-27 18:02 ` Sylwester Nawrocki [this message]
2014-03-27 12:16 ` [PATCH RFC v3 2/2] clk: Add handling of clk parent and rate assigned from DT Sylwester Nawrocki
2014-03-27 13:24 ` Laurent Pinchart
2014-03-27 13:57 ` Sylwester Nawrocki
2014-03-27 14:08 ` Laurent Pinchart
2014-03-27 14:47 ` Sascha Hauer
2014-03-28 16:44 ` Laurent Pinchart
2014-03-31 8:32 ` Sascha Hauer
2014-04-01 13:36 ` Laurent Pinchart
2014-03-27 15:02 ` Sylwester Nawrocki
2014-03-28 16:49 ` Laurent Pinchart
2014-03-31 11:40 ` Sylwester Nawrocki
2014-03-27 17:19 ` Bartlomiej Zolnierkiewicz
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=533467C7.7020804@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=mark.rutland@arm.com \
--cc=mturquette@linaro.org \
--cc=robh+dt@kernel.org \
--cc=sw0312.kim@samsung.com \
--cc=t.figa@samsung.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