From: "Jakub Piotr Cłapa" <jpc-ml@zenburn.net>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: [omap3isp] xclk deadlock
Date: Fri, 05 Jul 2013 00:36:44 +0200 [thread overview]
Message-ID: <51D5F8FC.4040504@zenburn.net> (raw)
In-Reply-To: <2398527.WgqgO0AkRo@avalon>
Hi Laurent,
On 04.07.13 23:11, Laurent Pinchart wrote:
> The omap3isp/xclk clock branch was used only to push patches to the media
> tree, I should have deleted it afterwards. Mike's reentrancy patches were
> already merged (or scheduled for merge) in mainline at that time, and for
> technical reasons they were not present in the omap3isp/xclk branch.
Thanks for the explanation. It would be great if you could update your
board/beagle/mt9p031 branch and include the discussed changes. I belive
your branch is the only authoritative source of magic required to get
the Aptina+Beagle combination going.
> I've now deleted the branch from the public tree, sorry for the confusion.
Not a problem at all. The confusion was worse when I was trying to apply
random patch files found via Google. ;)
--
regards,
Jakub Piotr Cłapa
LoEE.pl
next prev parent reply other threads:[~2013-07-04 22:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 1:00 [omap3isp] xclk deadlock Jakub Piotr Cłapa
2013-07-04 20:21 ` Jakub Piotr Cłapa
2013-07-04 21:11 ` Laurent Pinchart
2013-07-04 22:36 ` Jakub Piotr Cłapa [this message]
2013-07-05 10:48 ` Laurent Pinchart
2013-07-12 14:44 ` Jakub Piotr Cłapa
2013-07-17 12:50 ` Laurent Pinchart
2013-07-17 22:17 ` Jakub Piotr Cłapa
2013-07-26 15:51 ` Laurent Pinchart
2013-07-26 23:51 ` Jakub Piotr Cłapa
2013-07-26 7:50 ` Tomi Valkeinen
2013-07-26 15:37 ` [omapdss] fault in dispc_write_irqenable [was: Re: [omap3isp] xclk deadlock] Jakub Piotr Cłapa
2013-07-26 15:52 ` Laurent Pinchart
2013-07-26 19:02 ` Jakub Piotr Cłapa
2013-07-26 19:13 ` Laurent Pinchart
2013-07-29 6:19 ` Tomi Valkeinen
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=51D5F8FC.4040504@zenburn.net \
--to=jpc-ml@zenburn.net \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
/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.