From: Wolfram Sang <wsa@the-dreams.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 4/5] ARM: shmobile: r8a7790: add IIC(B) clocks to dtsi
Date: Tue, 25 Mar 2014 16:48:12 +0000 [thread overview]
Message-ID: <20140325164812.GE6374@katana> (raw)
In-Reply-To: <CANqRtoQhi=vgLkYQciJska6XogyiJ1REO6HBOHNsPP3ajbq+Ag@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1715 bytes --]
On Wed, Mar 12, 2014 at 08:05:26PM +0900, Magnus Damm wrote:
> Hi Wolfram,
>
> On Wed, Mar 12, 2014 at 6:24 AM, Wolfram Sang <wsa@the-dreams.de> wrote:
> > From: Wolfram Sang <wsa@sang-engineering.com>
> >
> > Signed-off-by: Wolfram Sang <wsa@sang-engineering.com>
> > ---
> > Note: Adding clocks whilst keeping the current sorting is very likely to
> > break a previously working clock IMO. Imagine adding PCIEC clock inbetween IIC0
> > and IIC1 here. Adding chronologically and grouped by similar function blocks is
> > easier to track. An example addition could then look like:
> >
> > R8A7790_CLK_TPU0
> > R8A7790_CLK_SDHI3 R8A7790_CLK_SDHI2 R8A7790_CLK_SDHI1 R8A7790_CLK_SDHI0
> > R8A7790_CLK_MMCIF1 R8A7790_CLK_MMCIF0
> > R8A7790_CLK_CMT1
> > R8A7790_CLK_IIC2 R8A7790_CLK_IIC1 R8A7790_CLK_IIC0
> > + R8A7790_CLK_PCIEC
>
> Can you please care to explain a bit more about why you see a risk
> here? Is it a risk for typo or something else?
The risk here is if you put something in the "middle" then there is a
chance you might be off, and, for example, mix up parent clocks.
Especially when you need to reformat paragraphs because of too long
lines. Yeah, all this can be avoided by careful review, but this review
really needs to be careful.
> It looks to me that this is just a matter about adding the entry at
> the right position in several places.
Yes. IMO adding it with the pattern I sketched above will make it a
piece of cake since the diff is a lot more simple than the patch I
originally submitted.
That being said, I will keep the current sorting for consistency reasons
but I personally made up my mind ;)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-25 16:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 21:24 [PATCH 0/5] ARM: shmobile: r8a7790: enable IIC(B) cores Wolfram Sang
2014-03-11 21:24 ` [PATCH 1/5] pinctrl: pfc: r8a7790: add i2c0 muxing Wolfram Sang
2014-03-12 10:23 ` Laurent Pinchart
2014-03-11 21:24 ` [PATCH 2/5] pinctrl: pfc: r8a7790: add mux data for IIC(B) cores Wolfram Sang
2014-03-12 10:31 ` Laurent Pinchart
2014-03-11 21:24 ` [PATCH 3/5] ARM: shmobile: r8a7790: add IIC0-2 clock macros Wolfram Sang
2014-03-12 10:32 ` Laurent Pinchart
2014-03-11 21:24 ` [PATCH 4/5] ARM: shmobile: r8a7790: add IIC(B) clocks to dtsi Wolfram Sang
2014-03-12 10:37 ` Laurent Pinchart
2014-03-12 11:05 ` Magnus Damm
2014-03-25 16:48 ` Wolfram Sang [this message]
2014-03-11 21:24 ` [PATCH 5/5] ARM: shmobile: r8a7790: add IIC(B) cores " Wolfram Sang
2014-03-12 10:39 ` Laurent Pinchart
2014-03-12 10:40 ` [PATCH 0/5] ARM: shmobile: r8a7790: enable IIC(B) cores Laurent Pinchart
2014-03-25 16:31 ` Wolfram Sang
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=20140325164812.GE6374@katana \
--to=wsa@the-dreams.de \
--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;
as well as URLs for NNTP newsgroup(s).