All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 3/3] clk-mstp: add backwards comapt for indicies field
Date: Fri, 07 Mar 2014 10:10:11 +0000	[thread overview]
Message-ID: <58097128.FjP4hkbmQo@avalon> (raw)
In-Reply-To: <1392314571-30107-3-git-send-email-ben.dooks@codethink.co.uk>

Hi Ben,

On Thursday 06 March 2014 19:06:35 Ben Dooks wrote:
> On 13/02/14 23:15, Laurent Pinchart wrote:
> > Hi Ben,
> > 
> > Thank you for the patch.
> > 
> > On Thursday 13 February 2014 18:02:51 Ben Dooks wrote:
> >> Add comaptibiltiy for older device trees by checking to see if
> >> the clock-indicies property is there and falling back to the
> >> older renesas,clock-indices field.
> > 
> > I would drop this patch. The Renesas clocks DT bindings are too new
> > (v3.14-rc1, and for multiplatform kernels only) to be considered as stable
> > in my opinion.
> 
> I think this may be required as the current amount of development work being
> done means that either we need to be at a point where we can merge the
> driver change via Simon's tree, or to put the compatibility in and hope the
> driver update goes in first before we merge the dts/dtsi changes.
> 
> I'm not sure which is the best way to do this?

I assume that backward compat will get the most votes, so I won't fight 
against it :-)

-- 
Regards,

Laurent Pinchart


      parent reply	other threads:[~2014-03-07 10:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 18:02 [PATCH 3/3] clk-mstp: add backwards comapt for indicies field Ben Dooks
2014-02-13 23:15 ` Laurent Pinchart
2014-02-14 10:27 ` Ben Dooks
2014-02-14 14:36 ` Laurent Pinchart
2014-02-23 20:23 ` Mike Turquette
2014-03-06 19:06 ` Ben Dooks
2014-03-07 10:10 ` Laurent Pinchart [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=58097128.FjP4hkbmQo@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-sh@vger.kernel.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.