From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] [media] include/media: move platform driver headers to a separate dir
Date: Wed, 11 Nov 2015 21:26:31 +0100 [thread overview]
Message-ID: <4220808.QEkJDXYE1T@wuerfel> (raw)
In-Reply-To: <09e182fa61a7122356b790cd2a4a7f622dabb4ce.1447261977.git.mchehab@osg.samsung.com>
On Wednesday 11 November 2015 15:14:48 Mauro Carvalho Chehab wrote:
> rename include/media/{ => platform}/exynos-fimc.h (100%)
> rename include/media/{ => platform}/mmp-camera.h (100%)
> rename include/media/{ => platform}/omap1_camera.h (100%)
> rename include/media/{ => platform}/omap4iss.h (100%)
> rename include/media/{ => platform}/s3c_camif.h (100%)
> rename include/media/{ => platform}/s5p_hdmi.h (100%)
> rename include/media/{ => platform}/sh_mobile_ceu.h (100%)
> rename include/media/{ => platform}/sh_mobile_csi2.h (100%)
> rename include/media/{ => platform}/sh_vou.h (100%)
> rename include/media/{ => platform}/sii9234.h (100%)
> rename include/media/{ => platform}/soc_camera.h (100%)
> rename include/media/{ => platform}/soc_camera_platform.h (98%)
> rename include/media/{ => platform}/soc_mediabus.h (100%)
This still seems to be a mix of various things. Some of these are interfaces
between drivers, while others declare a foo_platform_data structure that
is used to interface between platform code and the driver.
I think the latter should go into include/linux/platform_data/media/*.h instead.
Arnd
next prev parent reply other threads:[~2015-11-11 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <413d2bb0b813a7e62867de7a94b0ab61e16cb1cb.1447261977.git.mchehab@osg.samsung.com>
2015-11-11 17:14 ` [PATCH 2/2] [media] include/media: move platform driver headers to a separate dir Mauro Carvalho Chehab
2015-11-11 20:26 ` Arnd Bergmann [this message]
2015-11-13 19:13 ` Mauro Carvalho Chehab
2015-11-13 20:15 ` Geert Uytterhoeven
2015-11-13 21:31 ` Arnd Bergmann
2015-11-13 22:57 ` Mauro Carvalho Chehab
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=4220808.QEkJDXYE1T@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox