public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, michael.d.kinney@intel.com
Cc: Leif Lindholm <quic_llindhol@quicinc.com>,
	"Demeter, Miki" <miki.demeter@intel.com>,
	 "Kasbekar, Saloni" <saloni.kasbekar@intel.com>,
	Nickle Wang <nicklew@nvidia.com>,
	 "Clark-williams, Zachary" <zachary.clark-williams@intel.com>,
	Abner Chang <abner.chang@amd.com>,
	 Igor Kulchytskyy <igork@ami.com>,
	Nick Ramirez <nramirez@nvidia.com>
Subject: Re: [edk2-devel] [PATCH 2/2] NetworkPkg/HttpDxe: fix driver binding start issue.
Date: Thu, 20 Jul 2023 19:19:16 +0200	[thread overview]
Message-ID: <CAMj1kXHh8_nJUY-2cpuDu4aQDqi+RdjG9yumG17uW=QCvEbG6Q@mail.gmail.com> (raw)
In-Reply-To: <CO1PR11MB49293B1BF967BC999B90746FD23EA@CO1PR11MB4929.namprd11.prod.outlook.com>

On Thu, 20 Jul 2023 at 19:10, Michael D Kinney
<michael.d.kinney@intel.com> wrote:
>
> Hi Ard,
>
> This is my mistake.  I usually check the Author field when
> adding Rb/Ab tags because I have seen lots of cases where
> the Author field needs updating as well.  I forgot to do this
> step in this one.
>
> I agree a CI check against the Author field being a valid
> email address and not one of the mailing addresses would be
> valuable.  Perhaps in PatchCheck.py?
>

Yeah, and actually, a test seems to exist already but it didn't catch
this particular case:

        if ' via Groups.Io' in name and mo.group(3).endswith('@groups.io'):
            self.error("Email rewritten by lists DMARC / DKIM / SPF: " +
                       email)

I suppose replacing the 'and' with 'or' would be sufficient here? I
don't think @groups.io is ever a valid author email domain.


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



  reply	other threads:[~2023-07-20 17:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <174276A45CE2816B.5513@groups.io>
2023-06-28  0:55 ` [edk2-devel] [PATCH 2/2] NetworkPkg/HttpDxe: fix driver binding start issue Nickle Wang
2023-06-28 19:06   ` Saloni Kasbekar
2023-06-28 22:29     ` Nickle Wang
2023-06-29 22:28       ` Saloni Kasbekar
2023-07-13  6:54         ` Nickle Wang
2023-07-13 16:12           ` Saloni Kasbekar
2023-07-20  0:26             ` Michael D Kinney
2023-07-20  1:41               ` Michael D Kinney
2023-07-20 16:42                 ` Ard Biesheuvel
2023-07-20 17:07                   ` Michael D Kinney
2023-07-20 17:19                     ` Ard Biesheuvel [this message]
2023-07-24 21:53                       ` Michael D Kinney

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='CAMj1kXHh8_nJUY-2cpuDu4aQDqi+RdjG9yumG17uW=QCvEbG6Q@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