From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Suman Anna <s-anna@ti.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Sakari Ailus <sakari.ailus@iki.fi>
Subject: Re: [PATCH 1/2] ARM: OMAP2+: Remove legacy OMAP3 ISP instantiation
Date: Mon, 09 Nov 2015 19:48:33 +0200 [thread overview]
Message-ID: <10133709.DpTcCTIhJE@avalon> (raw)
In-Reply-To: <20151012170558.GF23801@atomide.com>
Hi Tony,
On Monday 12 October 2015 10:05:59 Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [150914 09:37]:
> > * Suman Anna <s-anna@ti.com> [150914 09:33]:
> >> On 09/03/2015 05:34 PM, Suman Anna wrote:
> >>> On 07/16/2015 07:58 AM, Tony Lindgren wrote:
> >>>> * Laurent Pinchart [150716 05:57]:
> >>>> The OMAP3 ISP is now fully supported in DT, remove its instantiation
> >>>>> from C code.
> >>>>
> >>>> Please feel to queue this along with the second patch in this series,
> >>>> this should not cause any merge conflicts:
> >>>>
> >>>> Acked-by: Tony Lindgren <tony@atomide.com>
> >>>
> >>> Just wondering if you have already queued this, I see the v4l changes
> >>> in linux-next, but not this patch. Also, can you confirm if this
> >>> series is making it into 4.3?
> >>
> >> This patch is not in 4.3-rc1, can you pick this up for the next merge
> >> window? I am gonna send out some additional cleanup patches (removing
> >> legacy mailbox and iommu pieces) on top on this patch. The second patch
> >> in this series did make it.
> >
> > OK tagging this one for next, will apply once I'm done with fixes.
>
> Applying into omap-for-v4.4/cleanup finally thanks.
Is see that the patch is in your master branch but not your for-next branch.
Will it make it to v4.4-rc1 ?
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: OMAP2+: Remove legacy OMAP3 ISP instantiation
Date: Mon, 09 Nov 2015 19:48:33 +0200 [thread overview]
Message-ID: <10133709.DpTcCTIhJE@avalon> (raw)
In-Reply-To: <20151012170558.GF23801@atomide.com>
Hi Tony,
On Monday 12 October 2015 10:05:59 Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [150914 09:37]:
> > * Suman Anna <s-anna@ti.com> [150914 09:33]:
> >> On 09/03/2015 05:34 PM, Suman Anna wrote:
> >>> On 07/16/2015 07:58 AM, Tony Lindgren wrote:
> >>>> * Laurent Pinchart [150716 05:57]:
> >>>> The OMAP3 ISP is now fully supported in DT, remove its instantiation
> >>>>> from C code.
> >>>>
> >>>> Please feel to queue this along with the second patch in this series,
> >>>> this should not cause any merge conflicts:
> >>>>
> >>>> Acked-by: Tony Lindgren <tony@atomide.com>
> >>>
> >>> Just wondering if you have already queued this, I see the v4l changes
> >>> in linux-next, but not this patch. Also, can you confirm if this
> >>> series is making it into 4.3?
> >>
> >> This patch is not in 4.3-rc1, can you pick this up for the next merge
> >> window? I am gonna send out some additional cleanup patches (removing
> >> legacy mailbox and iommu pieces) on top on this patch. The second patch
> >> in this series did make it.
> >
> > OK tagging this one for next, will apply once I'm done with fixes.
>
> Applying into omap-for-v4.4/cleanup finally thanks.
Is see that the patch is in your master branch but not your for-next branch.
Will it make it to v4.4-rc1 ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-11-09 17:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 12:55 [PATCH 0/2] omap3isp: Remove legacy platform data support Laurent Pinchart
2015-07-16 12:55 ` Laurent Pinchart
2015-07-16 12:55 ` [PATCH 1/2] ARM: OMAP2+: Remove legacy OMAP3 ISP instantiation Laurent Pinchart
2015-07-16 12:55 ` Laurent Pinchart
2015-07-16 12:58 ` Tony Lindgren
2015-07-16 12:58 ` Tony Lindgren
2015-09-03 22:34 ` Suman Anna
2015-09-03 22:34 ` Suman Anna
2015-09-14 16:29 ` Suman Anna
2015-09-14 16:29 ` Suman Anna
2015-09-14 16:33 ` Tony Lindgren
2015-09-14 16:33 ` Tony Lindgren
2015-10-12 17:05 ` Tony Lindgren
2015-10-12 17:05 ` Tony Lindgren
2015-11-09 17:48 ` Laurent Pinchart [this message]
2015-11-09 17:48 ` Laurent Pinchart
2015-07-16 15:45 ` Sakari Ailus
2015-07-16 15:45 ` Sakari Ailus
2015-07-16 15:52 ` Laurent Pinchart
2015-07-16 15:52 ` Laurent Pinchart
2015-07-16 16:01 ` Sakari Ailus
2015-07-16 16:01 ` Sakari Ailus
2015-07-16 12:55 ` [PATCH 2/2] v4l: omap3isp: Drop platform data support Laurent Pinchart
2015-07-16 12:55 ` Laurent Pinchart
2015-07-16 16:14 ` [PATCH 0/2] omap3isp: Remove legacy " Sakari Ailus
2015-07-16 16:14 ` Sakari Ailus
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=10133709.DpTcCTIhJE@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=s-anna@ti.com \
--cc=sakari.ailus@iki.fi \
--cc=tony@atomide.com \
/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.