From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
dri-devel@lists.freedesktop.org, kernel@pengutronix.de,
Grant Likely <grant.likely@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH v3 2/9] staging: imx-drm: Add temporary copies of v4l2-of parsing functions
Date: Mon, 24 Feb 2014 15:52:21 +0000 [thread overview]
Message-ID: <20140224155221.GM21483@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1392723370-4772-3-git-send-email-p.zabel@pengutronix.de>
On Tue, Feb 18, 2014 at 12:36:03PM +0100, Philipp Zabel wrote:
> From: Philipp Zabel <philipp.zabel@gmail.com>
>
> The existing v4l2-of parser functions for the video interface bindings
> described in Documentation/device-tree/bindings/media/video-interfaces.txt
> are useful for DRM drivers, too. They will be moved to drivers/media
> so they can be used by drm drivers, too. Until then, duplicate the
> v4l2-of parser functions temporarily.
>
> Signed-off-by: Philipp Zabel <philipp.zabel@gmail.com>
Ergh. So, because we can't get agreement on where to put the common
helpers, we have to put up with adding duplicate helpers into the
staging directory, inflating not only the kernel source code size
but also the binary size as well.
Come on people, get agreement on how to deal with this. Staging may
be a dumping ground for drivers which aren't ready to be merged as
proper drivers, but this is no reason to ignore proper process.
Do we, or do we not want to get imx-drm out of drivers/staging? If
we do, the only way that's going to happen is if we stop throwing in
this kind of stuff.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-02-24 15:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 11:36 [RFC PATCH v3 0/9] imx-drm dt bindings Philipp Zabel
2014-02-18 11:36 ` [RFC PATCH v3 1/9] staging: imx-drm-core: don't request probe deferral in imx_drm_encoder_parse_of Philipp Zabel
2014-02-24 15:49 ` Russell King - ARM Linux
2014-02-24 16:56 ` Philipp Zabel
2014-02-24 17:03 ` Philipp Zabel
2014-02-24 17:06 ` Russell King - ARM Linux
2014-02-24 17:41 ` Philipp Zabel
2014-02-18 11:36 ` [RFC PATCH v3 2/9] staging: imx-drm: Add temporary copies of v4l2-of parsing functions Philipp Zabel
2014-02-24 15:52 ` Russell King - ARM Linux [this message]
2014-02-24 17:31 ` Philipp Zabel
2014-02-18 11:36 ` [RFC PATCH v3 3/9] staging: imx-drm-core: Use OF graph to find components and connections between encoder and crtcs Philipp Zabel
2014-02-18 11:36 ` [RFC PATCH v3 4/9] staging: imx-drm: Document updated imx-drm device tree bindings Philipp Zabel
2014-02-18 11:36 ` [RFC PATCH v3 5/9] staging: imx-drm: Document imx-hdmi " Philipp Zabel
2014-02-18 11:36 ` [RFC PATCH v3 7/9] ARM: dts: imx53: Add IPU DI ports and endpoints, move imx-drm node to dtsi Philipp Zabel
2014-02-18 11:36 ` [RFC PATCH v3 8/9] ARM: dts: imx6qdl: " Philipp Zabel
[not found] ` <1392723370-4772-1-git-send-email-p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-02-18 11:36 ` [RFC PATCH v3 6/9] ARM: dts: imx51: Add IPU " Philipp Zabel
2014-02-18 11:36 ` [RFC PATCH v3 9/9] staging: imx-drm: Update TODO Philipp Zabel
2014-02-24 15:36 ` [RFC PATCH v3 0/9] imx-drm dt bindings Philipp Zabel
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=20140224155221.GM21483@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
/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).