linux-kernel - linux-api scope (Re: [PATCH v2 11/22] media: dvb-frontend invoke enable/disable

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:	Wed, 3 Feb 2016 20:51:16 -0800
From:	Andy Lutomirski <luto@...nel.org>
To:	Shuah Khan <shuahkh@....samsung.com>
Cc:	Mauro Carvalho Chehab <mchehab@....samsung.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-media@...r.kernel.org, Linux API <linux-api@...r.kernel.org>,
	ALSA development <alsa-devel@...a-project.org>
Subject: linux-api scope (Re: [PATCH v2 11/22] media: dvb-frontend invoke
 enable/disable_source handlers)

[cc list heavily trimmed]

On Wed, Feb 3, 2016 at 8:03 PM, Shuah Khan <shuahkh@....samsung.com> wrote:
> Change dvb frontend to check if tuner is free when
> device opened in RW mode. Call to enable_source
> handler either returns with an active pipeline to
> tuner or error if tuner is busy. Tuner is released
> when frontend is released calling the disable_source
> handler.

As an actual subscriber to linux-api, I prefer for the linux-api list
to be lowish-volume and mostly limited to API-related things.  Is this
API related?  Do people think that these series should be sent to
linux-api?

Thanks,
Andy