linux-kernel - RE: blackfin: Kconfig symbol VIDEO

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] [day] [month] [year] [list]

Date:	Thu, 13 Feb 2014 10:01:50 +0000
From:	"Zhang, Sonic" <Sonic.Zhang@...log.com>
To:	Paul Bolle <pebolle@...cali.nl>, Steven Miao <realmz6@...il.com>
CC:	Richard Weinberger <richard@....at>,
	"adi-buildroot-devel@...ts.sourceforge.net" 
	<adi-buildroot-devel@...ts.sourceforge.net>,
	"open list:CAN NETWORK DRIVERS <linux-can@...r.kernel.org>, open 
	list:NETWORKING DRIVERS <netdev@...r.kernel.org>, open list" 
	<linux-kernel@...r.kernel.org>
Subject: RE: blackfin: Kconfig symbol VIDEO_MT9M114?

Hi Paul,

I will send out a patch to remove it.

Regards,

Sonic

>-----Original Message-----
>From: Paul Bolle [mailto:pebolle@...cali.nl]
>Sent: Thursday, February 13, 2014 5:30 PM
>To: Steven Miao
>Cc: Zhang, Sonic; Richard Weinberger; adi-buildroot-devel@...ts.sourceforge.net;
>open list:CAN NETWORK DRIVERS <linux-can@...r.kernel.org>, open
>list:NETWORKING DRIVERS <netdev@...r.kernel.org>, open list
>Subject: Re: blackfin: Kconfig symbol VIDEO_MT9M114?
>
>Hi Steven,
>
>On Thu, 2014-02-13 at 17:00 +0800, Steven Miao wrote:
>> VIDEO_MT9M114 is from patch "Aptina mt9m114 HD digital image sensor
>> driver", but unfortunately this patch hasn't been accepted yet.
>> https://patchwork.linuxtv.org/patch/16308/
>> This Kconfig symbol should be removed until the mt9m114 driver is
>> accepted by mainline.
>
>Thanks for looking into this.
>
>It's easy for me to submit a trivial patch to remove the one line depending on these
>Kconfig macros. But it seems that line should be added to the queue for that driver at
>the same time, otherwise we risk losing it. So it's safer if you or the people working on
>that driver coordinate that, isn't it?
>
>
>Paul Bolle
>