From: "Wu, Hao A" <hao.a.wu@intel.com>
To: Mara Sophie Grosch <littlefox@lf-net.org>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [PATCH v2 0/2] MdeModulePkg: fix checks for NVM command set
Date: Fri, 25 Mar 2022 08:49:28 +0000 [thread overview]
Message-ID: <DM6PR11MB402512DB852D0656754E21FECA1A9@DM6PR11MB4025.namprd11.prod.outlook.com> (raw)
In-Reply-To: <4315.1648197874415398229@groups.io>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
Oh Sorry, will double check to avoid such mistake.
Best Regards,
Hao Wu
From: littlefox via groups.io <littlefox=lf-net.org@groups.io>
Sent: Friday, March 25, 2022 4:45 PM
To: Wu; Wu, Hao A <hao.a.wu@intel.com>; devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH v2 0/2] MdeModulePkg: fix checks for NVM command set
Hi,
thanks for merging, though I already had a pull request for it and you now used the bounce email address for the commit author ^^'
It's ok, just wanted to make sure you know that groups.io pitfall for the next :)
Best regards and many thanks for your time
Mara Sophie Grosch
[-- Attachment #2: Type: text/html, Size: 2742 bytes --]
prev parent reply other threads:[~2022-03-25 8:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16DE909798871558.18232@groups.io>
2022-03-23 10:22 ` [PATCH v2 0/2] MdeModulePkg: fix checks for NVM command set Mara Sophie Grosch
2022-03-23 10:22 ` [PATCH v2 1/2] MdeModulePkg/NvmExpressDxe: fix check for Cap.Css Mara Sophie Grosch
2022-03-23 10:22 ` [PATCH v2 2/2] MdeModulePkg/NvmExpressPei: fix check for NVM command set Mara Sophie Grosch
2022-03-23 10:31 ` [edk2-devel] [PATCH v2 0/2] MdeModulePkg: fix checks " Mara Sophie Grosch
2022-03-24 0:05 ` Wu, Hao A
2022-03-25 1:04 ` Wu, Hao A
2022-03-25 8:44 ` Mara Sophie Grosch
2022-03-25 8:49 ` Wu, Hao A [this message]
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=DM6PR11MB402512DB852D0656754E21FECA1A9@DM6PR11MB4025.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