summaryrefslogtreecommitdiffstats
path: root/block/Makefile
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab@redhat.com>2013-02-15 13:39:31 -0200
committerLinus Torvalds <torvalds@linux-foundation.org>2013-02-15 12:11:23 -0800
commitac89758697195a8155f3861a34f0b41c6e562fcb (patch)
tree67a97370b01558c8b691c6bc37192c133bde8cae /block/Makefile
parent11e7651432405eeee833fe9d1307488df7a81cd3 (diff)
downloadop-kernel-dev-ac89758697195a8155f3861a34f0b41c6e562fcb.zip
op-kernel-dev-ac89758697195a8155f3861a34f0b41c6e562fcb.tar.gz
Revert "[media] dvb_frontend: return -ENOTTY for unimplement IOCTL"
As reported by Klaus Schmidinger: "In VDR I use an ioctl() call with FE_READ_UNCORRECTED_BLOCKS on a device (using stb0899). After this call I check 'errno' for EOPNOTSUPP to determine whether this device supports this call. This used to work just fine, until a few months ago I noticed that my devices using stb0899 didn't display their signal quality in VDR's OSD any more. After further investigation I found that ioctl(FE_READ_UNCORRECTED_BLOCKS) no longer returns EOPNOTSUPP, but rather ENOTTY. And since I stop getting the signal quality in case any unknown errno value appears, this broke my signal quality query function." While the changes reflect what is there at: http://comments.gmane.org/gmane.linux.kernel/1235728 it does cause regression on userspace. So, revert it to stop the damage. This reverts commit 177ffe506cf8 ("[media] dvb_frontend: return -ENOTTY for unimplement IOCTL"). Reported-by: Klaus Schmidinger <Klaus.Schmidinger@tvdr.de> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'block/Makefile')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud