From: Rui Miguel Silva <rui.silva@linaro.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
sakari.ailus@linux.intel.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-media@vger.kernel.org
Subject: Re: [PATCH v8 00/12] media: staging/imx7: add i.MX7 media driver
Date: Thu, 22 Nov 2018 09:38:51 +0000 [thread overview]
Message-ID: <m34lc9moyc.fsf@linaro.org> (raw)
In-Reply-To: <18c5ad5c-e800-c317-4246-a8a207f3dff4@xs4all.nl>
Hi Hans,
On Wed 21 Nov 2018 at 11:53, Hans Verkuil wrote:
> On 11/21/2018 12:15 PM, Rui Miguel Silva wrote:
>> Hi,
>> This series introduces the Media driver to work with the i.MX7
>> SoC. it uses the
>> already existing imx media core drivers but since the i.MX7,
>> contrary to
>> i.MX5/6, do not have an IPU and because of that some changes in
>> the imx media
>> core are made along this series to make it support that case.
>
> Can you run scripts/checkpatch.pl --strict over these patches? I
> get too
> many messages from it. Most should be easy to fix.
Yeah, I will fix as much as I think is sane, some I will leave it
to
make code more readable.
---
Cheers,
Rui
prev parent reply other threads:[~2018-11-22 9:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 11:15 [PATCH v8 00/12] media: staging/imx7: add i.MX7 media driver Rui Miguel Silva
2018-11-21 11:15 ` [PATCH v8 01/12] media: staging/imx: refactor imx media device probe Rui Miguel Silva
2018-11-21 22:40 ` kbuild test robot
2018-11-21 11:15 ` [PATCH v8 02/12] media: staging/imx: rearrange group id to take in account IPU Rui Miguel Silva
2018-11-21 11:15 ` [PATCH v8 03/12] media: staging/imx7: add imx7 CSI subdev driver Rui Miguel Silva
2018-11-21 22:29 ` Sakari Ailus
2018-11-22 9:46 ` Rui Miguel Silva
2018-11-21 11:15 ` [PATCH v8 04/12] media: staging/imx7: add MIPI CSI-2 receiver subdev for i.MX7 Rui Miguel Silva
2018-11-21 22:54 ` kbuild test robot
2018-11-21 22:54 ` [PATCH] media: staging/imx7: fix platform_no_drv_owner.cocci warnings kbuild test robot
2018-11-21 11:15 ` [PATCH v8 05/12] media: dt-bindings: add bindings for i.MX7 media driver Rui Miguel Silva
2018-11-21 22:16 ` Sakari Ailus
2018-11-22 9:42 ` Rui Miguel Silva
2018-11-21 11:15 ` [PATCH v8 06/12] ARM: dts: imx7s: add mipi phy power domain Rui Miguel Silva
2018-11-21 11:15 ` [PATCH v8 07/12] ARM: dts: imx7s: add multiplexer controls Rui Miguel Silva
2018-11-21 11:15 ` [PATCH v8 08/12] ARM: dts: imx7: Add video mux, csi and mipi_csi and connections Rui Miguel Silva
2018-11-21 11:15 ` [PATCH v8 09/12] ARM: dts: imx7s-warp: add ov2680 sensor node Rui Miguel Silva
2018-11-21 11:15 ` [PATCH v8 10/12] media: imx7.rst: add documentation for i.MX7 media driver Rui Miguel Silva
2018-11-21 11:15 ` [PATCH v8 11/12] media: staging/imx: add i.MX7 entries to TODO file Rui Miguel Silva
2018-11-21 11:15 ` [PATCH v8 12/12] media: video-mux: add bayer formats Rui Miguel Silva
2018-11-21 11:53 ` [PATCH v8 00/12] media: staging/imx7: add i.MX7 media driver Hans Verkuil
2018-11-22 9:38 ` Rui Miguel Silva [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=m34lc9moyc.fsf@linaro.org \
--to=rui.silva@linaro.org \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--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 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).