linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Sakari Ailus <sakari.ailus@iki.fi>,
	linux-media@vger.kernel.org, linux-omap@vger.kernel.org,
	khilman@deeprootsystems.com
Subject: Re: [PATCH v5 0/3] OMAP 3 CSI-2 configuration
Date: Thu, 18 Oct 2012 08:39:00 -0700	[thread overview]
Message-ID: <20121018153859.GC30550@atomide.com> (raw)
In-Reply-To: <8138988.XlrgGsn68R@avalon>

* Laurent Pinchart <laurent.pinchart@ideasonboard.com> [121018 06:46]:
> Hi Tony,
> 
> On Tuesday 16 October 2012 16:51:40 Laurent Pinchart wrote:
> > Hi Sakari,
> > 
> > Thanks for the patches.
> > 
> > For the whole series,
> > 
> > Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > 
> > Tony, do you want to take patch 1/3 in your tree, or can I push the whole
> > series through mine ?
> 
> Ping ?

Oops sorry for the delay. Please take the whole series as it's unlikely
to conflict with the other omap changes.

Regards,

Tony

  reply	other threads:[~2012-10-18 15:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-14 10:31 [PATCH v5 0/3] OMAP 3 CSI-2 configuration Sakari Ailus
2012-10-14 10:31 ` [PATCH v5 1/3] omap3isp: Add CSI configuration registers from control block to ISP resources Sakari Ailus
2012-10-14 10:31 ` [PATCH v5 2/3] omap3isp: Add PHY routing configuration Sakari Ailus
2012-10-14 10:31 ` [PATCH v5 3/3] omap3isp: Configure CSI-2 phy based on platform data Sakari Ailus
2012-10-16 14:51 ` [PATCH v5 0/3] OMAP 3 CSI-2 configuration Laurent Pinchart
2012-10-18 13:45   ` Laurent Pinchart
2012-10-18 15:39     ` Tony Lindgren [this message]
2012-10-20 14:11   ` [PATCH v5.1 1/3] omap3isp: Add CSI configuration registers from control block to ISP resources Sakari Ailus
2012-10-20 17:38     ` Laurent Pinchart

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=20121018153859.GC30550@atomide.com \
    --to=tony@atomide.com \
    --cc=khilman@deeprootsystems.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-omap@vger.kernel.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).