From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=T_SCC_BODY_TEXT_LINE
	autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 6264 invoked from network); 6 Jan 2024 19:44:30 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 6 Jan 2024 19:44:30 -0000
Received: from duke.felloff.net ([216.126.196.34]) by 9front; Sat Jan  6 14:43:32 -0500 2024
Message-ID: <F8BEB161CCE48E825649EE4FBAA1EFD3@felloff.net>
Date: Sat, 06 Jan 2024 20:43:20 +0100
From: cinap_lenrek@felloff.net
To: 9front@9front.org
In-Reply-To: <2019153489.3948164.1704557042176@comcenter.netcologne.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: scale-out blockchain YAML template persistence framework 
Subject: Re: [9front] [patch] nusb/audio /dev entries fix v2
Reply-To: 9front@9front.org
Precedence: bulk

sorry, i was busy debigging kernel crashes in the scheduler.

for mixfs, i was waiting because i was not happy with the
fact that you can specify arbitrary files for the new
audio device which could be a security issue.

for now, i'll restrict the audio device name to /dev/audio*,
#u/audio* and #A/audio*...

the new mixfs and updated manpage has been pushed now.

i'll apply your nusb/audio patch next.

--
cinap