linux-kernel - Re: [PATCH v2 31/76] ARC: Build system: Makefiles, Kconfig, Linker script

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: <201301181925.36466.arnd@arndb.de>
Date:	Fri, 18 Jan 2013 19:25:36 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Vineet Gupta <Vineet.Gupta1@...opsys.com>,
	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 31/76] ARC: Build system: Makefiles, Kconfig, Linker script

On Friday 18 January 2013, Sam Ravnborg wrote:
> > +obj-y        := arcksyms.o setup.o irq.o time.o reset.o ptrace.o entry.o process.o \
> > +        signal.o traps.o sys.o troubleshoot.o stacktrace.o clk.o
> 
> For new stuff I usually recommend to drop line continuation using \
> 
> Just do the much prettier:
> obj-y := arcksyms.o setup.o irq.o time.o reset.o ptrace.o entry.o process.o
> obj-y += signal.o traps.o sys.o troubleshoot.o stacktrace.o clk.o

Agreed, although we are moving some files to the more verbose

obj-y += arcksyms.o
obj-y += clk.o
obj-y += entry.o
obj-y += ...

and use alphabetical order, both of which help avoid merge conflicts
when Makefile changes come in through separate branches. This 
particular Makefile is likely to remain rather stable though, so
it's not necessary to go this far.

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