From: "Mikolaj Lisik" <lisik@google.com>
To: "Demeter, Miki" <miki.demeter@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"announce@edk2.groups.io" <announce@edk2.groups.io>,
"discuss@edk2.groups.io" <discuss@edk2.groups.io>
Subject: Re: [edk2-announce] [IMPORTANT] February Release Reviews and Merges
Date: Fri, 17 Feb 2023 18:56:31 -0800 [thread overview]
Message-ID: <CADtC8PWOT9b_D4OeZX1Ts4aF8pWn66nTCG+UL1djVdRbTkodCQ@mail.gmail.com> (raw)
In-Reply-To: <DS0PR11MB64450E9B9DA50EE5F393AAF38DD99@DS0PR11MB6445.namprd11.prod.outlook.com>
Apologies for the delay (and I am aware it probably won't make it for
the release), but I would still like to write about a patch I've had
open for a while (that has been ack-ed by multiple people):
[PATCH v2] OvmfPkg: Create additional PML1 entries for large SEV-SNP VMs
Looking at the title again it seems that there is a typo (in the title
of v2 only): "PML1" should be "PML4", not sure if it's a valid reason
for me to send a v3 or if it can be taken care of by the maintainer.
Thank you!
Mikolaj
Mikolaj
On Thu, Feb 9, 2023 at 9:00 AM Demeter, Miki <miki.demeter@intel.com> wrote:
>
> Important Information About the February Release
>
> The Stewards are aware there has been an issue with getting patches reviewed and/or merged in a timely manner. The stewards are considering a delay to the February release to allow for these issues to be addressed.
>
> Please take the time to validate that your submissions to the email list fall into one of the two categories please contact me directly immediately and CC the mailing list
>
> [1] You have patches submitted to the mailing list requesting review with no response
>
> [2] You have patches submitted to the mailing list that have been reviewed but not merged for the February release
>
>
> Thank you
>
>
>
> --
> Miki Demeter (she/her/Miki)
> Security Researcher / FW Developer
> FST
> Intel Corporation
>
> Co-Chair, Network of Intel African-Ancestry(NIA) - Oregon
> NIA-Oregon<https://intel.sharepoint.com/sites/NIA>
>
> Portland Women in Tech Best Speaker
> miki.demeter@intel.com<mailto:miki.demeter@intel.com>
> 503.712.8030 (office)
> 971.248.0123 (cell)
>
>
>
>
>
>
next prev parent reply other threads:[~2023-02-18 2:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 17:00 [IMPORTANT] February Release Reviews and Merges Demeter, Miki
2023-02-13 19:05 ` [edk2-announce] " Robert Phelps
2023-02-14 0:52 ` 回复: [edk2-devel] " gaoliming
2023-02-14 14:14 ` Robert Phelps
2023-02-15 3:46 ` 回复: " gaoliming
2023-03-01 3:03 ` 回复: [edk2-discuss] " gaoliming
2023-02-15 15:59 ` 回复: [edk2-devel] [IMPORTANT] February Release Reviews and Merges for this stable tag 202302 gaoliming
2023-02-15 18:55 ` Leif Lindholm
2023-03-01 14:51 ` 回复: [edk2-discuss] " gaoliming
2023-02-18 2:56 ` Mikolaj Lisik [this message]
[not found] ` <17440ABBEE208CE7.5898@groups.io>
2023-02-20 14:28 ` gaoliming
2023-02-20 20:14 ` Sunil V L
2023-02-22 3:08 ` 回复: " gaoliming
2023-02-22 9:51 ` Sunil V L
2023-02-23 4:16 ` 回复: " gaoliming
[not found] ` <17458EB902D6FE20.17041@groups.io>
2023-02-22 3:18 ` gaoliming
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=CADtC8PWOT9b_D4OeZX1Ts4aF8pWn66nTCG+UL1djVdRbTkodCQ@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