From: "Rebecca Cran via groups.io" <rebecca=os.amperecomputing.com@groups.io>
To: Nhi Pham <nhi@os.amperecomputing.com>, devel@edk2.groups.io
Cc: quic_llindhol@quicinc.com, chuong@os.amperecomputing.com
Subject: Re: [edk2-devel] [PATCH 1/2] AmpereSiliconPkg: Implement BMC Configuration screen
Date: Tue, 3 Sep 2024 08:34:30 -0600 [thread overview]
Message-ID: <b486f206-4cf3-433f-ab37-f0c43bdda203@os.amperecomputing.com> (raw)
In-Reply-To: <20240814031846.2351141-2-nhi@os.amperecomputing.com>
On 8/13/2024 9:18 PM, Nhi Pham wrote:
> +/**
> + This function updates the BMC information.
> +
> + @param[in] VOID
> +
> + @retval EFI_SUCCESS The entry point is executed successfully.
> + @retval Other Some error occurs when executing this entry point.
> +
> +**/
> +EFI_STATUS
> +UpdateBmcConfigForm (
> + VOID
> + )
> +{
VOID isn't a parameter so shouldn't be documented via @param.
--
Rebecca
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120483): https://edk2.groups.io/g/devel/message/120483
Mute This Topic: https://groups.io/mt/107889121/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-09-03 18:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 3:18 [edk2-devel] [PATCH 0/2] Ampere: Add BMC Configuration Screen Nhi Pham via groups.io
2024-08-14 3:18 ` [edk2-devel] [PATCH 1/2] AmpereSiliconPkg: Implement BMC Configuration screen Nhi Pham via groups.io
2024-09-03 14:34 ` Rebecca Cran via groups.io [this message]
2024-08-14 3:18 ` [edk2-devel] [PATCH 2/2] JadePkg: Add BmcConfigDxe Nhi Pham via groups.io
2024-08-22 8:22 ` [edk2-devel] [PATCH 0/2] Ampere: Add BMC Configuration Screen Chuong Tran
2024-08-23 2:51 ` Nhi Pham via groups.io
[not found] ` <17EE3BCF72FBD18E.23723@groups.io>
2024-08-29 7:16 ` Nhi Pham via groups.io
2024-09-01 7:31 ` memristor2 via groups.io
2024-09-06 8:15 ` Chuong Tran
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=b486f206-4cf3-433f-ab37-f0c43bdda203@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