alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org, clemens@ladisch.de
Subject: Re: [PATCH v4 00/11] ALSA: oxfw: code refactoring for quirks specific to ASICs
Date: Tue, 18 May 2021 12:29:02 +0200	[thread overview]
Message-ID: <s5hv97gl4i9.wl-tiwai@suse.de> (raw)
In-Reply-To: <20210518084557.102681-1-o-takashi@sakamocchi.jp>

On Tue, 18 May 2021 10:45:46 +0200,
Takashi Sakamoto wrote:
> 
> Hi,
> 
> This patchset is revised version of my take 3:
>  * https://lore.kernel.org/alsa-devel/20210518024326.67576-1-o-takashi@sakamocchi.jp/
> 
> Changes from v3:
>  * use unsigned int type instead of int type for storage of combination
>    of enumeration-constants
> 
> Takashi Sakamoto (11):
>   Revert "ALSA: bebob/oxfw: fix Kconfig entry for Mackie d.2 Pro"
>   ALSA: firewire-lib/motu: use int type for the value of bitwise OR with
>     enumerator-constant
>   ALSA: oxfw: code refactoring for existent device entry with
>     specifier_id and version
>   ALSA: oxfw: code refactoring to detect mackie models
>   ALSA: oxfw: add explicit device entry for Loud Technologies Tapco
>     Link.FireWire 4x6
>   ALSA: oxfw: add explicit device entry for Loud Technologies Mackie
>     Onyx Sattelite
>   ALSA: oxfw: add comment for the type of ASICs
>   ALSA: oxfw: code refactoring for jumbo-payload quirk in OXFW970
>   ALSA: firewire-lib: code refactoring for jumbo payload quirk
>   ALSA: oxfw: code refactoring for wrong_dbs quirk
>   ALSA: oxfw: add quirk flag for blocking transmission method

Applied all 11 patches now.  Thanks.


Takashi

      parent reply	other threads:[~2021-05-18 10:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18  8:45 [PATCH v4 00/11] ALSA: oxfw: code refactoring for quirks specific to ASICs Takashi Sakamoto
2021-05-18  8:45 ` [PATCH v4 01/11] Revert "ALSA: bebob/oxfw: fix Kconfig entry for Mackie d.2 Pro" Takashi Sakamoto
2021-05-18  8:45 ` [PATCH v4 02/11] ALSA: firewire-lib/motu: use int type for the value of bitwise OR with enumerator-constant Takashi Sakamoto
2021-05-18  8:45 ` [PATCH v4 03/11] ALSA: oxfw: code refactoring for existent device entry with specifier_id and version Takashi Sakamoto
2021-05-18  8:45 ` [PATCH v4 04/11] ALSA: oxfw: code refactoring to detect mackie models Takashi Sakamoto
2021-05-18  8:45 ` [PATCH v4 05/11] ALSA: oxfw: add explicit device entry for Loud Technologies Tapco Link.FireWire 4x6 Takashi Sakamoto
2021-05-18  8:45 ` [PATCH v4 06/11] ALSA: oxfw: add explicit device entry for Loud Technologies Mackie Onyx Sattelite Takashi Sakamoto
2021-05-18  8:45 ` [PATCH v4 07/11] ALSA: oxfw: add comment for the type of ASICs Takashi Sakamoto
2021-05-18  8:45 ` [PATCH v4 08/11] ALSA: oxfw: code refactoring for jumbo-payload quirk in OXFW970 Takashi Sakamoto
2021-05-18  8:45 ` [PATCH v4 09/11] ALSA: firewire-lib: code refactoring for jumbo payload quirk Takashi Sakamoto
2021-05-18  8:45 ` [PATCH v4 10/11] ALSA: oxfw: code refactoring for wrong_dbs quirk Takashi Sakamoto
2021-05-18  8:45 ` [PATCH v4 11/11] ALSA: oxfw: add quirk flag for blocking transmission method Takashi Sakamoto
2021-05-18 10:29 ` 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=s5hv97gl4i9.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=o-takashi@sakamocchi.jp \
    /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).