linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: devel@driverdev.osuosl.org, linux-doc@vger.kernel.org,
	linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sakari Ailus <sakari.ailus@iki.fi>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	Mauro Carvalho Chehab <m.chehab@samsung.com>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v6 00/10]  [media] Make mediabus format subsystem neutral
Date: Mon, 10 Nov 2014 18:25:50 +0100	[thread overview]
Message-ID: <20141110182550.18d95bce@bbrezillon> (raw)
In-Reply-To: <1415640114-14930-1-git-send-email-boris.brezillon@free-electrons.com>

On Mon, 10 Nov 2014 18:21:44 +0100
Boris Brezillon <boris.brezillon@free-electrons.com> wrote:

> Hello,
> 
> This patch series prepares the use of media bus formats outside of
> the V4L2 subsytem (my final goal is to use it in the Atmel HLCDC DRM
> driver where I have to configure my DPI/RGB bus according to the
> connected display).
> 
> The series first defines MEDIA_BUS_FMT_ macros, and then replace all
> references to the v4l2_mbus_pixelcode enum and its values within the
> kernel.
> 
> Best Regards,
> 
> Boris
> 
> Changes since v5:
> - fix V4L2_MBUS_FROM_MEDIA_BUS_FMT macro definition

Sorry for the noise, I sent the wrong patch set :-(.

-- 
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      parent reply	other threads:[~2014-11-10 17:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 17:21 [PATCH v6 00/10] [media] Make mediabus format subsystem neutral Boris Brezillon
2014-11-10 17:21 ` [PATCH v6 01/10] [media] Move mediabus format definition to a more standard place Boris Brezillon
2014-11-10 17:21 ` [PATCH v6 02/10] [media] v4l: Update subdev-formats doc with new MEDIA_BUS_FMT values Boris Brezillon
2014-11-10 17:21 ` [PATCH v6 03/10] [media] Make use of the new media_bus_format definitions Boris Brezillon
2014-11-10 17:21 ` [PATCH v6 04/10] [media] i2c: Make use of media_bus_format enum Boris Brezillon
2014-11-10 17:21 ` [PATCH v6 05/10] [media] pci: Make use of MEDIA_BUS_FMT definitions Boris Brezillon
2014-11-10 17:21 ` [PATCH v6 06/10] [media] platform: Make use of media_bus_format enum Boris Brezillon
2014-11-10 17:21 ` [PATCH v6 07/10] [media] usb: " Boris Brezillon
2014-11-10 17:21 ` [PATCH v6 08/10] staging: media: Make use of MEDIA_BUS_FMT_ definitions Boris Brezillon
2014-11-10 17:21 ` [PATCH v6 09/10] gpu: ipu-v3: Make use of media_bus_format enum Boris Brezillon
2014-11-10 17:21 ` [PATCH v6 10/10] [media] v4l: Forbid usage of V4L2_MBUS_FMT definitions inside the kernel Boris Brezillon
2014-11-10 17:25 ` Boris Brezillon [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=20141110182550.18d95bce@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=hans.verkuil@cisco.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=sakari.ailus@iki.fi \
    /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).