From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-media@vger.kernel.org
Subject: Re: [RFC 1/1] omap3isp: Ignore endpoints with invalid configuration
Date: Wed, 1 Mar 2017 09:33:59 +0200 [thread overview]
Message-ID: <fc3116d9-b9c0-f9c7-f2ca-afce803e841f@linux.intel.com> (raw)
In-Reply-To: <20170228193016.GA25351@amd>
Pavel Machek wrote:
> On Tue 2017-02-28 14:45:31, Sakari Ailus wrote:
>> Pavel Machek wrote:
>>> Tested-by: Pavel Machek <pavel@ucw.cz>
>>
>> Thanks!
>>
>> I've applied the patch, plus yours, to the ccp2 branch.
>
> Thanks!
>
> https://git.linuxtv.org/sailus/media_tree.git/log/?h=ccp2 ? I don't
> see recent changes there...
I accidentally pushed it to a wrong place. Pushing again...
--
Sakari Ailus
sakari.ailus@linux.intel.com
next prev parent reply other threads:[~2017-03-01 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 12:02 [RFC 1/1] omap3isp: Ignore endpoints with invalid configuration Sakari Ailus
2017-02-28 12:35 ` Pavel Machek
2017-02-28 12:45 ` Sakari Ailus
2017-02-28 19:30 ` Pavel Machek
2017-03-01 7:33 ` Sakari Ailus [this message]
2017-03-01 10:37 ` Pavel Machek
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=fc3116d9-b9c0-f9c7-f2ca-afce803e841f@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=linux-media@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).