From: Michal Marek <mmarek@suse.com>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-kbuild@vger.kernel.org, linux-arch@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 2/2] kbuild: modversions for exported asm symbols
Date: Tue, 1 Nov 2016 15:44:17 +0100 [thread overview]
Message-ID: <195f928c-3d69-1c05-fe82-85e445f7d48c@suse.com> (raw)
In-Reply-To: <20161102013633.5b437f36@roar.ozlabs.ibm.com>
On 2016-11-01 15:36, Nicholas Piggin wrote:
> On Tue, 1 Nov 2016 15:19:59 +0100
> Michal Marek <mmarek@suse.com> wrote:
>
>> On 2016-10-31 12:14, Nicholas Piggin wrote:
>>> +# This is convoluted. The .S file must first be preprocessed to run guards and
>>> +# expand names, then the resulting exports must be constructed into plain
>>> +# EXPORT_SYMBOL(symbol); to build our dummy C file, and that gets preprocessed
>>> +# to make the genksyms input.
>>> #
>>> # These mirror gensymtypes_c and co above, keep them in synch.
>>> cmd_gensymtypes_S = \
>>> (echo "\#include <linux/kernel.h>" ; \
>>> echo "\#include <asm/asm-prototypes.h>" ; \
>>> - grep EXPORT_SYMBOL $< | sed 's/$$/;/' ) | \
>>> + $(CPP) $(a_flags) $< | \
>>> + grep ^___EXPORT_SYMBOL | \
>>> + sed 's/___EXPORT_SYMBOL \([a-zA-Z0-9_]*\),.*/EXPORT_SYMBOL(\1);/' ) | \
>>
>> Is this sed pass necessary? Just add -D__GENKSYMS__ also to the first
>> cpp run and EXPORT_SYMBOL will stay intact.
>
> I can't see how it would work if asm-generic/export.h doesn't have any
> tests for GENKSYMS.
You are right, these would have to be added first to mimic the
<linux/export.h> behavior.
Michal
next prev parent reply other threads:[~2016-11-01 14:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-15 12:43 [PATCH 0/2] kbuild: CRC versions for asm functions Nicholas Piggin
2016-10-15 12:43 ` [PATCH 1/2] kbuild: modpost warn if export version crc is missing Nicholas Piggin
2016-10-15 12:43 ` Nicholas Piggin
2016-10-15 12:43 ` [PATCH 2/2] kbuild: modversions for exported asm symbols Nicholas Piggin
2016-10-15 12:43 ` Nicholas Piggin
2016-10-19 14:50 ` Michal Marek
2016-10-19 14:59 ` Arnd Bergmann
2016-10-20 3:58 ` Nicholas Piggin
2016-10-20 8:03 ` Arnd Bergmann
2016-10-20 8:03 ` Arnd Bergmann
2016-10-22 15:36 ` Michal Marek
2016-10-22 15:36 ` Michal Marek
2016-10-31 11:14 ` Nicholas Piggin
2016-11-01 14:19 ` Michal Marek
2016-11-01 14:19 ` Michal Marek
2016-11-01 14:21 ` Michal Marek
2016-11-01 14:36 ` Nicholas Piggin
2016-11-01 14:36 ` Nicholas Piggin
2016-11-01 14:44 ` Michal Marek [this message]
2016-11-01 14:44 ` Michal Marek
2016-11-01 15:50 ` Michal Marek
2016-11-01 15:50 ` Michal Marek
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=195f928c-3d69-1c05-fe82-85e445f7d48c@suse.com \
--to=mmarek@suse.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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).