Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Geoffrey D. Bennett" <g@b4.vu>
Cc: Takashi Iwai <tiwai@suse.com>, alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/5] ALSA: scarlett2: cleanup + level meter fix
Date: Fri, 27 Oct 2023 11:23:27 +0200	[thread overview]
Message-ID: <87edhgxvu8.wl-tiwai@suse.de> (raw)
In-Reply-To: <cover.1698342632.git.g@b4.vu>

On Thu, 26 Oct 2023 20:00:36 +0200,
Geoffrey D. Bennett wrote:
> 
> Hi Takashi,
> 
> 5 patches here for the scarlett2 driver...
> 
> Patches 1-4 are renames/cleanup/refactoring in preparation for adding
> firmware update, Scarlett Gen 4, and Vocaster support.
> 
> Patch 5 fixes the Level Meter control which was barely useful before,
> but now works as expected.
> 
> Thanks,
> Geoffrey.
> 
> Geoffrey D. Bennett (5):
>   ALSA: scarlett2: Rename scarlett_gen2 to scarlett2
>   ALSA: scarlett2: Rename Gen 3 config sets
>   ALSA: scarlett2: Add support for reading firmware version
>   ALSA: scarlett2: Allow passing any output to line_out_remap()
>   ALSA: scarlett2: Remap Level Meter values

Applied all five patches now.  Thanks.


Takashi

      parent reply	other threads:[~2023-10-27  9:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26 18:00 [PATCH 0/5] ALSA: scarlett2: cleanup + level meter fix Geoffrey D. Bennett
2023-10-26 18:01 ` [PATCH 1/5] ALSA: scarlett2: Rename scarlett_gen2 to scarlett2 Geoffrey D. Bennett
2023-10-26 18:02 ` [PATCH 2/5] ALSA: scarlett2: Rename Gen 3 config sets Geoffrey D. Bennett
2023-10-26 18:05 ` [PATCH 3/5] ALSA: scarlett2: Add support for reading firmware version Geoffrey D. Bennett
2023-10-26 18:06 ` [PATCH 4/5] ALSA: scarlett2: Allow passing any output to line_out_remap() Geoffrey D. Bennett
2023-10-26 18:08 ` [PATCH 5/5] ALSA: scarlett2: Remap Level Meter values Geoffrey D. Bennett
2023-10-27  9:23 ` Takashi Iwai [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=87edhgxvu8.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=g@b4.vu \
    --cc=tiwai@suse.com \
    /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