public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH 0/3] ALSA/PCI: add PantherLake audio support
Date: Thu, 13 Jun 2024 14:19:05 +0200	[thread overview]
Message-ID: <878qz9nih2.wl-tiwai@suse.de> (raw)
In-Reply-To: <20240612064709.51141-1-pierre-louis.bossart@linux.intel.com>

On Wed, 12 Jun 2024 08:47:06 +0200,
Pierre-Louis Bossart wrote:
> 
> Add the PCI ID for PantherLake.
> 
> Since there's a follow-up patchset for ASoC, these 3 patches could be
> applied to the ASoC tree. Otherwise an immutable branch would be
> needed.
> 
> Pierre-Louis Bossart (3):
>   PCI: pci_ids: add INTEL_HDA_PTL
>   ALSA: hda: hda-intel: add PantherLake support
>   ALSA: hda: intel-dsp-config: Add PTL support

Applied now to for-next branch.

There were duplicated Reviewed-by tags by Peter as checkpatch
complained, so I removed the one. 


thanks,

Takashi

  parent reply	other threads:[~2024-06-13 12:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12  6:47 [PATCH 0/3] ALSA/PCI: add PantherLake audio support Pierre-Louis Bossart
2024-06-12  6:47 ` [PATCH 1/3] PCI: pci_ids: add INTEL_HDA_PTL Pierre-Louis Bossart
2024-06-12 19:48   ` Bjorn Helgaas
2024-06-13 12:17     ` Takashi Iwai
2024-06-12  6:47 ` [PATCH 2/3] ALSA: hda: hda-intel: add PantherLake support Pierre-Louis Bossart
2024-06-12  6:47 ` [PATCH 3/3] ALSA: hda: intel-dsp-config: Add PTL support Pierre-Louis Bossart
2024-06-13 12:19 ` Takashi Iwai [this message]
2024-06-13 14:16   ` [PATCH 0/3] ALSA/PCI: add PantherLake audio support Pierre-Louis Bossart
2024-06-13 14:22     ` Takashi Iwai

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=878qz9nih2.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=bhelgaas@google.com \
    --cc=broonie@kernel.org \
    --cc=linux-pci@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