From: Viresh Kumar <viresh.kumar@linaro.org>
To: Matthew McClintock <mmcclint@codeaurora.org>
Cc: Mason <slash.tmp@free.fr>, Rafael Wysocki <rjw@rjwysocki.net>,
arnd.bergmann@linaro.org, linaro-kernel@lists.linaro.org,
linux-pm@vger.kernel.org, kgene.kim@samsung.com,
xf@rock-chips.com, heiko@sntech.de, k.kozlowski@samsung.com,
Sebastian Frias <sf84@laposte.net>
Subject: Re: [PATCH V3 0/4] cpufreq: dt: Create platform device from generic code
Date: Thu, 28 Apr 2016 07:57:14 +0530 [thread overview]
Message-ID: <20160428022714.GY4225@vireshk-i7> (raw)
In-Reply-To: <F0617D5F-67FB-4A02-9CDB-1DA9AD4CA27B@codeaurora.org>
On 27-04-16, 11:57, Matthew McClintock wrote:
> On Apr 27, 2016, at 11:47 AM, Mason <slash.tmp@free.fr> wrote:
> >
> > Should I add it at the beginning or at the end?
> > (I suppose at the end.)
>
> I was going to do alphabetical order.
That's right, you should follow the way things are present in the file itself.
So, it should be in alphabetical order, + blank lines separating your platform
from the rest.
--
viresh
prev parent reply other threads:[~2016-04-28 2:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 8:15 [PATCH V3 0/4] cpufreq: dt: Create platform device from generic code Viresh Kumar
2016-03-30 8:15 ` [PATCH V3 1/4] cpufreq: dt: Include types.h from cpufreq-dt.h Viresh Kumar
2016-03-30 8:15 ` [PATCH V3 2/4] cpufreq: dt: Add generic platform-device creation support Viresh Kumar
2016-04-13 19:46 ` Matthew McClintock
2016-03-30 8:15 ` [PATCH V3 3/4] ARM: exynos: exynos-cpufreq platform device isn't supported anymore Viresh Kumar
2016-03-30 8:30 ` Krzysztof Kozlowski
2016-03-30 8:15 ` [PATCH V3 4/4] cpufreq: exynos: Use generic platdev driver Viresh Kumar
2016-04-07 8:31 ` [PATCH V3 0/4] cpufreq: dt: Create platform device from generic code Viresh Kumar
2016-04-20 9:55 ` Viresh Kumar
2016-04-20 21:27 ` Mason
2016-04-20 22:31 ` Rafael J. Wysocki
2016-04-27 16:47 ` Mason
2016-04-27 16:57 ` Matthew McClintock
2016-04-28 2:27 ` Viresh Kumar [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=20160428022714.GY4225@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=arnd.bergmann@linaro.org \
--cc=heiko@sntech.de \
--cc=k.kozlowski@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=mmcclint@codeaurora.org \
--cc=rjw@rjwysocki.net \
--cc=sf84@laposte.net \
--cc=slash.tmp@free.fr \
--cc=xf@rock-chips.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