From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: postmaster@alsa-project.org,
sound-open-firmware-owner@alsa-project.org, tiwai@suse.de,
alsa-devel@alsa-project.org,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
sound-open-firmware@alsa-project.org
Subject: Re: [alsa-devel@alsa-project.org: [PATCH 3/5] ASoC: mediatek: mt8195-afe-pcm: Simplify runtime PM during probe]
Date: Fri, 5 May 2023 17:38:28 -0300 [thread overview]
Message-ID: <ZFVpRKM5vxpWWaI9@geday> (raw)
In-Reply-To: <ZFMF2cD3nPgpZOpa@finisterre.sirena.org.uk>
On Thu, May 04, 2023 at 10:09:45AM +0900, Mark Brown wrote:
> Hi,
>
> Here's another mail (one of several in this series) that got completely
> mangled by the alsa-project.org mailman to the point of unusability. I
> didn't see any response to my last mail about this, is there any news on
> fixing mailman to not do this? It's extremely disruptive to working
> with lore.
Hi Mark,
Are you complaining about the added headers in the message? Because the
patch itself didn't look mangled from my side. From my understanding,
Jaroslav had to start mangling mail addresses due to strict DMARC rules
which make some servers reject the message from alsa-devel.
Thanks,
Geraldo Nascimento
>
> Thanks,
> Mark
next prev parent reply other threads:[~2023-05-05 20:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 1:09 [alsa-devel@alsa-project.org: [PATCH 3/5] ASoC: mediatek: mt8195-afe-pcm: Simplify runtime PM during probe] Mark Brown
2023-05-04 7:35 ` Takashi Iwai
2023-05-04 7:58 ` Takashi Iwai
2023-05-08 7:52 ` Takashi Iwai
2023-05-09 7:12 ` DMARC (Was: Re: [alsa-devel@alsa-project.org: [PATCH 3/5] ASoC: mediatek: mt8195-afe-pcm: Simplify runtime PM during probe]) Jaroslav Kysela
2023-05-09 9:37 ` Mark Brown
2023-05-09 9:54 ` Jaroslav Kysela
2023-05-09 14:35 ` Mark Brown
2023-05-09 18:03 ` Jaroslav Kysela
2023-05-09 18:26 ` Konstantin Ryabitsev
2023-05-10 2:05 ` Mark Brown
2023-05-10 3:33 ` Chen-Yu Tsai
2023-05-10 3:58 ` Geraldo Nascimento
2023-05-10 6:17 ` Jaroslav Kysela
2023-05-10 15:13 ` Konstantin Ryabitsev
2023-05-10 17:15 ` Geraldo Nascimento
2023-05-09 18:22 ` Konstantin Ryabitsev
2023-05-10 7:50 ` Jaroslav Kysela
2023-05-10 15:34 ` Konstantin Ryabitsev
2023-05-10 16:19 ` Jaroslav Kysela
2023-05-10 16:43 ` Konstantin Ryabitsev
2023-05-10 18:38 ` Jaroslav Kysela
2023-05-11 5:58 ` Mark Brown
2023-05-09 17:51 ` Geraldo Nascimento
2023-05-10 3:01 ` Chen-Yu Tsai
2023-05-10 6:46 ` Jaroslav Kysela
2023-05-05 20:38 ` Geraldo Nascimento [this message]
2023-05-06 0:13 ` [alsa-devel@alsa-project.org: [PATCH 3/5] ASoC: mediatek: mt8195-afe-pcm: Simplify runtime PM during probe] Mark Brown
2023-05-06 2:17 ` Geraldo Nascimento
2023-05-07 23:33 ` Mark Brown
2023-05-07 23:38 ` Geraldo Nascimento
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=ZFVpRKM5vxpWWaI9@geday \
--to=geraldogabriel@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=postmaster@alsa-project.org \
--cc=sound-open-firmware-owner@alsa-project.org \
--cc=sound-open-firmware@alsa-project.org \
--cc=tiwai@suse.de \
/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