linux-kernel - Re: ARC: ARC_BOARD_ANGEL4 and ARC_BOARD

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:	Mon, 22 Sep 2014 05:16:54 +0000
From:	Vineet Gupta <Vineet.Gupta1@...opsys.com>
To:	Paul Bolle <pebolle@...cali.nl>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: ARC:  ARC_BOARD_ANGEL4 and ARC_BOARD_ML509

On Friday 12 September 2014 02:30 PM, Paul Bolle wrote:
> Hi Vineet,
>
> On Mon, 2014-06-09 at 09:05 +0000, Vineet Gupta wrote:
>> On Wednesday 04 June 2014 03:04 PM, Paul Bolle wrote:
>>> Linux-next included commit c00bfd974fb0 ("ARC: [arcfpga] Get rid of
>>> legacy BVCI latency unit support") in next-20140604. It removes the
>>> Kconfig symbol ARC_HAS_BVCI_LAT_UNIT. And that symbol's entry is the
>>> only place were the symbols ARC_BOARD_ANGEL4 and ARC_BOARD_ML509 are
>>> currently used. So it follows that the entries for ARC_BOARD_ANGEL4 and
>>> ARC_BOARD_ML509 could be removed too.
>> Thx for noticing this.
>>
>> I'm planning to use these symbols to set up default builtin DT blobs from Kconfig
>> itself (rather than current defconfigs). If that doesn't workout - sure I will
>> remove the symbols.
> No news here as of v3.17-rc4 and next-20140912. Are you still planning
> to use these symbols or should I submit the trivial patch to drop them?

Please send over patch - I'll queue it up for 3.18

Thx,
-Vineet

>
> Thanks,
>
>
> Paul Bolle
>
>

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