From: Fabio Estevam <festevam-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Alexander Shiyan <shc_work-JGs/UdohzUI@public.gmane.org>
Cc: "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Shawn Guo <shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
Sascha Hauer <kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2 3/3] ARM: i.MX1 clk: Add devicetree support
Date: Tue, 13 May 2014 13:28:28 -0300 [thread overview]
Message-ID: <CAOMZO5CNk4uAu0OujRgiJpU2gHJpAnD4zpqxSHd4hXo3fnJ4_w@mail.gmail.com> (raw)
In-Reply-To: <1399998253.839894262-epzXK9EC9shsdVUOrk1QfQ@public.gmane.org>
On Tue, May 13, 2014 at 1:24 PM, Alexander Shiyan <shc_work-JGs/UdohzUI@public.gmane.org> wrote:
> Tue, 13 May 2014 13:18:40 -0300 от Fabio Estevam <festevam@gmail.com>:
>> On Tue, May 13, 2014 at 1:05 PM, Alexander Shiyan <shc_work-JGs/UdohzUI@public.gmane.org> wrote:
>>
>> > + clk[IMX1_CLK_DUMMY] =
>> > + imx_clk_fixed("dummy", 0);
>> > + clk[IMX1_CLK_CLK32] =
>> > + imx_obtain_fixed_clock("clk32", fref);
>> > + clk[IMX1_CLK_CLK16M_EXT] =
>> > + imx_clk_fixed("clk16m_ext", 16000000);
>> > + clk[IMX1_CLK_CLK16M] =
>> > + imx_clk_gate("clk16m", "clk16m_ext", CCM_CSCR, 17);
>>
>> Why don't you put each entry into a single line instead?
>>
>> Even if it gets larger than 80 columns, it would be easier to read.
>
> I thought about it, but came to the conclusion that it is better to observe
> the kernel rules.
Do you mean checkpatch complaint?
Then try to make checkpatch happy with other clock file such as
arch/arm/mach-imx/clk-imx6q.
The result will be unreadable :-)
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-05-13 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 16:05 [PATCH v2 3/3] ARM: i.MX1 clk: Add devicetree support Alexander Shiyan
[not found] ` <1399997116-4313-1-git-send-email-shc_work-JGs/UdohzUI@public.gmane.org>
2014-05-13 16:18 ` Fabio Estevam
[not found] ` <CAOMZO5Br9wpZu06oP3-Ax5XG=u+A6Ydq9peKet64Kw_moGgRaw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-13 16:24 ` Alexander Shiyan
[not found] ` <1399998253.839894262-epzXK9EC9shsdVUOrk1QfQ@public.gmane.org>
2014-05-13 16:28 ` Fabio Estevam [this message]
[not found] ` <CAOMZO5CNk4uAu0OujRgiJpU2gHJpAnD4zpqxSHd4hXo3fnJ4_w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-13 16:44 ` Alexander Shiyan
[not found] ` <1399999493.354004023-epzXK9EC9shsdVUOrk1QfQ@public.gmane.org>
2014-05-13 17:31 ` Sascha Hauer
[not found] ` <20140513173143.GU5858-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-05-14 16:53 ` Alexander Shiyan
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=CAOMZO5CNk4uAu0OujRgiJpU2gHJpAnD4zpqxSHd4hXo3fnJ4_w@mail.gmail.com \
--to=festevam-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=shc_work-JGs/UdohzUI@public.gmane.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).