linux-kernel - [PATCH v2 0/2] Allow rc device to open from lirc

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-next>] [day] [month] [year] [list]

Date:	Mon, 22 Jul 2013 09:21:59 +0100
From:	Srinivas KANDAGATLA <srinivas.kandagatla@...com>
To:	linux-media@...r.kernel.org
Cc:	alipowski@...eria.pl, Mauro Carvalho Chehab <mchehab@...hat.com>,
	linux-kernel@...r.kernel.org, srinivas.kandagatla@...il.com,
	srinivas.kandagatla@...com, sean@...s.org
Subject: [PATCH v2 0/2] Allow rc device to open from lirc

From: Srinivas Kandagatla <srinivas.kandagatla@...com>

Thankyou for providing comments on v1 patch.

This patchset adds new members to rc_device structure to open rc device from
code other than rc-main. In the current code rc-device is only opened via input
driver. In cases where rc device is using lirc protocol, it will never be opened
as there is no input driver associated with lirc.

Thes patch set add fix to allow use cases like this to open rc device directly.

Changes since v1:
	- used rcdev->lock around increments and decrements of users pointed by
	  Sean Young.
	- Common up code in rc_open/rc_close.

Thanks,
srini

Srinivas Kandagatla (2):
  media: rc: Add rc_open/close and use count to rc_dev.
  media: lirc: Allow lirc dev to talk to rc device

 drivers/media/rc/ir-lirc-codec.c |    1 +
 drivers/media/rc/lirc_dev.c      |   10 ++++++++
 drivers/media/rc/rc-main.c       |   46 ++++++++++++++++++++++++++++++++++---
 include/media/lirc_dev.h         |    1 +
 include/media/rc-core.h          |    4 +++
 5 files changed, 58 insertions(+), 4 deletions(-)

-- 
1.7.6.5

--
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/