[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141105150814.GT3136@valkosipuli.retiisi.org.uk>
Date: Wed, 5 Nov 2014 17:08:15 +0200
From: Sakari Ailus <sakari.ailus@....fi>
To: Boris Brezillon <boris.brezillon@...e-electrons.com>
Cc: Mauro Carvalho Chehab <m.chehab@...sung.com>,
Hans Verkuil <hans.verkuil@...co.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
linux-media@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-api@...r.kernel.org, devel@...verdev.osuosl.org,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
Guennadi Liakhovetski <g.liakhovetski@....de>
Subject: Re: [PATCH 11/15] [media] Deprecate v4l2_mbus_pixelcode
Hi Boris,
On Tue, Nov 04, 2014 at 10:55:06AM +0100, Boris Brezillon wrote:
> The v4l2_mbus_pixelcode enum (or its values) should be replaced by the
> media_bus_format enum.
> Keep this enum in v4l2-mediabus.h and create a new header containing
> the v4l2_mbus_framefmt struct definition (which is not deprecated) so
> that we can add a #warning statement in v4l2-mediabus.h and hopefully
> encourage users to move to the new definitions.
>
> Replace inclusion of v4l2-mediabus.h with v4l2-mbus.h in all common headers
> and update the documentation Makefile to parse v4l2-mbus.h instead of
> v4l2-mediabus.h.
>
> Signed-off-by: Boris Brezillon <boris.brezillon@...e-electrons.com>
> ---
> Documentation/DocBook/media/Makefile | 2 +-
> include/media/v4l2-mediabus.h | 2 +-
> include/uapi/linux/Kbuild | 1 +
> include/uapi/linux/v4l2-mbus.h | 35 +++++++++++++++++++++++++++++++++++
> include/uapi/linux/v4l2-mediabus.h | 26 ++++----------------------
I would keep the original file name, even if the compatibility definitions
are there. I don't see any harm in having them around as well.
--
Sakari Ailus
e-mail: sakari.ailus@....fi XMPP: sailus@...iisi.org.uk
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists