From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Bard Liao <yung-chuan.liao@linux.intel.com>,
linux-sound@vger.kernel.org, vkoul@kernel.org,
vinod.koul@linaro.org, linux-kernel@vger.kernel.org,
tiwai@suse.de, pierre-louis.bossart@linux.intel.com,
bard.liao@intel.com
Subject: Re: [PATCH 1/3] ALSA/ASoC/SoundWire: Intel: use single definition for SDW_INTEL_MAX_LINKS
Date: Sun, 18 Aug 2024 09:50:53 +0200 [thread overview]
Message-ID: <87cym61d7m.wl-tiwai@suse.de> (raw)
In-Reply-To: <19ab3bfb-cc7c-4f3d-84bb-ef35d8849064@sirena.org.uk>
On Fri, 16 Aug 2024 13:25:45 +0200,
Mark Brown wrote:
>
> On Fri, Aug 16, 2024 at 10:33:29AM +0800, Bard Liao wrote:
> > From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> >
> > The definitions are currently duplicated in intel-sdw-acpi.c and
> > sof_sdw.c. Move the definition to the sdw_intel.h header, and change
> > the prefix to make it Intel-specific.
> >
> > No functionality change in this patch.
>
> Acked-by: Mark Brown <broonie@kernel.org>
As Bard requested, the series can go via ASoC tree.
Feel free to take my ack for HDA part.
Reviewed-by: Takashi Iwai <tiwai@suse.de>
Takashi
next prev parent reply other threads:[~2024-08-18 7:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 2:33 [PATCH 0/3] ALSA/ASoC/SoundWire: Intel: update maximum number of links Bard Liao
2024-08-16 2:33 ` [PATCH 1/3] ALSA/ASoC/SoundWire: Intel: use single definition for SDW_INTEL_MAX_LINKS Bard Liao
2024-08-16 11:25 ` Mark Brown
2024-08-18 7:50 ` Takashi Iwai [this message]
2024-08-16 2:33 ` [PATCH 2/3] soundwire: intel: increase maximum number of links Bard Liao
2024-08-17 17:21 ` Vinod Koul
2024-08-16 2:33 ` [PATCH 3/3] soundwire: intel: add probe-time check on link id Bard Liao
2024-08-17 17:22 ` Vinod Koul
2024-08-20 12:44 ` [PATCH 0/3] ALSA/ASoC/SoundWire: Intel: update maximum number of links Mark Brown
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=87cym61d7m.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=vinod.koul@linaro.org \
--cc=vkoul@kernel.org \
--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