From: Philipp Zabel <p.zabel@pengutronix.de>
To: Steve Longerbeam <slongerbeam@gmail.com>, linux-media@vger.kernel.org
Cc: Hans Verkuil <hans.verkuil@cisco.com>,
Tim Harvey <tharvey@gateworks.com>,
kernel@pengutronix.de
Subject: Re: [PATCH v8] media: imx: add mem2mem device
Date: Fri, 14 Jun 2019 16:13:57 +0200 [thread overview]
Message-ID: <1560521637.18257.5.camel@pengutronix.de> (raw)
In-Reply-To: <9ca64889-046f-324c-9a5a-94ea0082f21e@gmail.com>
Hi Steve,
On Tue, 2019-06-11 at 18:08 -0700, Steve Longerbeam wrote:
> Hi Philipp,
>
> Version 9 will also need to fix merge conflicts due to the recent module
> re-org and the switch to sync registration for the IPU internal subdevs.
>
> I've done that work already, feel free to cherry-pick it from my github
> fork if you agree with the merge fixes:
>
> git@github.com:slongerbeam/mediatree.git, branch imx/mem2mem.v8.
>
> Btw, some bugs have been found and fixed in ipu-image-convert.c. I will
> be posting a patch-set shortly. You can review branch imx/bgthree-2136
> in my fork for the changes.
Thank you, I'll resend the mem2mem next week. I had rebased already, but
I haven't tested unbinding/rebinding yet, as imx-media exploded on me
even without the mem2mem patch when I try tried.
regards
Philipp
prev parent reply other threads:[~2019-06-14 14:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 16:44 [PATCH v8] media: imx: add mem2mem device Philipp Zabel
2019-05-10 13:03 ` Hans Verkuil
2019-05-29 15:44 ` [v8] " Sven Van Asbroeck
2019-05-29 16:53 ` Fabio Estevam
2019-05-29 17:20 ` Sven Van Asbroeck
2019-05-29 20:55 ` Sven Van Asbroeck
2019-05-29 22:19 ` Fabio Estevam
2019-05-29 23:48 ` Nicolas Dufresne
2019-05-29 23:52 ` Nicolas Dufresne
2019-05-31 15:34 ` Nicolas Dufresne
2019-05-31 16:07 ` Sven Van Asbroeck
2019-05-31 17:34 ` Nicolas Dufresne
2019-05-30 21:09 ` Nicolas Dufresne
2019-05-30 21:34 ` Sven Van Asbroeck
2019-05-30 22:18 ` Fabio Estevam
2019-05-31 0:26 ` Sven Van Asbroeck
2019-05-31 0:26 ` Robin Gong
2019-05-31 21:58 ` Sven Van Asbroeck
2019-06-04 8:51 ` Robin Gong
2019-06-04 17:57 ` Sven Van Asbroeck
2019-06-05 10:08 ` Robin Gong
2019-06-05 13:51 ` Sven Van Asbroeck
2019-06-06 2:32 ` Robin Gong
2019-06-06 13:34 ` Sven Van Asbroeck
2019-06-10 9:09 ` Robin Gong
2019-06-10 15:46 ` Sven Van Asbroeck
2019-06-11 9:09 ` Robin Gong
2019-06-11 9:17 ` Robin Gong
2019-06-11 17:30 ` Sven Van Asbroeck
2019-06-13 8:52 ` Robin Gong
2019-06-13 14:00 ` Sven Van Asbroeck
2019-05-31 21:16 ` Sven Van Asbroeck
2019-06-12 1:08 ` [PATCH v8] " Steve Longerbeam
2019-06-14 14:13 ` Philipp Zabel [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=1560521637.18257.5.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=hans.verkuil@cisco.com \
--cc=kernel@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=slongerbeam@gmail.com \
--cc=tharvey@gateworks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox