[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170329103507.j6wcjt4wkd7q2ynb@hirez.programming.kicks-ass.net>
Date: Wed, 29 Mar 2017 12:35:07 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Davidlohr Bueso <dave@...olabs.net>
Cc: mingo@...nel.org, akpm@...ux-foundation.org, jack@...e.cz,
kirill.shutemov@...ux.intel.com, mhocko@...e.com,
mgorman@...hsingularity.net, linux-kernel@...r.kernel.org,
Davidlohr Bueso <dbueso@...e.de>
Subject: Re: [PATCH 1/5] locking: Introduce range reader/writer lock
On Mon, Mar 06, 2017 at 09:03:26PM -0800, Davidlohr Bueso wrote:
> +EXPORT_SYMBOL(range_rwlock_init);
> +EXPORT_SYMBOL(range_rwlock_init_inf);
> +EXPORT_SYMBOL(range_read_lock);
> +EXPORT_SYMBOL(range_read_lock_interruptible);
> +EXPORT_SYMBOL(range_read_lock_killable);
> +EXPORT_SYMBOL(range_read_trylock);
> +EXPORT_SYMBOL(range_read_unlock);
> +EXPORT_SYMBOL(range_write_lock);
> +EXPORT_SYMBOL(range_write_lock_interruptible);
> +EXPORT_SYMBOL(range_write_lock_killable);
> +EXPORT_SYMBOL(range_write_trylock);
> +EXPORT_SYMBOL(range_write_unlock);
> +EXPORT_SYMBOL(range_downgrade_write);
Is there a good reason this isn't _GPL ?
Powered by blists - more mailing lists