<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/media/dvb/dvb-core/dvbdev.c, branch linux-2.6.21.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.21.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.21.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2007-03-27T11:45:54Z</updated>
<entry>
<title>V4L/DVB (5400): Core: fix several locking related problems</title>
<updated>2007-03-27T11:45:54Z</updated>
<author>
<name>Simon Arlott</name>
</author>
<published>2007-03-10T09:21:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c278850206fd9df0bb62a72ca0b277fe20c5a452'/>
<id>urn:sha1:c278850206fd9df0bb62a72ca0b277fe20c5a452</id>
<content type='text'>
Fix several instances of dvb-core functions using mutex_lock_interruptible
and returning -ERESTARTSYS where the calling function will either never
retry or never check the return value.
These cause a race condition with dvb_dmxdev_filter_free and
dvb_dvr_release, both of which are filesystem release functions whose
return value is ignored and will never be retried.  When this happens it
becomes impossible to open dvr0 again (-EBUSY) since it has not been
released properly.

Signed-off-by: Simon Arlott &lt;simon@fire.lp0.eu&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Acked-By: Johannes Stezenbach &lt;js@linuxtv.org&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@infradead.org&gt;
</content>
</entry>
<entry>
<title>V4L/DVB (5244): Dvbdev: fix illegal re-usage of fileoperations struct</title>
<updated>2007-02-21T15:35:31Z</updated>
<author>
<name>Marcel Siegert</name>
</author>
<published>2007-02-13T12:46:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b61901024776b25ce7b8edc31bb1757c7382a88e'/>
<id>urn:sha1:b61901024776b25ce7b8edc31bb1757c7382a88e</id>
<content type='text'>
Arjan van de Ven &lt;arjan@infradead.org&gt; reported an illegal re-usage of 
the fileoperations struct if more than one dvb device (e.g. frontend) is 
present. 

This patch fixes this issue.  

It allocates a new fileoperations struct each time a device is 
registered and copies the default template fileops.

Signed-off-by: Marcel Siegert &lt;mws@linuxtv.org&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@infradead.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] remove many unneeded #includes of sched.h</title>
<updated>2007-02-14T16:09:54Z</updated>
<author>
<name>Tim Schmielau</name>
</author>
<published>2007-02-14T08:33:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cd354f1ae75e6466a7e31b727faede57a1f89ca5'/>
<id>urn:sha1:cd354f1ae75e6466a7e31b727faede57a1f89ca5</id>
<content type='text'>
After Al Viro (finally) succeeded in removing the sched.h #include in module.h
recently, it makes sense again to remove other superfluous sched.h includes.
There are quite a lot of files which include it but don't actually need
anything defined in there.  Presumably these includes were once needed for
macros that used to live in sched.h, but moved to other header files in the
course of cleaning it up.

To ease the pain, this time I did not fiddle with any header files and only
removed #includes from .c-files, which tend to cause less trouble.

Compile tested against 2.6.20-rc2 and 2.6.20-rc2-mm2 (with offsets) on alpha,
arm, i386, ia64, mips, powerpc, and x86_64 with allnoconfig, defconfig,
allmodconfig, and allyesconfig as well as a few randconfigs on x86_64 and all
configs in arch/arm/configs on arm.  I also checked that no new warnings were
introduced by the patch (actually, some warnings are removed that were emitted
by unnecessarily included header files).

