From: Michal Marek <mmarek@suse.cz>
To: Geoff Levand <geoff@infradead.org>
Cc: linux-kbuild@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: [PATCH 3/3] mn10300: Remove redundent debugging info flag
Date: Mon, 27 Jan 2014 22:08:39 +0100 [thread overview]
Message-ID: <52E6CAD7.2020208@suse.cz> (raw)
In-Reply-To: <e9d530c5b8b1c9a8510d9c8db8663aedc393de8f.1386804405.git.geoff@infradead.org>
Dne 12.12.2013 00:34, Geoff Levand napsal(a):
> The gereric makefile now sets '-Wa,--gdwarf2' in KBUILD_AFLAGS, so
> this setting is no longer needed in arch makefiles.
>
> Cc: David Howells <dhowells@redhat.com>
> Signed-off-by: Geoff Levand <geoff@infradead.org> for Huawei, Linaro
> ---
> arch/mn10300/Makefile | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/mn10300/Makefile b/arch/mn10300/Makefile
> index a3d0fef..f5a9db9 100644
> --- a/arch/mn10300/Makefile
> +++ b/arch/mn10300/Makefile
> @@ -97,7 +97,6 @@ endef
> # that are unhelpful whilst debugging.
> ifdef CONFIG_DEBUG_INFO
> #KBUILD_CFLAGS += -O1
> -KBUILD_AFLAGS += -Wa,--gdwarf2
> endif
This leaves only a commented-out assignment in the ifdef block. Just
remove it completely together with the outdated comment above. Same for
the frv Makefile.
Michal
next prev parent reply other threads:[~2014-01-27 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 23:34 [PATCH 0/3] Fix debugging info for .S files Geoff Levand
2013-12-11 23:34 ` [PATCH 1/3] kbuild: Fix debugging info generation " Geoff Levand
2014-01-27 21:03 ` Michal Marek
2013-12-11 23:34 ` [PATCH 2/3] frv: Remove redundent debugging info flag Geoff Levand
2014-01-28 1:48 ` [PATCH V2 2/3] frv: Remove redundant " Geoff Levand
2014-01-28 10:16 ` Michal Marek
2013-12-11 23:34 ` [PATCH 3/3] mn10300: Remove redundent " Geoff Levand
2014-01-27 21:08 ` Michal Marek [this message]
2014-01-28 1:48 ` [PATCH V2 3/3] mn10300: Remove redundant " Geoff Levand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52E6CAD7.2020208@suse.cz \
--to=mmarek@suse.cz \
--cc=dhowells@redhat.com \
--cc=geoff@infradead.org \
--cc=linux-kbuild@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.