Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 9 Nov 2021 20:00:09 +0100
From:   Peter Zijlstra <peterz@infradead.org>
To:     Ard Biesheuvel <ardb@kernel.org>
Cc:     linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        Josh Poimboeuf <jpoimboe@redhat.com>,
        Jason Baron <jbaron@akamai.com>,
        Steven Rostedt <rostedt@goodmis.org>,
        Mark Rutland <mark.rutland@arm.com>,
        Kees Cook <keescook@chromium.org>
Subject: Re: [RFC PATCH 6/7] static_call: rename EXPORT_ macros to be more
 self-explanatory
Message-ID: <YYrFOZT+6bNTfP+t@hirez.programming.kicks-ass.net>
References: <20211109164549.1724710-1-ardb@kernel.org>
 <20211109164549.1724710-7-ardb@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20211109164549.1724710-7-ardb@kernel.org>
Precedence: bulk

On Tue, Nov 09, 2021 at 05:45:48PM +0100, Ard Biesheuvel wrote:
> So let's rename these macros to
> 
>   EXPORT_STATIC_CALL        -> EXPORT_STATIC_CALL_FOR_UPDATE
>   EXPORT_STATIC_CALL_TRAMP  -> EXPORT_STATIC_CALL
> 

Ok, let's pain this shed a bit.

How about:

	EXPORT_STATIC_CALL_RW
	EXPORT_STATIC_CALL_RO

respectively. OR.. alternatively, have both:

	EXPORT_STATIC_CALL_KEY
	EXPORT_STATIC_CALL_TRAMP

and those that want to export both get to use both.