public inbox for linux-sound@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: linux-sound@vger.kernel.org, tiwai@suse.de, broonie@kernel.org
Subject: Re: [PATCH 0/5] PCI/ALSA/ASoC: Add IDs and definitions for ARL and ARL-S
Date: Thu, 07 Dec 2023 09:31:03 +0100	[thread overview]
Message-ID: <87plzi1kjc.wl-tiwai@suse.de> (raw)
In-Reply-To: <20231204212710.185976-1-pierre-louis.bossart@linux.intel.com>

On Mon, 04 Dec 2023 22:27:05 +0100,
Pierre-Louis Bossart wrote:
> 
> ArrowLake (ARL) and ArrowLake-S (ARL-S) have different PCI IDs. Add
> the usual slew of descriptors for those devices.
> 
> There are no additional PCI IDs planned for this kernel cycle so it might be
> simpler to have Takashi handle all the patches with Mark's Acked-by tag?
> 
> Pierre-Louis Bossart (5):
>   PCI: add INTEL_HDA_ARL to pci_ids.h
>   ALSA: hda: Intel: add HDA_ARL PCI ID support
>   ALSA: hda: intel-dspcfg: add filters for ARL-S and ARL
>   ASoC: SOF: Intel: pci-mtl: fix ARL-S definitions
>   ASoC: SOF: Intel: pci-mtl: add HDA_ARL PCI support

Applied all five patches now to for-next branch.


thanks,

Takashi

      parent reply	other threads:[~2023-12-07  8:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 21:27 [PATCH 0/5] PCI/ALSA/ASoC: Add IDs and definitions for ARL and ARL-S Pierre-Louis Bossart
2023-12-04 21:27 ` [PATCH 1/5] PCI: add INTEL_HDA_ARL to pci_ids.h Pierre-Louis Bossart
2023-12-04 21:27 ` [PATCH 2/5] ALSA: hda: Intel: add HDA_ARL PCI ID support Pierre-Louis Bossart
2023-12-04 21:27 ` [PATCH 3/5] ALSA: hda: intel-dspcfg: add filters for ARL-S and ARL Pierre-Louis Bossart
2023-12-04 21:27 ` [PATCH 4/5] ASoC: SOF: Intel: pci-mtl: fix ARL-S definitions Pierre-Louis Bossart
2023-12-04 21:27 ` [PATCH 5/5] ASoC: SOF: Intel: pci-mtl: add HDA_ARL PCI support Pierre-Louis Bossart
2023-12-04 21:39 ` [PATCH 0/5] PCI/ALSA/ASoC: Add IDs and definitions for ARL and ARL-S Mark Brown
2023-12-07  8:31 ` 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=87plzi1kjc.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=broonie@kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.intel.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