From: "Chang, Abner" <abner.chang@amd.com>
To: Mike Maslenkin <mike.maslenkin@gmail.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "nicklew@nvidia.com" <nicklew@nvidia.com>,
"igork@ami.com" <igork@ami.com>
Subject: Re: [PATCH 0/2][edk2-redfish-client] fix trivial misprint
Date: Wed, 5 Jul 2023 02:39:21 +0000 [thread overview]
Message-ID: <MN2PR12MB39666031AEB9511D2D93E656EA2FA@MN2PR12MB3966.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230703213748.63317-1-mike.maslenkin@gmail.com>
[AMD Official Use Only - General]
Thank you Mike, please just create a PR for this.
Abner
> -----Original Message-----
> From: Mike Maslenkin <mike.maslenkin@gmail.com>
> Sent: Tuesday, July 4, 2023 5:38 AM
> To: devel@edk2.groups.io
> Cc: Chang, Abner <Abner.Chang@amd.com>; nicklew@nvidia.com;
> igork@ami.com; Mike Maslenkin <mike.maslenkin@gmail.com>
> Subject: [PATCH 0/2][edk2-redfish-client] fix trivial misprint
>
> Caution: This message originated from an External Source. Use proper caution
> when opening attachments, clicking links, or responding.
>
>
> Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com>
> Cc: Abner Chang <abner.chang@amd.com>
> Cc: Nickle Wang <nicklew@nvidia.com>
> Cc: Igor Kulchytskyy <igork@ami.com>
prev parent reply other threads:[~2023-07-05 2:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 21:37 [PATCH 0/2][edk2-redfish-client] fix trivial misprint Mike Maslenkin
2023-07-03 21:37 ` [PATCH 1/2][edk2-redfish-client] RedfishClientPkg: fix format used for output __func__ Mike Maslenkin
2023-07-04 13:14 ` Nickle Wang
2023-07-05 2:38 ` Chang, Abner
2023-07-03 21:37 ` [PATCH 2/2][edk2-redfish-client] Tools: fix script name in README Mike Maslenkin
2023-07-04 13:15 ` Nickle Wang
2023-07-05 2:38 ` Chang, Abner
2023-07-05 2:39 ` Chang, Abner [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=MN2PR12MB39666031AEB9511D2D93E656EA2FA@MN2PR12MB3966.namprd12.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