public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Tinh Nguyen" <tinhnguyen@os.amperecomputing.com>
To: devel@edk2.groups.io
Cc: patches@amperecomputing.com, michael.d.kinney@intel.com,
	gaoliming@byosoft.com.cn, zhiguang.liu@intel.com,
	abner.chang@amd.com,
	Tinh Nguyen <tinhnguyen@os.amperecomputing.com>
Subject: [PATCH v3 0/3] Add IPMI SSIF definitions
Date: Wed,  3 May 2023 18:24:12 +0700	[thread overview]
Message-ID: <20230503112415.2073176-1-tinhnguyen@os.amperecomputing.com> (raw)

Change from v2:
  - Add the carbon copy (Cc) in the commit message.
  - Add Bugzilla ID in the commit message.
  - Mention why I set the number of retries as 250.

Change from v1:
  - Separate the commit for the IPMI SSIF header and IPMI SSIF PCDs
  - Correct some indent and comment style.
  - Change the PCDs name for a more readable.
  - Support KCS/SMIC Interface Capabilities too.


Tinh Nguyen (3):
  MdePkg/IndustryStandard: Add definitions for IPMI SSIF
  MdePkg: Add new PCDs for IPMI SSIF
  MdePkg/IndustryStandard: Add Interface Capabilities definitions

 MdePkg/MdePkg.dec                              | 27 ++++++
 MdePkg/Include/IndustryStandard/IpmiNetFnApp.h | 46 +++++++++
 MdePkg/Include/IndustryStandard/IpmiSsif.h     | 98 ++++++++++++++++++++
 3 files changed, 171 insertions(+)
 create mode 100644 MdePkg/Include/IndustryStandard/IpmiSsif.h

--
2.40.0

             reply	other threads:[~2023-05-03 11:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 11:24 Tinh Nguyen [this message]
2023-05-03 11:24 ` [PATCH v3 1/3] MdePkg/IndustryStandard: Add definitions for IPMI SSIF Tinh Nguyen
2023-05-03 11:24 ` [PATCH v3 2/3] MdePkg: Add new PCDs " Tinh Nguyen
2023-05-03 11:24 ` [PATCH v3 3/3] MdePkg/IndustryStandard: Add Interface Capabilities definitions Tinh Nguyen
2023-05-04  8:06   ` 回复: [ ** SPAMMAIL ** ][edk2-devel] " gaoliming
2023-05-07  9:34     ` Tinh Nguyen
2023-05-03 12:41 ` [PATCH v3 0/3] Add IPMI SSIF definitions Chang, Abner

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=20230503112415.2073176-1-tinhnguyen@os.amperecomputing.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