linux-kernel - linux-next: build failure after merge of the v4l-dvb tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20200422104130.28d34c28@canb.auug.org.au>
Date:   Wed, 22 Apr 2020 10:41:30 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Mauro Carvalho Chehab <mchehab@...nel.org>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Dafna Hirschfeld <dafna.hirschfeld@...labora.com>,
        Helen Koike <helen.koike@...labora.com>,
        Hans Verkuil <hverkuil-cisco@...all.nl>
Subject: linux-next: build failure after merge of the v4l-dvb tree

Hi all,

After merging the v4l-dvb tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/staging/media/rkisp1/rkisp1-isp.c: In function 'rkisp1_config_isp':
drivers/staging/media/rkisp1/rkisp1-isp.c:294:14: error: 'struct rkisp1_sensor_async' has no member named 'mbus'
  294 |    if (sensor->mbus.type == V4L2_MBUS_BT656)
      |              ^~

Caused by commit

  4d0b43804c12 ("media: staging: rkisp1: remove mbus field from rkisp1_sensor_async")

I have used the v4l-dvb tree from next-20200421 for today.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped