From: "Isaac Oram" <isaac.w.oram@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"benjamin.doron00@gmail.com" <benjamin.doron00@gmail.com>,
"Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>,
"Chaganty, Rangasai V" <rangasai.v.chaganty@intel.com>
Subject: Re: [edk2-devel] [edk2-platforms][PATCH V1 0/2] Platforms/Intel: Build fixes
Date: Wed, 28 Sep 2022 17:22:30 +0000 [thread overview]
Message-ID: <SA1PR11MB5801FF7172FF537F1BA55847D0549@SA1PR11MB5801.namprd11.prod.outlook.com> (raw)
In-Reply-To: <4915.1664381803976585893@groups.io>
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
Nate or Sai, this series should be a quick review if you could please prioritize…
Benjamin,
Your series is reviewed but breaks several builds due to unrelated changes. My plan is to get approval for mine, then submit both series as a batch to ensure bisect not broken.
But I didn’t get a reviewed by or ack yet for my changes. If you review/send Reviewed-by then all I need is an Ack. And it may be that the others were waiting for your approval since my changes modify yours.
Anytime I am included in a review, but am not a maintainer, I try to review as it isn’t approval to commit, but maintainers may want to see my thoughts. That is my interpretation anyway. There are no requirement for you to review, maintainer approval is the gate as I understand it.
There are two paths. But if you integrate my changes into yours and send a new version, it is then signed off by both of us and we need a third reviewer anyway. Thus it seems easier to have Nate or Sai review my series.
Regards.
Isaac
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Benjamin Doron
Sent: Wednesday, September 28, 2022 9:17 AM
To: Oram, Isaac W <isaac.w.oram@intel.com>; devel@edk2.groups.io
Subject: Re: [edk2-devel] [edk2-platforms][PATCH V1 0/2] Platforms/Intel: Build fixes
Thanks, Isaac. Are these two S3 series ready to merge, or did I have more review to address?
[-- Attachment #2: Type: text/html, Size: 3940 bytes --]
next prev parent reply other threads:[~2022-09-28 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 18:40 [edk2-devel][edk2-platforms][PATCH V1 0/2] Platforms/Intel: Build fixes Isaac Oram
2022-09-14 18:40 ` [edk2-devel][edk2-platforms][PATCH V1 1/2] S3FeaturePkg/Build: Add libraries needed by S3FeaturePkg Isaac Oram
2022-09-14 18:40 ` [edk2-devel][edk2-platforms][PATCH V1 2/2] MinPlatformPkg/S3: Use EFI_PHYSICAL_ADDRESS for address Isaac Oram
2022-09-28 16:16 ` [edk2-devel] [edk2-platforms][PATCH V1 0/2] Platforms/Intel: Build fixes Benjamin Doron
2022-09-28 17:22 ` Isaac Oram [this message]
2022-10-11 23:40 ` [edk2-devel][edk2-platforms][PATCH " Nate DeSimone
2022-10-12 1:33 ` Isaac Oram
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=SA1PR11MB5801FF7172FF537F1BA55847D0549@SA1PR11MB5801.namprd11.prod.outlook.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