[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <56FC3EDA.5030701@siemens.com>
Date: Wed, 30 Mar 2016 23:02:18 +0200
From: Jan Kiszka <jan.kiszka@...mens.com>
To: Kieran Bingham <kieran.bingham@...aro.org>,
linux-kernel@...r.kernel.org
Cc: lee.jones@...aro.org, peter.griffin@...aro.org,
maxime.coquelin@...com, mmarek@...e.com,
linux-kbuild@...r.kernel.org
Subject: Re: [PATCHv4 01/12] scripts/gdb: Provide linux constants
On 2016-03-30 14:00, Kieran Bingham wrote:
> Some macro's and defines are needed when parsing memory, and without
> compiling the kernel as -g3 they are not available in the debug-symbols.
>
> We use the pre-processor here to extract constants to a dedicated module
> for the linux debugger extensions
>
> Top level Kbuild is used to call in and generate the constants file,
> while maintaining dependencies on autogenerated files in
> include/generated
>
> CC: mmarek@...e.com
> CC: linux-kbuild@...r.kernel.org
>
> Signed-off-by: Kieran Bingham <kieran.bingham@...aro.org>
> ---
> Changes since v1:
>
> Kbuild:
> - Call to generate constants_py with dependancy on generated files
>
> scripts/gdb/linux/Makefile:
> - Use call if_changed, and correct quiet invocation
> - Annouce "GEN $@" instead of GDB PP
>
> scripts/gdb/linux/constants.py.in:
> - Updated to use better macro implementations for one line defines
> ---
Please only use a single separator line (i.e. remove this one), or the
history blob above makes it into the commit log. But there is no need to
resend if that will remain the only remark.
Jan
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
Powered by blists - more mailing lists