From: Greg KH <gregkh@linuxfoundation.org>
To: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org, tiwai@suse.de,
linux-sound@vger.kernel.org, kai.vehmanen@linux.intel.com,
ranjani.sridharan@linux.intel.com,
yung-chuan.liao@linux.intel.com, pierre-louis.bossart@linux.dev,
stable@vger.kernel.org, liam.r.girdwood@intel.com
Subject: Re: [PATCH for 7.0 1/2] ALSA: hda/intel: enforce stricter period-size alignment for Intel NVL
Date: Wed, 8 Apr 2026 12:46:12 +0200 [thread overview]
Message-ID: <2026040848-stiffness-generous-94c3@gregkh> (raw)
In-Reply-To: <20260408084514.24325-2-peter.ujfalusi@linux.intel.com>
On Wed, Apr 08, 2026 at 11:45:13AM +0300, Peter Ujfalusi wrote:
> From: Kai Vehmanen <kai.vehmanen@linux.intel.com>
>
> Intel ACE4 based products set more strict constraints on HDA BDLE start
> address and length alignment. Modify capability flags to drop
> AZX_DCAPS_NO_ALIGN_BUFSIZE for Intel Nova Lake platforms.
>
> Fixes: 7f428282fde3 ("ALSA: hda: controllers: intel: add support for Nova Lake")
> Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> Reviewed-by: Péter Ujfalusi <peter.ujfalusi@linux.intel.com>
> Reviewed-by: Liam Girdwood <liam.r.girdwood@intel.com>
This also needs a:
Cc: stable <stable@kernel.org>
As the commit you reference here is in the stable 6.19.y tree.
thanks,
greg k-h
next prev parent reply other threads:[~2026-04-08 10:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 8:45 [PATCH for 7.0 0/2] ALSA/SOF Intel: Enforce stricter period size for NVL Peter Ujfalusi
2026-04-08 8:45 ` [PATCH for 7.0 1/2] ALSA: hda/intel: enforce stricter period-size alignment for Intel NVL Peter Ujfalusi
2026-04-08 10:46 ` Greg KH [this message]
2026-04-08 12:10 ` Takashi Iwai
2026-04-08 8:45 ` [PATCH for 7.0 2/2] ASoC: SOF: Intel: hda: modify period size constraints for ACE4 Peter Ujfalusi
2026-04-08 11:41 ` [PATCH for 7.0 0/2] ALSA/SOF Intel: Enforce stricter period size for NVL Takashi Iwai
2026-04-08 12:05 ` Mark Brown
2026-04-08 12:09 ` 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=2026040848-stiffness-generous-94c3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@intel.com \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=ranjani.sridharan@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=yung-chuan.liao@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