From: Geoff Levand <geoff@infradead.org>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: [PATCH 0/3] Fix debugging info for .S files
Date: Wed, 11 Dec 2013 23:34:40 +0000 [thread overview]
Message-ID: <cover.1386804405.git.geoff@infradead.org> (raw)
Hi Michal,
Here are a few small patches to fixup debug info gereration for .S files. I
tested the generated vmlinux with the ARM Fast Model debugger and ARM64 target.
Please apply.
-Geoff
The following changes since commit 374b105797c3d4f29c685f3be535c35f5689b30e:
Linux 3.13-rc3 (2013-12-06 09:34:04 -0800)
are available in the git repository at:
git://git.linaro.org/people/geoff.levand/linux-kexec.git for-kbuild
for you to fetch changes up to e9d530c5b8b1c9a8510d9c8db8663aedc393de8f:
mn10300: Remove redundent debugging info flag (2013-12-11 15:15:00 -0800)
----------------------------------------------------------------
Geoff Levand (3):
kbuild: Fix debugging info generation for .S files
frv: Remove redundent debugging info flag
mn10300: Remove redundent debugging info flag
Makefile | 2 +-
arch/frv/Makefile | 1 -
arch/mn10300/Makefile | 1 -
3 files changed, 1 insertion(+), 3 deletions(-)
--
1.8.1.2
next reply other threads:[~2013-12-11 23:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 23:34 Geoff Levand [this message]
2013-12-11 23:34 ` [PATCH 1/3] kbuild: Fix debugging info generation for .S files 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
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=cover.1386804405.git.geoff@infradead.org \
--to=geoff@infradead.org \
--cc=dhowells@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
/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.