From: Arnd Bergmann <arnd@arndb.de>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: Michal Marek <mmarek@suse.com>,
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: Thu, 20 Oct 2016 10:03:14 +0200 [thread overview]
Message-ID: <16513464.3RM484EDf1@wuerfel> (raw)
In-Reply-To: <20161020145827.453025a6@roar.ozlabs.ibm.com>
On Thursday, October 20, 2016 2:58:27 PM CEST Nicholas Piggin wrote:
>
> Yeah, I had the same idea as you and Michal too. It's conceptually nicer,
> but in practice it turned into a mess. If some architectures wanted to start
> protecting their .h files and including them into .S for the prototypes, we
> could start parsing those too. Should we do the quick and dirty way for 4.9?
Let's stay with your approach for now.
Arnd
next prev parent reply other threads:[~2016-10-20 8:03 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 [this message]
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
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=16513464.3RM484EDf1@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.com \
--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).