From: Olof Johansson <olof@lixom.net>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Renesas ARM Based SoC CPG MSTP Clock Domain Updates for v4.3
Date: Tue, 11 Aug 2015 13:42:49 +0000 [thread overview]
Message-ID: <20150811134249.GQ30181@localhost> (raw)
In-Reply-To: <cover.1438911559.git.horms+renesas@verge.net.au>
On Fri, Aug 07, 2015 at 11:12:03AM +0900, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these Renesas ARM based SoC CPG MSTP clock domain updates
> for v4.3.
>
> This pull request is based on "Third Round of Renesas ARM Based SoC DT
> Updates for v4.3", tagged as renesas-dt3-for-v4.3, which I have also sent a
> pull-request for.
>
> The reason for that base is that the DT changes in this series update nodes
> added in that tag.
>
> This series begins with driver changes and follows up with DT changes.
> The latter depend on the former.
>
>
> The following changes since commit 94bdc48d55ca10f90b4a625f0e443197e0013557:
>
> ARM: shmobile: sh73a0 dtsi: Add missing "gpio-ranges" to gpio node (2015-08-05 06:39:28 +0900)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-cpg-mstp-clock-domain-for-v4.3
>
> for you to fetch changes up to 2daa8a5a8c0994893c2ca456303f0bf53e881cb9:
>
> ARM: shmobile: r8a7794 dtsi: Add CPG/MSTP Clock Domain (2015-08-05 06:42:51 +0900)
We normally prefer to see drivers separately from DT. If you've looked at how
we organize arm-soc, you've maybe seen that we have a separate topic for
next/driver and one for next/dt. In other words, we try to keep them apart
where it makes sense.
In this case, that would mean having the clk changes in a drivers branch, and
include that in this dt4 branch.
If you want a reminder for when you might have looked at the branch sorting
wrong: If you're naming the branch after a feature instead of the type of
patches in it (when you send it to us), then chances are that we would ideally
like to see the contents sorted differently -- at least in the cases where they
cross the category boundaries that we organize our tree in.
So, while it's not a huge deal I think it makes sense to revisit this
and do that sorting for consistency's sake. Can I please ask that you
respin this pull request with that in mind? I'd cherry-pick them apart
but I know you tend to base branches on each other so that might mess
you up and I don't want to do that.
Thanks,
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM Based SoC CPG MSTP Clock Domain Updates for v4.3
Date: Tue, 11 Aug 2015 15:42:49 +0200 [thread overview]
Message-ID: <20150811134249.GQ30181@localhost> (raw)
In-Reply-To: <cover.1438911559.git.horms+renesas@verge.net.au>
On Fri, Aug 07, 2015 at 11:12:03AM +0900, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these Renesas ARM based SoC CPG MSTP clock domain updates
> for v4.3.
>
> This pull request is based on "Third Round of Renesas ARM Based SoC DT
> Updates for v4.3", tagged as renesas-dt3-for-v4.3, which I have also sent a
> pull-request for.
>
> The reason for that base is that the DT changes in this series update nodes
> added in that tag.
>
> This series begins with driver changes and follows up with DT changes.
> The latter depend on the former.
>
>
> The following changes since commit 94bdc48d55ca10f90b4a625f0e443197e0013557:
>
> ARM: shmobile: sh73a0 dtsi: Add missing "gpio-ranges" to gpio node (2015-08-05 06:39:28 +0900)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-cpg-mstp-clock-domain-for-v4.3
>
> for you to fetch changes up to 2daa8a5a8c0994893c2ca456303f0bf53e881cb9:
>
> ARM: shmobile: r8a7794 dtsi: Add CPG/MSTP Clock Domain (2015-08-05 06:42:51 +0900)
We normally prefer to see drivers separately from DT. If you've looked at how
we organize arm-soc, you've maybe seen that we have a separate topic for
next/driver and one for next/dt. In other words, we try to keep them apart
where it makes sense.
In this case, that would mean having the clk changes in a drivers branch, and
include that in this dt4 branch.
If you want a reminder for when you might have looked at the branch sorting
wrong: If you're naming the branch after a feature instead of the type of
patches in it (when you send it to us), then chances are that we would ideally
like to see the contents sorted differently -- at least in the cases where they
cross the category boundaries that we organize our tree in.
So, while it's not a huge deal I think it makes sense to revisit this
and do that sorting for consistency's sake. Can I please ask that you
respin this pull request with that in mind? I'd cherry-pick them apart
but I know you tend to base branches on each other so that might mess
you up and I don't want to do that.
Thanks,
-Olof
next prev parent reply other threads:[~2015-08-11 13:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 2:12 [GIT PULL] Renesas ARM Based SoC CPG MSTP Clock Domain Updates for v4.3 Simon Horman
2015-08-07 2:12 ` Simon Horman
2015-08-07 2:12 ` [PATCH 01/12] clk: shmobile: Add CPG/MSTP Clock Domain support Simon Horman
2015-08-07 2:12 ` Simon Horman
2015-08-07 2:12 ` [PATCH 02/12] clk: shmobile: r8a7778: " Simon Horman
2015-08-07 2:12 ` Simon Horman
2015-08-07 2:12 ` [PATCH 03/12] clk: shmobile: r8a7779: " Simon Horman
2015-08-07 2:12 ` Simon Horman
2015-08-07 2:12 ` [PATCH 04/12] clk: shmobile: rcar-gen2: " Simon Horman
2015-08-07 2:12 ` Simon Horman
2015-08-07 2:12 ` [PATCH 05/12] clk: shmobile: rz: " Simon Horman
2015-08-07 2:12 ` Simon Horman
2015-08-07 2:12 ` [PATCH 06/12] ARM: shmobile: r7s72100 dtsi: Add CPG/MSTP Clock Domain Simon Horman
2015-08-07 2:12 ` Simon Horman
2015-08-07 2:12 ` [PATCH 07/12] ARM: shmobile: r8a7778 " Simon Horman
2015-08-07 2:12 ` Simon Horman
2015-08-07 2:12 ` [PATCH 08/12] ARM: shmobile: r8a7779 " Simon Horman
2015-08-07 2:12 ` Simon Horman
2015-08-07 2:12 ` [PATCH 09/12] ARM: shmobile: r8a7790 " Simon Horman
2015-08-07 2:12 ` Simon Horman
2015-08-07 2:12 ` [PATCH 10/12] ARM: shmobile: r8a7791 " Simon Horman
2015-08-07 2:12 ` Simon Horman
2015-08-07 2:12 ` [PATCH 11/12] ARM: shmobile: r8a7793 " Simon Horman
2015-08-07 2:12 ` Simon Horman
2015-08-07 2:12 ` [PATCH 12/12] ARM: shmobile: r8a7794 " Simon Horman
2015-08-07 2:12 ` Simon Horman
2015-08-11 13:38 ` [GIT PULL] Renesas ARM Based SoC CPG MSTP Clock Domain Updates for v4.3 Olof Johansson
2015-08-11 13:38 ` Olof Johansson
2015-08-12 8:48 ` Simon Horman
2015-08-12 8:48 ` Simon Horman
2015-08-13 9:30 ` Olof Johansson
2015-08-13 9:30 ` Olof Johansson
2015-08-11 13:42 ` Olof Johansson [this message]
2015-08-11 13:42 ` Olof Johansson
2015-08-12 8:46 ` Simon Horman
2015-08-12 8:46 ` Simon Horman
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=20150811134249.GQ30181@localhost \
--to=olof@lixom.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.