From: Mark Brown <broonie@kernel.org>
To: Gabriel Santese <santesegabriel@gmail.com>
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
mario.limonciello@amd.com, venkataprasad.potturu@amd.com,
talhah.peerbhai@gmail.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: Add quirk for MSI Bravo 17 D7VF internal mic
Date: Thu, 29 May 2025 12:18:46 +0100 [thread overview]
Message-ID: <2bca9eea-d75e-4e2b-a32c-25b2e7fcaa2e@sirena.org.uk> (raw)
In-Reply-To: <20250528235331.67800-1-santesegabriel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
On Thu, May 29, 2025 at 01:53:31AM +0200, Gabriel Santese wrote:
> MSI Bravo 17 (D7VF), like other laptops from the family,
> has broken ACPI tables and needs a quirk for internal mic
> to work properly.
> ---
> sound/soc/amd/yc/acp6x-mach.c | 7 +++++++
> 1 file changed, 7 insertions(+)
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.
Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-05-29 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 23:53 [PATCH] mfd: Add quirk for MSI Bravo 17 D7VF internal mic Gabriel Santese
2025-05-29 11:18 ` Mark Brown [this message]
2025-05-30 0:52 ` [PATCH] ASoC: amd: yc: " Gabriel Santese
2025-06-12 15: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=2bca9eea-d75e-4e2b-a32c-25b2e7fcaa2e@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perex@perex.cz \
--cc=santesegabriel@gmail.com \
--cc=talhah.peerbhai@gmail.com \
--cc=tiwai@suse.com \
--cc=venkataprasad.potturu@amd.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