From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/3] Lager i2c bus support
Date: Wed, 25 Sep 2013 08:50:25 +0000 [thread overview]
Message-ID: <1683639.Kv1TdYPjqG@avalon> (raw)
In-Reply-To: <1378813194-19493-1-git-send-email-ulrich.hecht@gmail.com>
Hi Simon,
On Wednesday 25 September 2013 13:59:26 Simon Horman wrote:
> On Thu, Sep 19, 2013 at 02:28:20PM -0700, Simon Horman wrote:
> > On Mon, Sep 16, 2013 at 03:23:46PM +0200, Ulrich Hecht wrote:
> > > On Thu, Sep 12, 2013 at 3:51 PM, Guennadi Liakhovetski wrote:
> > Apologies for me excessively slow response.
> >
> > > > What is your preferred way to resolve this? We can choose one of the
> > > > following:
> > > >
> > > > 1. merge the two i2c clock patches into one - feel free to take my
> > > > code into "ARM: shmobile: r8a7790: add the I2C bus clock" from this
> > > > series
> > > >
> > > > 2. port one of the patches on top of the other one - if this series
> > > > isn't going to be modified again, I can port my patch on top of it.
> > >
> > > Since my DU stuff will have to be ported to DT anyway and I have found
> > > that my work towards that on the rcar-i2c driver is virtually
> > > identical to what Guennadi has already posted, I'd suggest to go with
> > > his version.
> >
> > That sounds like a good resolution to me.
>
> Btw, as far as I can see the current status of this work is as follows.
>
> 1. Awaiting Ack from Laurent on
> "pinctrl: sh-pfc: r8a7790: add pin definitions for the I2C3 interface"
> by Guennadi. This patch is targeted at Linus Walleji's tree.
I've replied to Guennadi's patch, there will likely be a v2.
> 2. Once Linus has queued up that patch I will queue up
> "ARM: shmobile: r8a7790: add I2C support in Device Tree mode"
> in the renesas tree.
There's no dependency between the two patches, you can thus queue it up
already.
> 3. From there I think you should be able to repost the parts of your
> series that aren't included in Guennadi's work.
>
> To be clear: I have marked this series as "Changes Requested" in patchwork
> and it is will not be on my radar unless it is re-posted in some form.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-09-25 8:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 11:39 [PATCH 0/3] Lager i2c bus support Ulrich Hecht
2013-09-10 21:10 ` Guennadi Liakhovetski
2013-09-12 13:51 ` Guennadi Liakhovetski
2013-09-16 13:23 ` Ulrich Hecht
2013-09-19 21:28 ` Simon Horman
2013-09-25 4:59 ` Simon Horman
2013-09-25 8:50 ` Laurent Pinchart [this message]
2013-09-25 23:48 ` 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=1683639.Kv1TdYPjqG@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 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).