From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/4] cpufreq: Add DVFS support for Armada 37xx
Date: Thu, 14 Dec 2017 15:06:27 +0530 [thread overview]
Message-ID: <20171214093627.GY3322@vireshk-i7> (raw)
In-Reply-To: <87fu8dps8h.fsf@free-electrons.com>
On 14-12-17, 10:35, Gregory CLEMENT wrote:
> Actually from the beginning the idea was to make difference between the
> define for the offset of the register and then the define for the value
> related to this register.
>
> Initially I used tab for this distinction, but then I though you
> suggested to only use space to have a more compact view, so I used double
> space.
>
> I don't mind using double space or tab, but for me making distinction
> between offset of the register and content of the register helps the
> readability of the code.
Sure, this looks fine to me.
--
viresh
next prev parent reply other threads:[~2017-12-14 9:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 17:51 [PATCH v3 0/4] Add CPU Frequency scaling support on Armada 37xx Gregory CLEMENT
2017-12-13 17:51 ` [PATCH v3 1/4] dt-bindings: marvell: Add documentation for the North Bridge PM " Gregory CLEMENT
2017-12-13 17:51 ` [PATCH v3 2/4] MAINTAINERS: add new entries for Armada 37xx cpufreq driver Gregory CLEMENT
2017-12-13 17:51 ` [PATCH v3 3/4] cpufreq: Add DVFS support for Armada 37xx Gregory CLEMENT
2017-12-14 3:04 ` Viresh Kumar
2017-12-14 9:35 ` Gregory CLEMENT
2017-12-14 9:36 ` Viresh Kumar [this message]
2017-12-13 17:51 ` [PATCH v3 4/4] arm64: dts: marvell: armada-37xx: add nodes allowing cpufreq support Gregory CLEMENT
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=20171214093627.GY3322@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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