linux-kernel - Re: [PATCH 10/17] ARM: at91: merge SOC

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

Message-ID: <20150122163605.GC19922@piout.net>
Date:	Thu, 22 Jan 2015 17:36:05 +0100
From:	Alexandre Belloni <alexandre.belloni@...e-electrons.com>
To:	Nicolas Ferre <nicolas.ferre@...el.com>
Cc:	Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>,
	Arnd Bergmann <arnd@...db.de>,
	Boris Brezillon <boris.brezillon@...e-electrons.com>,
	Bo Shen <voice.shen@...el.com>,
	Wenyou Yang <Wenyou.Yang@...el.com>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 10/17] ARM: at91: merge SOC_AT91SAM9xxx

On 22/01/2015 at 11:22:21 +0100, Nicolas Ferre wrote :
> Le 15/01/2015 22:58, Alexandre Belloni a écrit :
> > Only use SOC_AT91SAM9 for all the at91sam9 SoCs.
> > 
> > It enables HAVE_AT91_SMD and HAVE_AT91_UTMI for all the sam9 SoCs but this only
> > represents 96 bytes of uncompressed kernel code.
> 
> After this patch that removes all the CONFIG_SOC_AT91SAM9xxxx options
> excepted CONFIG_SOC_AT91SAM9, I still see a lot of them remaining in the
> source tree.
> 
> So, this patch is not complete in my opinion. Even if you remove these
> options later on, why not suppress them here?
> 

They went through other branches (you were in copy).


-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
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/