From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Ezequiel Garcia <ezequiel@collabora.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pawel Osciak <posciak@chromium.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Tomasz Figa <tfiga@chromium.org>,
Boris Brezillon <boris.brezillon@collabora.com>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>
Subject: Re: linux-next: build failure after merge of the v4l-dvb tree
Date: Tue, 23 Jul 2019 12:52:30 -0300 [thread overview]
Message-ID: <20190723125230.1ca56edd@coco.lan> (raw)
In-Reply-To: <13b14eb9475de71b408d1eed3c5e69fe089deeb0.camel@collabora.com>
Em Tue, 23 Jul 2019 12:14:20 -0300
Ezequiel Garcia <ezequiel@collabora.com> escreveu:
> On Tue, 2019-07-23 at 10:13 +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the v4l-dvb tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > In file included from <command-line>:
> > include/media/vp8-ctrls.h:25:2: error: unknown type name '__s8'
> > __s8 quant_update[4];
> > ^~~~
> > include/media/vp8-ctrls.h:26:2: error: unknown type name '__s8'
> > __s8 lf_update[4];
> > ^~~~
> > include/media/vp8-ctrls.h:27:2: error: unknown type name '__u8'
> > __u8 segment_probs[3];
> > ^~~~
> > include/media/vp8-ctrls.h:28:2: error: unknown type name '__u8'
> > __u8 padding;
> > ^~~~
> > include/media/vp8-ctrls.h:29:2: error: unknown type name '__u32'
> > __u32 flags;
> > ^~~~~
> > include/media/vp8-ctrls.h:36:2: error: unknown type name '__s8'
> > __s8 ref_frm_delta[4];
> > ^~~~
> > include/media/vp8-ctrls.h:37:2: error: unknown type name '__s8'
> > __s8 mb_mode_delta[4];
> > ^~~~
> > include/media/vp8-ctrls.h:38:2: error: unknown type name '__u8'
> > __u8 sharpness_level;
> > ^~~~
> > include/media/vp8-ctrls.h:39:2: error: unknown type name '__u8'
> > __u8 level;
> > ^~~~
> > include/media/vp8-ctrls.h:40:2: error: unknown type name '__u16'
> > __u16 padding;
> > ^~~~~
> > include/media/vp8-ctrls.h:41:2: error: unknown type name '__u32'
> > __u32 flags;
> > ^~~~~
> > include/media/vp8-ctrls.h:45:2: error: unknown type name '__u8'
> > __u8 y_ac_qi;
> > ^~~~
> > include/media/vp8-ctrls.h:46:2: error: unknown type name '__s8'
> > __s8 y_dc_delta;
> > ^~~~
> > include/media/vp8-ctrls.h:47:2: error: unknown type name '__s8'
> > __s8 y2_dc_delta;
> > ^~~~
> > include/media/vp8-ctrls.h:48:2: error: unknown type name '__s8'
> > __s8 y2_ac_delta;
> > ^~~~
> > include/media/vp8-ctrls.h:49:2: error: unknown type name '__s8'
> > __s8 uv_dc_delta;
> > ^~~~
> > include/media/vp8-ctrls.h:50:2: error: unknown type name '__s8'
> > __s8 uv_ac_delta;
> > ^~~~
> > include/media/vp8-ctrls.h:51:2: error: unknown type name '__u16'
> > __u16 padding;
> > ^~~~~
> > include/media/vp8-ctrls.h:55:2: error: unknown type name '__u8'
> > __u8 coeff_probs[4][8][3][11];
> > ^~~~
> > include/media/vp8-ctrls.h:56:2: error: unknown type name '__u8'
> > __u8 y_mode_probs[4];
> > ^~~~
> > include/media/vp8-ctrls.h:57:2: error: unknown type name '__u8'
> > __u8 uv_mode_probs[3];
> > ^~~~
> > include/media/vp8-ctrls.h:58:2: error: unknown type name '__u8'
> > __u8 mv_probs[2][19];
> > ^~~~
> > include/media/vp8-ctrls.h:59:2: error: unknown type name '__u8'
> > __u8 padding[3];
> > ^~~~
> > include/media/vp8-ctrls.h:63:2: error: unknown type name '__u8'
> > __u8 range;
> > ^~~~
> > include/media/vp8-ctrls.h:64:2: error: unknown type name '__u8'
> > __u8 value;
> > ^~~~
> > include/media/vp8-ctrls.h:65:2: error: unknown type name '__u8'
> > __u8 bit_count;
> > ^~~~
> > include/media/vp8-ctrls.h:66:2: error: unknown type name '__u8'
> > __u8 padding;
> > ^~~~
> > include/media/vp8-ctrls.h:86:2: error: unknown type name '__u16'
> > __u16 width;
> > ^~~~~
> > include/media/vp8-ctrls.h:87:2: error: unknown type name '__u16'
> > __u16 height;
> > ^~~~~
> > include/media/vp8-ctrls.h:89:2: error: unknown type name '__u8'
> > __u8 horizontal_scale;
> > ^~~~
> > include/media/vp8-ctrls.h:90:2: error: unknown type name '__u8'
> > __u8 vertical_scale;
> > ^~~~
> > include/media/vp8-ctrls.h:92:2: error: unknown type name '__u8'
> > __u8 version;
> > ^~~~
> > include/media/vp8-ctrls.h:93:2: error: unknown type name '__u8'
> > __u8 prob_skip_false;
> > ^~~~
> > include/media/vp8-ctrls.h:94:2: error: unknown type name '__u8'
> > __u8 prob_intra;
> > ^~~~
> > include/media/vp8-ctrls.h:95:2: error: unknown type name '__u8'
> > __u8 prob_last;
> > ^~~~
> > include/media/vp8-ctrls.h:96:2: error: unknown type name '__u8'
> > __u8 prob_gf;
> > ^~~~
> > include/media/vp8-ctrls.h:97:2: error: unknown type name '__u8'
> > __u8 num_dct_parts;
> > ^~~~
> > include/media/vp8-ctrls.h:99:2: error: unknown type name '__u32'
> > __u32 first_part_size;
> > ^~~~~
> > include/media/vp8-ctrls.h:100:2: error: unknown type name '__u32'
> > __u32 first_part_header_bits;
> > ^~~~~
> > include/media/vp8-ctrls.h:101:2: error: unknown type name '__u32'
> > __u32 dct_part_sizes[8];
> > ^~~~~
> > include/media/vp8-ctrls.h:103:2: error: unknown type name '__u64'
> > __u64 last_frame_ts;
> > ^~~~~
> > include/media/vp8-ctrls.h:104:2: error: unknown type name '__u64'
> > __u64 golden_frame_ts;
> > ^~~~~
> > include/media/vp8-ctrls.h:105:2: error: unknown type name '__u64'
> > __u64 alt_frame_ts;
> > ^~~~~
> > include/media/vp8-ctrls.h:107:2: error: unknown type name '__u64'
> > __u64 flags;
> > ^~~~~
> >
> > Caused by commit
> >
> > a57d6acaf352 ("media: uapi: Add VP8 stateless decoder API")
> >
> > I have added the following fix patch for today.
> >
>
> Looks good, thanks for the fix. I wonder why this
> got triggered with VP8 only, and not with MPEG-2.
I suspect that this got triggered by some change at linux-next, as
it built fine here on the top of 5.3-rc1.
Patch was applied earlier today.
Thanks,
Mauro
next prev parent reply other threads:[~2019-07-23 15:52 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 0:13 linux-next: build failure after merge of the v4l-dvb tree Stephen Rothwell
2019-07-23 15:14 ` Ezequiel Garcia
2019-07-23 15:52 ` Mauro Carvalho Chehab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-10 1:46 Stephen Rothwell
2020-09-14 6:24 Stephen Rothwell
2020-09-08 2:11 Stephen Rothwell
2020-04-22 0:41 Stephen Rothwell
2020-04-16 8:27 Stephen Rothwell
2020-03-13 2:19 Stephen Rothwell
2020-03-13 6:48 ` Marco Felsch
2020-03-13 7:05 ` Mauro Carvalho Chehab
2020-03-13 7:14 ` Marco Felsch
2020-03-13 7:07 ` Mauro Carvalho Chehab
2020-03-13 10:29 ` Stephen Rothwell
2020-03-16 6:50 ` Mauro Carvalho Chehab
2019-02-18 23:52 Stephen Rothwell
2018-07-27 1:49 Stephen Rothwell
2017-06-21 1:25 Stephen Rothwell
2017-06-21 8:54 ` Stanimir Varbanov
2017-01-31 0:55 Stephen Rothwell
2017-02-02 22:24 ` Stephen Rothwell
2017-02-02 22:46 ` Mauro Carvalho Chehab
2017-02-02 22:59 ` Stephen Rothwell
2017-02-02 23:24 ` Mauro Carvalho Chehab
2017-02-03 0:01 ` Stephen Rothwell
2017-02-03 0:24 ` Mauro Carvalho Chehab
2017-02-05 22:19 ` Stephen Rothwell
2017-02-05 22:22 ` Mauro Carvalho Chehab
2016-09-12 5:10 Stephen Rothwell
2016-09-12 6:33 ` Hans Verkuil
2015-08-12 3:24 Stephen Rothwell
2015-06-19 4:47 Michael Ellerman
2015-04-10 10:11 Stephen Rothwell
2015-04-10 12:45 ` Laurent Pinchart
2015-04-10 12:57 ` Stephen Rothwell
2015-04-13 3:05 ` Stephen Rothwell
2015-04-13 8:02 ` Laurent Pinchart
2014-09-09 2:43 Stephen Rothwell
2014-09-09 3:05 ` Mauro Carvalho Chehab
2014-09-17 3:47 ` Stephen Rothwell
2014-07-25 2:23 Stephen Rothwell
[not found] ` <9f4bd671-cbe0-4e11-997e-e369c52589f9@email.android.com>
2014-07-25 21:50 ` Mauro Carvalho Chehab
2014-07-15 3:29 Stephen Rothwell
2014-07-15 5:43 ` Guenter Roeck
2014-07-15 5:55 ` Stephen Rothwell
2014-07-15 9:01 ` Guenter Roeck
2014-07-15 18:08 ` Mauro Carvalho Chehab
2014-07-15 19:08 ` Guenter Roeck
2014-07-16 3:04 ` Stephen Rothwell
2014-07-16 4:29 ` Guenter Roeck
2014-07-16 13:21 ` Ingo Molnar
2014-07-16 13:22 ` Stephen Rothwell
2014-07-16 13:24 ` Ingo Molnar
2014-03-31 2:01 Stephen Rothwell
2014-03-31 10:26 ` Mauro Carvalho Chehab
2013-01-11 0:39 Stephen Rothwell
2013-01-11 15:12 ` Mauro Carvalho Chehab
2012-11-26 2:31 Stephen Rothwell
2012-11-26 12:10 ` Mauro Carvalho Chehab
2012-11-26 13:44 ` Marek Szyprowski
2012-11-12 0:09 Stephen Rothwell
2012-11-13 13:14 ` Mauro Carvalho Chehab
2012-11-07 0:05 Stephen Rothwell
2012-11-07 1:12 ` Mauro Carvalho Chehab
2012-10-29 0:14 Stephen Rothwell
2012-10-29 8:09 ` David Härdeman
2012-10-29 8:43 ` Jiri Kosina
2012-10-29 9:52 ` Mauro Carvalho Chehab
2012-11-05 0:34 ` Stephen Rothwell
2012-11-06 1:26 ` Mauro Carvalho Chehab
2012-08-17 1:10 Stephen Rothwell
2012-08-17 1:46 ` Mauro Carvalho Chehab
2012-07-09 1:50 Stephen Rothwell
2012-04-11 2:10 Stephen Rothwell
2012-04-11 7:32 ` Srinivas KANDAGATLA
2012-04-17 3:25 ` Stephen Rothwell
2011-09-26 4:02 Stephen Rothwell
2011-09-22 3:12 Stephen Rothwell
2011-09-22 12:46 ` Mauro Carvalho Chehab
2011-09-22 20:19 ` Greg KH
2011-09-23 14:27 ` Mauro Carvalho Chehab
2011-09-27 0:49 ` Greg KH
2011-07-04 3:08 Stephen Rothwell
2011-07-04 3:04 Stephen Rothwell
2011-07-05 12:43 ` Jonathan Corbet
2011-03-22 1:14 Stephen Rothwell
2011-03-22 7:54 ` Mauro Carvalho Chehab
2011-02-28 1:05 Stephen Rothwell
2011-02-28 7:28 ` Hans Verkuil
2011-03-01 11:21 ` Mauro Carvalho Chehab
2011-03-03 1:37 ` Stephen Rothwell
2010-11-14 23:25 Stephen Rothwell
2010-11-22 0:43 ` Stephen Rothwell
2010-11-22 12:08 ` Mauro Carvalho Chehab
2010-10-01 1:41 Stephen Rothwell
2010-09-29 1:29 Stephen Rothwell
2010-09-29 1:40 ` Mauro Carvalho Chehab
2010-09-30 3:44 ` Mauro Carvalho Chehab
2010-05-20 1:45 Stephen Rothwell
2010-05-20 1:51 ` Mauro Carvalho Chehab
2010-04-12 2:40 Stephen Rothwell
2010-04-28 1:07 ` Stephen Rothwell
2010-05-03 5:01 ` Stephen Rothwell
2010-05-03 7:58 ` Mauro Carvalho Chehab
2010-05-03 10:25 ` Stephen Rothwell
2010-02-05 5:52 Stephen Rothwell
2010-02-05 15:02 ` 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=20190723125230.1ca56edd@coco.lan \
--to=mchehab@kernel.org \
--cc=boris.brezillon@collabora.com \
--cc=ezequiel@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=posciak@chromium.org \
--cc=sfr@canb.auug.org.au \
--cc=tfiga@chromium.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 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.