From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] clk: shmobile: clk-mstp: add backwards comapt for indices field
Date: Mon, 10 Mar 2014 11:10:56 +0000 [thread overview]
Message-ID: <531D9DC0.7020100@codethink.co.uk> (raw)
In-Reply-To: <20140310105116.GG14999@e106331-lin.cambridge.arm.com>
On 10/03/14 10:51, Mark Rutland wrote:
> On Fri, Mar 07, 2014 at 12:46:40PM +0000, Ben Dooks wrote:
>> Add comaptibiltiy for older device trees by checking to see if
>> the clock-indices property is there and falling back to the
>> older renesas,clock-indices field.
>
> Why are these two separate patches? This temporarily breaks
> compatibility.
Given I've not had time to change any of the device trees
for the renesas series it isn't currently an issue.
I left it separate to make it easier to remove once the changes
are through.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2014-03-10 11:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 12:46 Renesas clock clk-mstp updates for clock-indices Ben Dooks
2014-03-07 12:46 ` [PATCH 1/2] clk: shmobile: clk-mstp: change to using clock-indices Ben Dooks
2014-03-11 5:16 ` Simon Horman
2014-03-11 11:07 ` Ben Dooks
2014-03-11 22:39 ` Simon Horman
2014-03-07 12:46 ` [PATCH 2/2] clk: shmobile: clk-mstp: add backwards comapt for indices field Ben Dooks
2014-03-07 17:26 ` Laurent Pinchart
2014-03-10 10:51 ` Mark Rutland
2014-03-10 11:10 ` Ben Dooks [this message]
2014-04-15 9:10 ` Geert Uytterhoeven
2014-04-10 2:39 ` Renesas clock clk-mstp updates for clock-indices Kuninori Morimoto
2014-04-15 9:26 ` Geert Uytterhoeven
2014-04-15 11:43 ` Ben Dooks
2014-04-15 11:46 ` Geert Uytterhoeven
2014-04-15 11:52 ` Ben Dooks
2014-04-15 12:24 ` Geert Uytterhoeven
2014-04-15 23:59 ` Simon Horman
2014-04-15 23:58 ` Simon Horman
2014-04-16 7:12 ` Geert Uytterhoeven
2014-04-16 7:52 ` 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=531D9DC0.7020100@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--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).