From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Hans Verkuil <hverkuil@xs4all.nl>, Yong Zhi <yong.zhi@intel.com>,
linux-media@vger.kernel.org
Cc: jian.xu.zheng@intel.com, rajmohan.mani@intel.com,
hyungwoo.yang@intel.com
Subject: Re: [PATCH 3/3] [media] intel-ipu3: cio2: Add new MIPI-CSI2 driver
Date: Thu, 4 May 2017 00:00:52 +0300 [thread overview]
Message-ID: <775060aa-9f9c-005c-91a4-44a83e5ad35b@linux.intel.com> (raw)
In-Reply-To: <4a486cd9-48f8-fcab-6abb-4e89671c95fe@xs4all.nl>
Hi Hans,
Hans Verkuil wrote:
> Is it likely that there will be more Intel PCI drivers? If so, then we
> can consider putting it in pci/intel/ipu3/.
Maybe. There is more hardware and they're called IPUs, too. I think this
naming would be a good idea going forward.
--
Regards,
Sakari Ailus
sakari.ailus@linux.intel.com
next prev parent reply other threads:[~2017-05-03 21:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 23:34 [PATCH 0/3] [media] add IPU3 CIO2 CSI2 driver Yong Zhi
2017-04-29 23:34 ` [PATCH 1/3] [media] videodev2.h, v4l2-ioctl: add IPU3 raw10 color format Yong Zhi
2017-04-29 23:34 ` [PATCH 2/3] [media] doc-rst: add IPU3 raw10 bayer pixel format definitions Yong Zhi
2017-05-08 8:33 ` Hans Verkuil
2017-05-16 12:02 ` Sakari Ailus
2017-04-29 23:34 ` [PATCH 3/3] [media] intel-ipu3: cio2: Add new MIPI-CSI2 driver Yong Zhi
2017-04-30 0:33 ` kbuild test robot
2017-05-02 13:00 ` Sakari Ailus
2017-05-03 10:57 ` Tuukka Toivonen
2017-05-03 20:23 ` Sakari Ailus
2017-05-09 15:27 ` Tomasz Figa
2017-05-25 14:57 ` Tomasz Figa
2017-05-03 8:58 ` Sakari Ailus
2017-05-03 11:06 ` Tuukka Toivonen
2017-05-03 20:25 ` Sakari Ailus
2017-05-03 20:35 ` Hans Verkuil
2017-05-03 21:00 ` Sakari Ailus [this message]
2017-05-08 9:06 ` Hans Verkuil
2017-05-08 12:10 ` Sakari Ailus
2017-05-08 12:32 ` Hans Verkuil
2017-05-08 12:56 ` Sakari Ailus
2017-05-08 13:08 ` Hans Verkuil
2017-05-08 21:32 ` Sakari Ailus
2017-06-01 10:27 ` Sakari Ailus
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=775060aa-9f9c-005c-91a4-44a83e5ad35b@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=hverkuil@xs4all.nl \
--cc=hyungwoo.yang@intel.com \
--cc=jian.xu.zheng@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=rajmohan.mani@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).