public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, quic_llindhol@quicinc.com
Cc: Rebecca Cran <rebecca@bsdio.com>
Subject: Re: [edk2-devel] [PATCH RFC edk2-platforms 0/5] Phase out MPCore SEC drivers
Date: Tue, 30 Jul 2024 17:00:29 +0200	[thread overview]
Message-ID: <CAMj1kXHrYKinQZDvpHK8bHL76EK=m0K0ykEeVOv8LytpKnqy=A@mail.gmail.com> (raw)
In-Reply-To: <1965653a-aef6-42e9-b2f6-d5f8844da405@quicinc.com>

On Tue, 30 Jul 2024 at 16:49, Leif Lindholm <quic_llindhol@quicinc.com> wrote:
>
> On 2024-07-30 15:30, Rebecca Cran wrote:
> > Ard,
> >
> >
> > It looks like your original message didn't make it through to the list.
> >
> > I don't see it on https://edk2.groups.io/g/devel/messages or in my
> > personal email client.
>
> Huh, indeed.
>
> groups.io seems upset that google's email setup has enabled some new
> form of ... something... Everything gets stuck in moderation with unique
> generated Return-Path ending in ardb.bounces.google.com
> I.e. for this specific email:
>
> Return-Path:
> 3gImnZggKDW0LcOM+RTeRZZRWP.NZXbfTN_WWTYOSZWbfTNTYN.NZX@flex--ardb.bounces.google.com
>
> Ard, can you look into what they're smoking over there?
>

I probably need to subscribe ardb+git@google.com to the mailing list,
which is the from" address when I send patches from my google dev
machine.

I am not going to bother with that, though, as we'll soon switch to
github for edk2-platforms. In the mean time, I can use another machine
to send out patches if needed.


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120081): https://edk2.groups.io/g/devel/message/120081
Mute This Topic: https://groups.io/mt/107626521/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-07-30 15:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 12:22 [edk2-devel] [PATCH RFC edk2-platforms 0/5] Phase out MPCore SEC drivers Ard Biesheuvel via groups.io
2024-07-29 12:22 ` [edk2-devel] [PATCH RFC edk2-platforms 1/5] Platform AARCH64: Drop leftover references to deleted timer PCD Ard Biesheuvel via groups.io
2024-07-29 12:22 ` [edk2-devel] [PATCH RFC edk2-platforms 2/5] Platform AARCH64: Remove bogus references to MPCore stack Ard Biesheuvel via groups.io
2024-07-30 19:16   ` Sami Mujawar
2024-07-29 12:22 ` [edk2-devel] [PATCH RFC edk2-platforms 3/5] Platform/Ampere: Switch to unicore SEC implementation Ard Biesheuvel via groups.io
2024-07-31  8:21   ` Nhi Pham via groups.io
2024-07-29 12:22 ` [edk2-devel] [PATCH RFC edk2-platforms 4/5] Platform/Durian: " Ard Biesheuvel via groups.io
2024-07-29 12:22 ` [edk2-devel] [PATCH RFC edk2-platforms 5/5] Platform/HiSilicon/D0x: " Ard Biesheuvel via groups.io
2024-07-30 12:42 ` [edk2-devel] [PATCH RFC edk2-platforms 0/5] Phase out MPCore SEC drivers Leif Lindholm
2024-07-30 14:30   ` Rebecca Cran
2024-07-30 14:48     ` Leif Lindholm
2024-07-30 15:00       ` Ard Biesheuvel [this message]
2024-07-30 15:09         ` Leif Lindholm
2024-07-30 15:18           ` Ard Biesheuvel
2024-07-30 15:34             ` Leif Lindholm
2024-07-30 14:18 ` Rebecca Cran via groups.io
2024-07-30 15:48   ` Ard Biesheuvel

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-list 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='CAMj1kXHrYKinQZDvpHK8bHL76EK=m0K0ykEeVOv8LytpKnqy=A@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /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