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: <20140430161358.GB15320@ravnborg.org>
Date:	Wed, 30 Apr 2014 18:13:59 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Michal Marek <mmarek@...e.cz>
Cc:	linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] kbuild: Use relative paths if possible

On Tue, Apr 29, 2014 at 04:08:08PM +0200, Michal Marek wrote:
> Hi,
> 
> This series changes the Makefile to use relative paths for $(objtree),
> always setting it to '.', and for $(srctree) setting either to '.' or
> '..', when building in the source tree or a subdirectory thereof,
> respectively. The goal is to make compiler messages and Ooopses more
> readable by avoiding the full path to the source/object directory.
> 
> Patch 2/5 is just an unrelated cleanup.
> 
> Michal
> 
> Michal Marek (5):
>   firmware: Simplify directory creation
>   firmware: Use $(quote) in the Makefile
>   kbuild: Use relative path for $(objtree)
>   kbuild: Use relative path when building in the source tree
>   kbuild: Use relative path when building in a subdir of the source tree

For patch 2,3,4 and 5 you can add my:
Acked-by: Sam Ravnborg <sam@...nborg.org>

Patch 1 also looks good, but I did not fully grasp it and this is MO
implied by an ack. So please do not hold it back due to this as
the cleanup looked good.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