All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Dave Airlie <airlied@redhat.com>,
	Boris Brezillion <boris.brezillon@free-electrons.com>,
	Hyun Kwon <hyun.kwon@xilinx.com>
Subject: Re: linux-next: manual merge of the v4l-dvb tree with Linus' tree
Date: Tue, 21 Apr 2015 10:49:52 +0300	[thread overview]
Message-ID: <5336539.Ny4ylH3Nve@avalon> (raw)
In-Reply-To: <20150421115409.73e6a066@canb.auug.org.au>

Hi Stephen,

On Tuesday 21 April 2015 11:54:09 Stephen Rothwell wrote:
> Hi Mauro,
> 
> Today's linux-next merge of the v4l-dvb tree got a conflict in
> include/uapi/linux/media-bus-format.h between various commits from
> Linus' tree and various commits from the v4l-dvb tree.
> 
> I reported this previously against the drm tree but some fo the numbers
> have changed.
> 
> I fixed it up (see below) and can carry the fix as necessary (no action
> is required).
> 
> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au
> 
> diff --cc include/uapi/linux/media-bus-format.h
> index 73c78f18a328,d391893064a0..000000000000
> --- a/include/uapi/linux/media-bus-format.h
> +++ b/include/uapi/linux/media-bus-format.h
> @@@ -45,18 -43,14 +45,20 @@@
>   #define MEDIA_BUS_FMT_RGB565_2X8_BE           0x1007
>   #define MEDIA_BUS_FMT_RGB565_2X8_LE           0x1008
>   #define MEDIA_BUS_FMT_RGB666_1X18             0x1009
>  +#define MEDIA_BUS_FMT_RGB666_1X24_CPADHI      0x1015
>  +#define MEDIA_BUS_FMT_RGB666_1X7X3_SPWG               0x1010
>  +#define MEDIA_BUS_FMT_BGR888_1X24             0x1013
>  +#define MEDIA_BUS_FMT_GBR888_1X24             0x1014
> + #define MEDIA_BUS_FMT_RBG888_1X24             0x100e
>   #define MEDIA_BUS_FMT_RGB888_1X24             0x100a
>   #define MEDIA_BUS_FMT_RGB888_2X12_BE          0x100b
>   #define MEDIA_BUS_FMT_RGB888_2X12_LE          0x100c
>  +#define MEDIA_BUS_FMT_RGB888_1X7X4_SPWG               0x1011
>  +#define MEDIA_BUS_FMT_RGB888_1X7X4_JEIDA      0x1012
>   #define MEDIA_BUS_FMT_ARGB8888_1X32           0x100d
> + #define MEDIA_BUS_FMT_RGB888_1X32_PADHI               0x100f
>   
>  -/* YUV (including grey) - next is     0x2025 */
>  +/* YUV (including grey) - next is     0x2026 */
>   #define MEDIA_BUS_FMT_Y8_1X8                  0x2001
>   #define MEDIA_BUS_FMT_UV8_1X8                 0x2015
>   #define MEDIA_BUS_FMT_UYVY8_1_5X8             0x2002
> @@@ -82,13 -80,7 +88,14 @@@
>   #define MEDIA_BUS_FMT_VYUY10_1X20             0x201b
>   #define MEDIA_BUS_FMT_YUYV10_1X20             0x200d
>   #define MEDIA_BUS_FMT_YVYU10_1X20             0x200e
>  +#define MEDIA_BUS_FMT_YUV8_1X24                       0x2025

The above line is correct.

>  +#define MEDIA_BUS_FMT_YUV10_1X30              0x2016
>  +#define MEDIA_BUS_FMT_AYUV8_1X32              0x2017
>  +#define MEDIA_BUS_FMT_UYVY12_2X12             0x201c
>  +#define MEDIA_BUS_FMT_VYUY12_2X12             0x201d
>  +#define MEDIA_BUS_FMT_YUYV12_2X12             0x201e
>  +#define MEDIA_BUS_FMT_YVYU12_2X12             0x201f

The above 6 lines introduce duplicate defines, you can remove them.

> + #define MEDIA_BUS_FMT_VUY8_1X24                       0x2024
>   #define MEDIA_BUS_FMT_UYVY12_1X24             0x2020
>   #define MEDIA_BUS_FMT_VYUY12_1X24             0x2021
>   #define MEDIA_BUS_FMT_YUYV12_1X24             0x2022

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2015-04-21  7:49 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21  1:54 linux-next: manual merge of the v4l-dvb tree with Linus' tree Stephen Rothwell
2015-04-21  7:49 ` Laurent Pinchart [this message]
2015-04-21  8:02   ` Stephen Rothwell
2015-04-21  9:56     ` Mauro Carvalho Chehab
2015-04-21 12:38       ` Laurent Pinchart
2015-04-21 13:12         ` Mauro Carvalho Chehab
2015-04-21 13:36           ` Philipp Zabel
  -- strict thread matches above, loose matches on Subject: below --
2025-08-26  1:39 Stephen Rothwell
2021-10-01  0:33 Stephen Rothwell
2021-10-01  6:46 ` Sean Young
2019-06-24  1:36 Stephen Rothwell
2019-06-06  0:43 Stephen Rothwell
2019-05-23 23:21 Stephen Rothwell
2019-01-31 23:22 Stephen Rothwell
2019-01-31 23:27 ` Stephen Rothwell
2016-08-04  1:02 Stephen Rothwell
2015-09-07 23:20 Stephen Rothwell
2015-04-21  1:50 Stephen Rothwell
2015-04-10  3:53 Stephen Rothwell
2014-01-14  0:50 Stephen Rothwell
2013-08-29  2:48 Stephen Rothwell
2012-10-02  1:13 Stephen Rothwell
2012-06-19  1:29 Stephen Rothwell
2012-06-19 10:06 ` Jiri Kosina
2012-06-19 11:50   ` Hans de Goede
2012-06-19 11:52     ` Jiri Kosina
2011-07-29  3:17 Stephen Rothwell
2011-07-29  4:10 ` Mauro Carvalho Chehab
2011-07-29  7:29   ` Stephen Rothwell
2011-04-08  3:27 Stephen Rothwell
2011-03-22  1:00 Stephen Rothwell
2010-07-06  2:01 Stephen Rothwell
2010-05-13  1:52 Stephen Rothwell
2010-05-10  0:36 Stephen Rothwell
2010-05-11 23:23 ` Mauro Carvalho Chehab
2010-05-12  0:23   ` Stephen Rothwell
2010-05-10  0:32 Stephen Rothwell
2010-05-11  5:19 ` Hiremath, Vaibhav
2010-05-10  0:29 Stephen Rothwell
2010-04-07  1:00 Stephen Rothwell
2010-04-09  5:22 ` Mauro Carvalho Chehab
2010-04-09  7:13   ` Stephen Rothwell
2009-09-02  2:17 Stephen Rothwell
2009-09-03  2:12 ` Mauro Carvalho Chehab
2009-09-03  6:49   ` Stephen Rothwell

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=5336539.Ny4ylH3Nve@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=airlied@redhat.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=hyun.kwon@xilinx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=p.zabel@pengutronix.de \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.