<feed xmlns='http://www.w3.org/2005/Atom'>
<title>user/sven/linux.git/include/linux/kernelcapi.h, branch v3.15.3</title>
<subtitle>Linux Kernel
</subtitle>
<id>https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v3.15.3</id>
<link rel='self' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v3.15.3'/>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/'/>
<updated>2012-10-13T09:46:48Z</updated>
<entry>
<title>UAPI: (Scripted) Disintegrate include/linux</title>
<updated>2012-10-13T09:46:48Z</updated>
<author>
<name>David Howells</name>
<email>dhowells@redhat.com</email>
</author>
<published>2012-10-13T09:46:48Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=607ca46e97a1b6594b29647d98a32d545c24bdff'/>
<id>urn:sha1:607ca46e97a1b6594b29647d98a32d545c24bdff</id>
<content type='text'>
Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;
Acked-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Acked-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Acked-by: Michael Kerrisk &lt;mtk.manpages@gmail.com&gt;
Acked-by: Paul E. McKenney &lt;paulmck@linux.vnet.ibm.com&gt;
Acked-by: Dave Jones &lt;davej@redhat.com&gt;
</content>
</entry>
<entry>
<title>CAPI: Rework controller state notifier</title>
<updated>2010-02-17T00:01:21Z</updated>
<author>
<name>Jan Kiszka</name>
<email>jan.kiszka@web.de</email>
</author>
<published>2010-02-08T10:12:13Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=ef69bb2ec6036945da1d3d3f07b75253f484f693'/>
<id>urn:sha1:ef69bb2ec6036945da1d3d3f07b75253f484f693</id>
<content type='text'>
Another step towards proper locking: Rework the callback provided to
capidrv for controller state changes. This is so far attached to an
application, which would require us to hold the corresponding lock
across notification calls.

But there is no direct relation between a controller up/down event and
an application, so let's decouple them and provide a notifier call chain
for those events instead. This notifier chain is first of all used
internally. Here we request the highest priority to unsure that
housekeeping work is done before any other notifications. The chain is
exported via [un]register_capictr_notifier to our only user, capidrv, to
replace the racy and unfixable capi20_set_callback.

Signed-off-by: Jan Kiszka &lt;jan.kiszka@web.de&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>include: Remove unnecessary inclusions of asm/semaphore.h</title>
<updated>2008-04-19T02:16:54Z</updated>
<author>
<name>Matthew Wilcox</name>
<email>matthew@wil.cx</email>
</author>
<published>2008-02-26T15:00:17Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=5a6483feb0c5193519625d0ea8c4254364d423cc'/>
<id>urn:sha1:5a6483feb0c5193519625d0ea8c4254364d423cc</id>
<content type='text'>
None of these files use any of the functionality promised by
asm/semaphore.h.  It's possible that they (or some user of them) rely
on it dragging in some unrelated header file, but I can't build all
these files, so we'll have to fix any build failures as they come up.

Signed-off-by: Matthew Wilcox &lt;willy@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Use mutex instead of semaphore in CAPI 2.0 driver</title>
<updated>2007-07-17T17:23:05Z</updated>
<author>
<name>Matthias Kaehlcke</name>
<email>matthias.kaehlcke@gmail.com</email>
</author>
<published>2007-07-17T11:04:16Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=67837f232d6d55be99d6e0dec4ea9bb8112840cd'/>
<id>urn:sha1:67837f232d6d55be99d6e0dec4ea9bb8112840cd</id>
<content type='text'>
The CAPI 2.0 driver uses a semaphore as mutex.  Use the mutex API instead of
the (binary) semaphore.

Signed-off-by: Matthias Kaehlcke &lt;matthias.kaehlcke@gmail.com&gt;
Acked-by: Karsten Keil &lt;kkeil@suse.de&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] fix fallout from header dependency trimming</title>
<updated>2006-12-04T20:45:29Z</updated>
<author>
<name>Al Viro</name>
<email>viro@hera.kernel.org</email>
</author>
<published>2006-12-04T20:41:19Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=a80958f4849316a18c06f75b9e850ccecbf20df8'/>
<id>urn:sha1:a80958f4849316a18c06f75b9e850ccecbf20df8</id>
<content type='text'>
OK, that seems to be enough to deal with the mess.

Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] severing skbuff.h -&gt; mm.h</title>
<updated>2006-12-04T07:00:34Z</updated>
<author>
<name>Al Viro</name>
<email>viro@zeniv.linux.org.uk</email>
</author>
<published>2006-12-04T04:15:30Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=d7fe0f241dceade9c8d4af75498765c5ff7f27e6'/>
<id>urn:sha1:d7fe0f241dceade9c8d4af75498765c5ff7f27e6</id>
<content type='text'>
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[PATCH] sparse: drivers/isdn/* annotation</title>
<updated>2004-07-12T02:09:14Z</updated>
<author>
<name>Alexander Viro</name>
<email>viro@www.linux.org.uk</email>
</author>
<published>2004-07-12T02:09:14Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=dd3fb8a8c1f93c64dd16cc05e53054b30437ecc9'/>
<id>urn:sha1:dd3fb8a8c1f93c64dd16cc05e53054b30437ecc9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[PATCH] i4l: kernelcapi receive workqueue and locking rework</title>
<updated>2004-04-12T05:41:07Z</updated>
<author>
<name>Andrew Morton</name>
<email>akpm@osdl.org</email>
</author>
<published>2004-04-12T05:41:07Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=ee28db843649533f5650186251ae4a8bd49a3da9'/>
<id>urn:sha1:ee28db843649533f5650186251ae4a8bd49a3da9</id>
<content type='text'>
From: Armin Schindler &lt;armin@melware.de&gt;

With this patch the ISDN kernel CAPI code uses a per application workqueue
with proper locking to prevent message re-ordering due to the fact a
workqueue may run on another CPU at the same time.  Also some locks for
internal data is added.

Removed global recv_queue work, use per application workqueue.  Added
proper locking mechanisms for application, controller and application
workqueue function.  Increased max.  number of possible applications and
controllers.
</content>
</entry>
<entry>
<title>ISDN: CAPI: Get rid of capi_signal mechanism</title>
<updated>2002-05-17T15:16:21Z</updated>
<author>
<name>Kai Germaschewski</name>
<email>kai@tp1.ruhr-uni-bochum.de</email>
</author>
<published>2002-05-17T15:16:21Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=7914dddec2e6546b6ce7b2ed9a408f9a6ba55ec4'/>
<id>urn:sha1:7914dddec2e6546b6ce7b2ed9a408f9a6ba55ec4</id>
<content type='text'>
On arrival of a new message, kernelcapi used to call
capi20_appl::signal(), which, from the application, would call back
to capi20_get_message(). So we rather just push the message down
directly, saving this detour.
</content>
</entry>
<entry>
<title>ISDN: CAPI use struct capi20_appl * in signal callback</title>
<updated>2002-05-17T15:04:23Z</updated>
<author>
<name>Kai Germaschewski</name>
<email>kai@tp1.ruhr-uni-bochum.de</email>
</author>
<published>2002-05-17T15:04:23Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=c073438613a5a16040e75c7a9d056495852cfa92'/>
<id>urn:sha1:c073438613a5a16040e75c7a9d056495852cfa92</id>
<content type='text'>
Instead of passing an opaque handle, pass the actual struct capi20_appl,
which is now known to the applications. Applications can store
a pointer to the private data into struct capi20_appl::private.
</content>
</entry>
</feed>
