From: Pavel Machek <pavel@ucw.cz>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>, linux-media@vger.kernel.org
Subject: Re: [PATCH 0/2] OMAP3ISP CCP2 support
Date: Fri, 14 Jul 2017 08:56:11 +0200 [thread overview]
Message-ID: <20170714065611.GA14652@amd> (raw)
In-Reply-To: <20170713220947.ntfpwkoitfadshnt@valkosipuli.retiisi.org.uk>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
Hi!
> > > The patches work fine on N9.
> >
> > I was able to fix the userspace, and they work for me, too. For both:
> >
> > Acked-by: Pavel Machek <pavel@ucw.cz>
> > Tested-by: Pavel Machek <pavel@ucw.cz>
>
> Thanks! I've applied these on ccp2-prepare. ccp2 branch is rebased, too.
Thanks!
I rebased my patches on top of it, and pushed result to camera-fw6-2
branch.
Can you drop this patch from ccp2 branch?
https://git.linuxtv.org/sailus/media_tree.git/commit/?h=ccp2&id=27be6eb1f66389632a5d9dbaf0426a83f1b99b54
It is preparation for subdevices support on isp; but those will not be
needed there as we decided to move subdevices to et8ek8.
Thanks and best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-07-14 6:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 16:19 [PATCH 0/2] OMAP3ISP CCP2 support Sakari Ailus
2017-07-13 16:19 ` [PATCH 1/2] omap3isp: Explicitly set the number of CSI-2 lanes used in lane cfg Sakari Ailus
2017-07-13 16:19 ` [PATCH 2/2] omap3isp: add CSI1 support Sakari Ailus
2017-07-13 21:13 ` [PATCH 0/2] OMAP3ISP CCP2 support Pavel Machek
2017-07-13 21:26 ` Sakari Ailus
2017-07-13 21:38 ` Pavel Machek
2017-07-13 22:09 ` Sakari Ailus
2017-07-14 6:56 ` Pavel Machek [this message]
2017-07-14 22:02 ` 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=20170714065611.GA14652@amd \
--to=pavel@ucw.cz \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=sakari.ailus@linux.intel.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.