From: nicolas.pitre@linaro.org (Nicolas Pitre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] fix modversion for symbol exported from asm code
Date: Wed, 30 Nov 2016 03:50:21 -0500 [thread overview]
Message-ID: <1480495824-4151-1-git-send-email-nicolas.pitre@linaro.org> (raw)
This is my alternative to asm-prototypes.h for fixing modversion with
assembly symbols. This preserves the goal of not having a central list
of symbols that may get out of sync wrt the actual code.
An example usage is provided for ARM.
The asm-prototypes.h method is still available for those who might
prefer it.
Given that modversion is currently broken, I'd advocate for the first
2 patches to go into mainline now even if v4.9 is imminent. That can't
make things any worse than they are, and with this in place people may
start fixing their own architecture.
next reply other threads:[~2016-11-30 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 8:50 Nicolas Pitre [this message]
2016-11-30 8:50 ` [PATCH 1/3] kbuild: improve EXPORT_SYMBOL() parsing from asm code Nicolas Pitre
2016-11-30 8:50 ` [PATCH 2/3] kbuild: make modversion for exported asm symbols more convivial Nicolas Pitre
2016-11-30 8:50 ` [PATCH 3/3] ARM: fix asm symbol exports Nicolas Pitre
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=1480495824-4151-1-git-send-email-nicolas.pitre@linaro.org \
--to=nicolas.pitre@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).