linux-kernel - Re: [Intel-gfx] [PATCH] lib: Export interval

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANN689GDsXunNZAkkv7=CS2ct5m2WNqEODrn2jrvmd99jWDCAw@mail.gmail.com>
Date:	Sun, 26 Jan 2014 06:03:38 -0800
From:	Michel Lespinasse <walken@...gle.com>
To:	Chris Wilson <chris@...is-wilson.co.uk>,
	intel-gfx@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
	Andrea Arcangeli <aarcange@...hat.com>,
	Rik van Riel <riel@...hat.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Michel Lespinasse <walken@...gle.com>
Subject: Re: [Intel-gfx] [PATCH] lib: Export interval_tree

On Sun, Jan 26, 2014 at 5:54 AM, Daniel Vetter <daniel@...ll.ch> wrote:
> On Sun, Jan 26, 2014 at 12:24:33PM +0000, Chris Wilson wrote:
>>  INTERVAL_TREE_DEFINE(struct interval_tree_node, rb,
>>                    unsigned long, __subtree_last,
>>                    START, LAST,, interval_tree)
>> +
>> +EXPORT_SYMBOL(interval_tree_insert);
>> +EXPORT_SYMBOL(interval_tree_remove);
>> +EXPORT_SYMBOL(interval_tree_iter_first);
>> +EXPORT_SYMBOL(interval_tree_iter_next);
>
> Hm, I've thought kernel coding style nowadays is to put the EXPORT_SYMBOL
> right below the definition of the function?

INTERVAL_TREE_DEFINE generates the definitions of these functions.

-- 
Michel "Walken" Lespinasse
A program is never fully debugged until the last user dies.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/