From: Mario Limonciello <superm1@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: mario.limonciello@amd.com, lgirdwood@gmail.com,
peter.ujfalusi@linux.intel.com, yung-chuan.liao@linux.intel.com,
ranjani.sridharan@linux.intel.com, daniel.baluta@nxp.com,
perex@perex.cz, tiwai@suse.com,
Stephen Rothwell <sfr@canb.auug.org.au>,
sound-open-firmware@alsa-project.org,
linux-sound@vger.kernel.org
Subject: Re: [PATCH] ASoC: SOF: amd: Add depends on CPU_SUP_AMD
Date: Thu, 20 Feb 2025 12:46:44 -0600 [thread overview]
Message-ID: <0ce85813-3c23-4363-94df-889e40785aa2@kernel.org> (raw)
In-Reply-To: <Z7d356eKF2gCNjfO@finisterre.sirena.org.uk>
On 2/20/2025 12:43, Mark Brown wrote:
> On Thu, Feb 20, 2025 at 10:51:26AM -0600, Mario Limonciello wrote:
>> From: Mario Limonciello <mario.limonciello@amd.com>
>>
>> When SMN support was switched to the kernel wide AMD_NODE instead of
>> local implementation this broke compilation on the allyesconfig for
>> some architectures. AMD_NODE is only supported on AMD platforms, so
>> modify all the AMD drivers that use it to also require CPU_SUP_AMD.
>>
>> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
>> Closes: https://lore.kernel.org/linux-next/20250220160950.2cd64bdb@canb.auug.org.au/
>> Fixes: f120cf33d232 ("ASoC: SOF: amd: Use AMD_NODE")
>> ---
>
> You've not provided a Signed-off-by for this so I can't do anything with
> it, please see Documentation/process/submitting-patches.rst for details
> on what this is and why it's important.
Whoops, sorry about that, will resend.
next prev parent reply other threads:[~2025-02-20 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 16:51 [PATCH] ASoC: SOF: amd: Add depends on CPU_SUP_AMD Mario Limonciello
2025-02-20 18:43 ` Mark Brown
2025-02-20 18:46 ` Mario Limonciello [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-20 18:48 Mario Limonciello
2025-02-20 22:21 ` 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=0ce85813-3c23-4363-94df-889e40785aa2@kernel.org \
--to=superm1@kernel.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=sound-open-firmware@alsa-project.org \
--cc=tiwai@suse.com \
--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