From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, yong.zhi@intel.com
Subject: Re: [PATCH 0/2] A few IPU3 CIO2 fixes
Date: Fri, 29 Dec 2017 11:42:56 -0200 [thread overview]
Message-ID: <20171229114256.149770c4@vento.lan> (raw)
In-Reply-To: <20171229125914.7218-1-sakari.ailus@linux.intel.com>
Em Fri, 29 Dec 2017 14:59:12 +0200
Sakari Ailus <sakari.ailus@linux.intel.com> escreveu:
> Hi Yong and Mauro,
>
> The two patches are addressing a few matters Mauro pointed out whilst
> handling the CIO2 driver pull request.
>
> Yong: could you review especially the latter patch?
I'm applying the first one, as it cleans 4 warnings. I'll wait for
an ack for the second one.
Regards,
Mauro\
prev parent reply other threads:[~2017-12-29 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 12:59 [PATCH 0/2] A few IPU3 CIO2 fixes Sakari Ailus
2017-12-29 12:59 ` [PATCH 1/2] v4l: Fix references in Intel IPU3 Bayer documentation Sakari Ailus
2017-12-29 12:59 ` [PATCH 2/2] intel-ipu3: Rename arr_size macro, use min Sakari Ailus
2017-12-29 13:42 ` Mauro Carvalho Chehab [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=20171229114256.149770c4@vento.lan \
--to=mchehab@s-opensource.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=yong.zhi@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 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).