Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: richardh@tuta.io
To: Alsa Devel <alsa-devel@alsa-project.org>
Subject: Help -  help: unsubscribe
Date: Sun, 11 Oct 2026 06:52:21 +0200 (CEST)	[thread overview]
Message-ID: <P3dIRUv----9@tuta.io> (raw)
In-Reply-To: <179167052709.30.15840441464360824678@mailman-core.alsa-project.org>

Hi 

Please unsubscribe richardh@tuta.io from your mailing list.

Many thanks

Richard

-- 
 Secured with Tuta Mail: 
 https://tuta.com/free-email


11 Oct 2026, 08:15 by alsa-devel-request@alsa-project.org:

> Send Alsa-devel mailing list submissions to
>  alsa-devel@alsa-project.org
>
> To subscribe or unsubscribe via email, send a message with subject or
> body 'help' to
>  alsa-devel-request@alsa-project.org
>
> You can reach the person managing the list at
>  alsa-devel-owner@alsa-project.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Alsa-devel digest..."Today's Topics:
>
>  1. ALSA: hda/realtek: LG Gram 16T90SP (ALC298 + ALC1318, SSID 1854:0521) - no speaker output, need amp init sequence
>  (Cory Mattson)
>  2. Backport request for 7.0.y and 7.1.y: 6485da8579e2 (ALSA: hda: Add Lenovo Legion 7i 16IAX7 17AA3874 quirk)
>  (Eli D)
>  3. [PATCH] ALSA: hda/realtek: Fix internal mic capture on ASUS ROG Flow Z13 GZ302EA
>  (Alex James)
>  4. ucm2: MediaTek: add mt8189-rt1019p-rt5682s (skywalker Chromebooks)
>  (GitHub pull_request - opened)
> _______________________________________________
> Alsa-devel mailing list -- alsa-devel@alsa-project.org
> To unsubscribe send an email to alsa-devel-leave@alsa-project.org
>


           reply	other threads:[~2026-10-11  4:53 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <179167052709.30.15840441464360824678@mailman-core.alsa-project.org>]

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=P3dIRUv----9@tuta.io \
    --to=richardh@tuta.io \
    --cc=alsa-devel@alsa-project.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