Signed-off-by: Tim Schmielau &lt;tim@physik3.uni-rostock.de&gt;
Acked-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&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] devfs: Remove devfs_remove() function from the kernel tree</title>
<updated>2006-06-26T19:25:07Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
</author>
<published>2005-06-21T04:15:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8ab5e4c15b53e147c08031a959d9f776823dbe73'/>
<id>urn:sha1:8ab5e4c15b53e147c08031a959d9f776823dbe73</id>
<content type='text'>
Removes the devfs_remove() function and all callers of it.

Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] devfs: Remove devfs_mk_cdev() function from the kernel tree</title>
<updated>2006-06-26T19:25:07Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
</author>
<published>2005-06-21T04:15:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7c69ef79741910883d5543caafa06aca3ebadbd1'/>
<id>urn:sha1:7c69ef79741910883d5543caafa06aca3ebadbd1</id>
<content type='text'>
Removes the devfs_mk_cdev() function and all callers of it.

Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] devfs: Remove devfs_mk_dir() function from the kernel tree</title>
<updated>2006-06-26T19:25:06Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
</author>
<published>2005-06-21T04:15:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=95dc112a5770dc670a1b45a3d9ee346fdd2b2697'/>
<id>urn:sha1:95dc112a5770dc670a1b45a3d9ee346fdd2b2697</id>
<content type='text'>
Removes the devfs_mk_dir() function and all callers of it.

Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>V4L/DVB (3762): Add sysfs device links to dvb devices</title>
<updated>2006-06-25T04:57:55Z</updated>
<author>
<name>Andrew de Quincey</name>
</author>
<published>2006-04-10T12:27:37Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d09dbf92ada861244056d914a8f68b8be99891ed'/>
<id>urn:sha1:d09dbf92ada861244056d914a8f68b8be99891ed</id>
<content type='text'>
Currently in /sys/class/dvb/dvbX.demuxY/ we have:
	dev
	uevent
With the patch, we have (for a PCI DVB device):
	dev
	device -&gt; ../../../devices/pci0000:00/0000:00:1e.0/0000:03:0d.0
	uevent
So userspace tools can (finally) work out which physical device a DVB adapter
refers to. Previously you had to kinda look through dmesg and hope that it
hadn't been dumped out of the buffer. This makes debugging a lot easier if
the system has been up for a long time!
This is done by adding an extra 'struct device *' parameter to
dvb_register_adapter(). It will work with any kind of standard
linux 'device'. Additionally, if someone has an embedded system which does
things differently, they can simply supply 'NULL' and the behaviour will be
as before - the link will simply not appear.

Ack'd-by: Manu Abraham &lt;manu@linuxtv.org&gt;
Acked-by: Michael Krufky &lt;mkrufky@linuxtv.org&gt;
Signed-off-by: Andrew de Quincey &lt;adq_dvb@lidskialf.net&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@infradead.org&gt;
</content>
</entry>
<entry>
<title>V4L/DVB (3725): Fix mutex in dvb_register_device to work.</title>
<updated>2006-05-12T22:54:37Z</updated>
<author>
<name>Andrew de Quincey</name>
</author>
<published>2006-04-04T12:41:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f47f4763cde162656448fcd1ada9d5e8101a00d2'/>
<id>urn:sha1:f47f4763cde162656448fcd1ada9d5e8101a00d2</id>
<content type='text'>
This mutex is meant to stop two devices getting the same ID. dvbdev_get_free_id() 
scans the list of already allocated devices to find a free id.
Unfortunately, since the mutex is unlocked before the card is added to the
above list, it is still possible for two of them to get the same id.
Its debatable whether this mutex lock is actually needed, but I'm unwilling
to just remove it in case something does depend on it.

Signed-off-by: Andrew de Quincey &lt;adq_dvb@lidskialf.net&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@infradead.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] mark f_ops const in the inode</title>
<updated>2006-03-28T17:16:05Z</updated>
<author>
<name>Arjan van de Ven</name>
</author>
<published>2006-03-28T09:56:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=99ac48f54a91d02140c497edc31dc57d4bc5c85d'/>
<id>urn:sha1:99ac48f54a91d02140c497edc31dc57d4bc5c85d</id>
<content type='text'>
Mark the f_ops members of inodes as const, as well as fix the
ripple-through this causes by places that copy this f_ops and then "do
stuff" with it.

Signed-off-by: Arjan van de Ven &lt;arjan@infradead.org&gt;
Signed-off-by: Alexey Dobriyan &lt;adobriyan@gmail.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>V4L/DVB (3380): Semaphore to mutex conversion on drivers/media</title>
<updated>2006-01-15T11:03:49Z</updated>
<author>
<name>Ingo Molnar</name>
</author>
<published>2006-01-15T09:52:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1e4baed379a2bff3c728ea34602d3432fb047af8'/>
<id>urn:sha1:1e4baed379a2bff3c728ea34602d3432fb047af8</id>
<content type='text'>
- Semaphore to mutex conversion.
The conversion was generated via scripts, and the result was validated
automatically via a script as well.

Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@infradead.org&gt;
</content>
</entry>
</feed>
