linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, sakari.ailus@iki.fi,
	Mike Turquette <mturquette@linaro.org>
Subject: Re: [PATCH 0/2] OMAP3 ISP common clock framework support
Date: Thu, 4 Apr 2013 18:25:08 -0300	[thread overview]
Message-ID: <20130404182508.6f1baaa2@redhat.com> (raw)
In-Reply-To: <1365073719-8038-1-git-send-email-laurent.pinchart@ideasonboard.com>

Em Thu,  4 Apr 2013 13:08:37 +0200
Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:

> Hello,
> 
> These two patches implement support for the common clock framework in the OMAP3
> ISP and MT9P031 drivers. They finally get rid of the last isp_platform_callback
> operation, and thus of the isp_platform_callback structure completely, as well
> as the only platform callback from the mt9p031 driver.
> 
> The patches depend on Mike Turquette's common clock framework reentrancy
> patches:
> 
>   clk: abstract locking out into helper functions
>   clk: allow reentrant calls into the clk framework
> 
> v6 of those two patches has been posted to LKML and LAKML.
> 
> Mauro, how would you like to proceed with merging these ? 

As discussed on IRC, just add those two patches on a branch based on
master. When asking me to pull from it, say that it should be a topic
branch that will depend on Mike's patches.

I'll hold them on a separate branch, sending them upstream only after
receiving an email from you or Mike that his patches got merged there
already.

> Mike, will the above
> two patches make it to v3.10 ? If so could you please provide a stable branch
> that Mauro could merge ?

Regards,
Mauro

> 
> Laurent Pinchart (2):
>   omap3isp: Use the common clock framework
>   mt9p031: Use the common clock framework
> 
>  drivers/media/i2c/mt9p031.c           |  22 ++-
>  drivers/media/platform/omap3isp/isp.c | 277 +++++++++++++++++++++++++---------
>  drivers/media/platform/omap3isp/isp.h |  22 ++-
>  include/media/mt9p031.h               |   2 -
>  include/media/omap3isp.h              |  10 +-
>  5 files changed, 240 insertions(+), 93 deletions(-)
> 


-- 

Cheers,
Mauro

      parent reply	other threads:[~2013-04-04 21:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 11:08 [PATCH 0/2] OMAP3 ISP common clock framework support Laurent Pinchart
2013-04-04 11:08 ` [PATCH 1/2] omap3isp: Use the common clock framework Laurent Pinchart
2013-04-04 11:20   ` Sakari Ailus
2013-04-04 11:27     ` Sylwester Nawrocki
2013-04-04 13:07       ` Sakari Ailus
2013-04-04 11:34     ` Laurent Pinchart
2013-04-04 11:08 ` [PATCH 2/2] mt9p031: " Laurent Pinchart
2013-04-04 21:25 ` Mauro Carvalho Chehab [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=20130404182508.6f1baaa2@redhat.com \
    --to=mchehab@redhat.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=sakari.ailus@iki.fi \
    /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).