linux-kernel - Re: [PATCH] arc: kernel: add default extern variable 'screen

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]

Date:	Sat, 26 Oct 2013 10:11:07 +0800
From:	Chen Gang <gang.chen@...anux.com>
To:	Vineet Gupta <Vineet.Gupta1@...opsys.com>
CC:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Arnd Bergmann <arnd@...db.de>,
	"sachin.kamat@...aro.org" <sachin.kamat@...aro.org>,
	Paul Gortmaker <paul.gortmaker@...driver.com>,
	James Hogan <james.hogan@...tec.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Will Deacon <will.deacon@....com>,
	Catalin Marinas <Catalin.Marinas@....com>
Subject: Re: [PATCH] arc: kernel: add default extern variable 'screen_info'
 in "setup.c"

On 10/24/2013 07:50 PM, Vineet Gupta wrote:
> On 10/24/2013 04:56 PM, Chen Gang wrote:
>> If what you said is correct, could you help to send related patch for
>> it? if I send this kind of patches, it will be easily redirected to
>> "/dev/null".
> 
> Geert has explained the state of things quite nicely. Please send your patch to
> introduce HAVE_xxx. I'm sure maintainers will respond to it as it is the correct
> thing to do. But I don't want to add bloat to kernel for a random defconfig
> failure which no one will really use for ARC.
> 
> If you think u can't/won't do it - let me know and I'll send the patches instead.
> 

Please help send.

Thanks. :-)

> -Vineet
> 
> 


-- 
Chen Gang
--
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/