From: "Sachin Ganesh via groups.io" <sachinganesh=ami.com@groups.io>
To: Felix Polyudov <Felixp@ami.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "gaoliming@byosoft.com.cn" <gaoliming@byosoft.com.cn>,
"michael.d.kinney@intel.com" <michael.d.kinney@intel.com>,
"zhiguang.liu@intel.com" <zhiguang.liu@intel.com>,
Dhanaraj V <vdhanaraj@ami.com>
Subject: Re: [edk2-devel] [PATCH 1/5] MdePkg: Add definition for NVMe Over Fabric Device Path
Date: Mon, 15 Apr 2024 19:59:02 +0000 [thread overview]
Message-ID: <BL3PR10MB6161296B8D8F4A828950297ED8092@BL3PR10MB6161.namprd10.prod.outlook.com> (raw)
In-Reply-To: <BN0PR10MB49815379027C01225B78C98BDE092@BN0PR10MB4981.namprd10.prod.outlook.com>
Hi Felix,
Corrected and resent the patch.
Thank You,
Sachin.
-----Original Message-----
From: Felix Polyudov <Felixp@ami.com>
Sent: Monday, April 15, 2024 11:04 PM
To: Sachin Ganesh <sachinganesh@ami.com>; devel@edk2.groups.io
Cc: gaoliming@byosoft.com.cn; michael.d.kinney@intel.com; zhiguang.liu@intel.com; Dhanaraj V <vdhanaraj@ami.com>
Subject: RE: [PATCH 1/5] MdePkg: Add definition for NVMe Over Fabric Device Path
Sachin,
> +#define MSG_NVME_OF_NAMESPACE_DP 0x20
UEFI Specification defines this as 34, which is 0x22 Refer to https://uefi.org/specs/UEFI/2.10/10_Protocols_Device_Path_Protocol.html#nvme-over-fabric-nvme-of-namespace-device-path
>
> +typedef struct {
>
...
> + /// Unique identifier of an NVM subsystem
>
> + ///
>
> + CHAR8 *SubsystemNQN;
>
This should be:
CHAR8 SubsystemNqn[];
Here is why:
1. According to edk2 coding conventions, only first latter of the acronym is capitalized Refer to section 4.3.4.3 @ https://tianocore-docs.github.io/edk2-CCodingStandardsSpecification/release-2.20/4_naming_conventions/43_identifiers.html#43-identifiers
2. The structure contains the actual string, not a pointer to the string.
> +} NVME_OF_NAMESPACE_DEVICE_PATH;
>
-The information contained in this message may be confidential and proprietary to American Megatrends (AMI). This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#117806): https://edk2.groups.io/g/devel/message/117806
Mute This Topic: https://groups.io/mt/105540403/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-04-15 20:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 16:47 [edk2-devel] [PATCH 0/5] General Updates based on UEFI 2.10 and PI 1.8 Specifications Sachin Ganesh via groups.io
2024-04-15 16:47 ` [edk2-devel] [PATCH 1/5] MdePkg: Add definition for NVMe Over Fabric Device Path Sachin Ganesh via groups.io
2024-04-15 17:33 ` Felix Polyudov via groups.io
2024-04-15 19:59 ` Sachin Ganesh via groups.io [this message]
2024-04-15 16:47 ` [edk2-devel] [PATCH 2/5] MdePkg: Add new Resource Attributes defined in PI 1.8 Spec Sachin Ganesh via groups.io
2024-04-15 16:47 ` [edk2-devel] [PATCH 3/5] MdePkg: Use newly defined Unaccepted Memory Type Sachin Ganesh via groups.io
2024-04-15 16:47 ` [edk2-devel] [PATCH 4/5] MdePkg: Update Delayed Dispatch PPI as per PI 1.8 Spec Sachin Ganesh via groups.io
2024-04-15 16:47 ` [edk2-devel] [PATCH 5/5] MdePkg: Update to PI 1.8 Revision Sachin Ganesh via groups.io
-- strict thread matches above, loose matches on Subject: below --
2024-04-01 22:40 [edk2-devel] [PATCH 0/5] General Updates based on UEFI 2.10 and PI 1.8 Specifications Sachin Ganesh via groups.io
2024-04-01 22:40 ` [edk2-devel] [PATCH 1/5] MdePkg: Add definition for NVMe Over Fabric Device Path Sachin Ganesh via groups.io
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=BL3PR10MB6161296B8D8F4A828950297ED8092@BL3PR10MB6161.namprd10.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