From: "Limonciello, Mario" <mario.limonciello@amd.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Xiaoyan Li <lxy.lixiaoyan@gmail.com>,
Syed Saba Kareem <Syed.SabaKareem@amd.com>,
Sebastian S <iam@decentr.al>,
Travis Glenn Hansen <travisghansen@yahoo.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: amd: yc: Add Lenovo Yoga Slim 7 Pro X to quirks table
Date: Tue, 20 Sep 2022 13:56:34 -0500 [thread overview]
Message-ID: <557738ee-9e22-6c04-c098-0ca965e67aed@amd.com> (raw)
In-Reply-To: <YyoLYe9uGNnfl1iA@sirena.org.uk>
On 9/20/2022 13:50, Mark Brown wrote:
> On Tue, Sep 20, 2022 at 01:09:45PM -0500, Limonciello, Mario wrote:
>
>> As I mentioned below the cutline it's on top of the other commit on the list
>> touching the same code:
>
>> https://lore.kernel.org/alsa-devel/20220917070847.14346-1-lxy.lixiaoyan@gmail.com/
>
> That looks like it's some patch which wasn't even sent to me...
>
> Please include human readable descriptions of things like commits and
> issues being discussed in e-mail in your mails, this makes them much
> easier for humans to read especially when they have no internet access.
> I do frequently catch up on my mail on flights or while otherwise
> travelling so this is even more pressing for me than just being about
> making things a bit easier to read.
I guess the author forgot to include you in To or CC. Would you like me
to just re-send the combination of both of them as a v2 (including the
first on on behalf of Xiaoyan Li)?
next prev parent reply other threads:[~2022-09-20 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 17:13 [PATCH] ASoC: amd: yc: Add Lenovo Yoga Slim 7 Pro X to quirks table Mario Limonciello
2022-09-20 18:08 ` Mark Brown
2022-09-20 18:09 ` Limonciello, Mario
2022-09-20 18:50 ` Mark Brown
2022-09-20 18:56 ` Limonciello, Mario [this message]
2022-09-20 19:08 ` Mark Brown
2022-09-21 9:23 ` 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=557738ee-9e22-6c04-c098-0ca965e67aed@amd.com \
--to=mario.limonciello@amd.com \
--cc=Syed.SabaKareem@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=iam@decentr.al \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lxy.lixiaoyan@gmail.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=travisghansen@yahoo.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