From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] Fix nusb/audio /dev entries
Date: Thu, 21 Dec 2023 21:48:46 +0100 [thread overview]
Message-ID: <CAFSF3XOv8dOeBDHg1sLjviAWXvY4mLT0Q1QAocX1TgV4CALnEg@mail.gmail.com> (raw)
In-Reply-To: <193272321.3542789.1703189557177@comcenter.netcologne.de>
> how about this? Bring audio more in line with the rest of nusb. Postfix all
> the device nodes with U<hname> so we can have as much usb audio devices as
> we like
> and are not dependent on bind order.
oh in...deed.
thank you.
prev parent reply other threads:[~2023-12-21 20:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 11:23 Arne Meyer
2023-12-20 16:44 ` qwx
2023-12-20 17:19 ` Kurt H Maier
2023-12-20 17:47 ` qwx
2023-12-20 17:51 ` Kurt H Maier
2023-12-20 18:11 ` qwx
2023-12-20 18:53 ` Arne Meyer
2023-12-20 23:10 ` qwx
2023-12-21 2:47 ` Sigrid Solveig Haflínudóttir
2023-12-21 7:53 ` hiro
2023-12-21 20:12 ` Arne Meyer
2023-12-21 20:48 ` hiro [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFSF3XOv8dOeBDHg1sLjviAWXvY4mLT0Q1QAocX1TgV4CALnEg@mail.gmail.com \
--to=23hiro@gmail.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).