linux-kernel - Re: linux-next: Tree for Aug 18 (drivers/media/i2c/tc358743.c)

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <55D34EA5.1010705@infradead.org>
Date:	Tue, 18 Aug 2015 08:26:29 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>, linux-next@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org,
	linux-media <linux-media@...r.kernel.org>,
	Ramakrishnan Muthukrishnan <ram@...ishnan.org>,
	Mikhail Khelik <mkhelik@...co.com>,
	Mats Randgaard <matrandg@...co.com>
Subject: Re: linux-next: Tree for Aug 18 (drivers/media/i2c/tc358743.c)

On 08/18/15 04:40, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20150817:
> 

on i386:

when CONFIG_MEDIA_CONTROLLER is not enabled:

../drivers/media/i2c/tc358743.c: In function 'tc358743_probe':
../drivers/media/i2c/tc358743.c:1890:29: error: 'struct v4l2_subdev' has no member named 'entity'
  err = media_entity_init(&sd->entity, 1, &state->pad, 0);
                             ^
../drivers/media/i2c/tc358743.c:1940:26: error: 'struct v4l2_subdev' has no member named 'entity'
  media_entity_cleanup(&sd->entity);
                          ^
../drivers/media/i2c/tc358743.c: In function 'tc358743_remove':
../drivers/media/i2c/tc358743.c:1955:26: error: 'struct v4l2_subdev' has no member named 'entity'
  media_entity_cleanup(&sd->entity);
                          ^



-- 
~Randy
--
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/