From: Qi Qi <ArcticLampyrid@outlook.com>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: "sbinding@opensource.cirrus.com" <sbinding@opensource.cirrus.com>,
"david.rhodes@cirrus.com" <david.rhodes@cirrus.com>,
"james.schulman@cirrus.com" <james.schulman@cirrus.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"patches@opensource.cirrus.com" <patches@opensource.cirrus.com>,
"rf@opensource.cirrus.com" <rf@opensource.cirrus.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] ALSA: hda/realtek: Fix internal speakers for Legion Y9000X 2022 IAH7
Date: Thu, 18 Apr 2024 14:19:04 +0000 [thread overview]
Message-ID: <1883258.tdWV9SEqCh@qlaptoparch> (raw)
In-Reply-To: <ZiEnWBbvmWwKqytK@ediswmail9.ad.cirrus.com>
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
> I would wait for Stefan to review the content before respinning
> but you need to use your real name for the Signed-off-by line as
> per Documentation/process/submitting-patches.rst, it's a legal
> thing.
Thanks for the reminder.
My real name is Junhao Pei.
My PGP fingerprint is 7DA8815C10FCDAB8C6D11C4BDC72A2519E77D6CF.
I claim that I own the copyright of these patches, and agree to license them
under GPL v2.0 or later.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-04-18 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <TYCP286MB25357A4599E935F26A8AAB24C40E2@TYCP286MB2535.JPNP286.PROD.OUTLOOK.COM>
2024-04-18 13:20 ` [PATCH v3 2/2] ALSA: hda/realtek: Fix internal speakers for Legion Y9000X 2022 IAH7 ArcticLampyrid
2024-04-18 13:59 ` Charles Keepax
2024-04-18 14:19 ` Qi Qi [this message]
2024-04-18 14:45 ` Greg KH
2024-04-19 15:40 ` Qi Qi
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=1883258.tdWV9SEqCh@qlaptoparch \
--to=arcticlampyrid@outlook.com \
--cc=ZiEnWBbvmWwKqytK@ediswmail9.ad.cirrus.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=david.rhodes@cirrus.com \
--cc=james.schulman@cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--cc=sbinding@opensource.cirrus.com \
--cc=stable@vger.kernel.org \
/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