From: "Rebecca Cran" <rebecca@bsdio.com>
To: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>,
devel@edk2.groups.io, quic_llindhol@quicinc.com
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
Pedro Falcato <pedro.falcato@gmail.com>
Subject: Re: [edk2-devel] [PATCH v6 2/2] add ArmCpuInfo EFI application
Date: Fri, 21 Apr 2023 09:15:10 -0600 [thread overview]
Message-ID: <391daf63-b07a-2bff-ad73-7fca2461d1c2@bsdio.com> (raw)
In-Reply-To: <1bdb2272-b5bc-fa76-9e7f-0be48ba36553@linaro.org>
On 4/21/23 08:59, Marcin Juszkiewicz wrote:
> Thanks for links. Interface for EDK2 CI is not easy for beginners.
It really isn't, unfortunately.
> Doxygen info is something I probably never wrote so would need to look
> at rest of EDK2 code to find out what it is and how to use it.
It's pretty straightforward. The format EDK2 uses is:
/** Description of the function.
@param FirstParam Description of FirstParam:
Can use multiple lines.
@param SecondParam Description of SecondParam.
@return Explanation of return values - or can use @retval instead.
@retval FirstPossibleReturnValue Can use @retval instead of @return
to describe individual values.
@retval SecondPossibleReturnValue Description.
**/
>
> There is also this:
>
> > ERROR - EFI coding style error
> > ERROR - *Error code: 9001
> > ERROR - *The file headers should follow Doxygen special
> > documentation blocks in section 2.3.5
> > ERROR - *file: D:\a\1\s\Build\.pytool\Plugin\EccCheck\ArmPkg
> > \Application\ArmCpuInfo\ArmCpuInfo.inf
> > ERROR - *Line number: 1
> > ERROR - *Header comment section must have Abstract information.
>
> Same situation as with Doxygen above.
Oh, that's something I've had trouble with in the past. For your patch,
it's probably due to the blank line between @file and the description:
## @file
#
# Attempt to have AArch64 cpu information.
One more thing: copyright lines should ideally have "<BR>" at the end,
to indicate to Doxygen to add a line break.
--
Rebecca Cran
next prev parent reply other threads:[~2023-04-21 15:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 18:02 [PATCH] add ArmCpuInfo EFI application Marcin Juszkiewicz
2023-04-06 21:05 ` [edk2-devel] " Rebecca Cran
2023-04-07 10:39 ` [PATCH v2] " Marcin Juszkiewicz
2023-04-07 10:55 ` [edk2-devel] " Ard Biesheuvel
2023-04-07 12:46 ` Marcin Juszkiewicz
2023-04-07 13:07 ` Ard Biesheuvel
2023-04-07 12:47 ` [PATCH v3] " Marcin Juszkiewicz
2023-04-07 13:02 ` [edk2-devel] " Pedro Falcato
2023-04-07 13:05 ` Pedro Falcato
2023-04-07 13:29 ` Marcin Juszkiewicz
2023-04-07 13:40 ` Pedro Falcato
2023-04-07 13:41 ` Pedro Falcato
2023-04-07 13:42 ` Marcin Juszkiewicz
2023-04-07 14:02 ` [PATCH v4] " Marcin Juszkiewicz
[not found] ` <1753ABF1A296B040.11304@groups.io>
2023-04-07 15:11 ` [edk2-devel] " Marcin Juszkiewicz
2023-04-07 15:29 ` [PATCH v5 0/2] add ArmCpuInfo application Marcin Juszkiewicz
2023-04-07 15:29 ` [PATCH v5 1/2] ArmLib: add functions to read system registers Marcin Juszkiewicz
2023-04-20 10:54 ` Leif Lindholm
2023-04-07 15:29 ` [PATCH v5 2/2] add ArmCpuInfo EFI application Marcin Juszkiewicz
2023-04-20 12:43 ` Leif Lindholm
2023-04-20 14:42 ` [edk2-devel] " Marcin Juszkiewicz
2023-04-20 14:44 ` [PATCH v6 1/2] ArmLib: add functions to read system registers Marcin Juszkiewicz
2023-04-20 14:44 ` [PATCH v6 2/2] add ArmCpuInfo EFI application Marcin Juszkiewicz
2023-04-20 17:29 ` Leif Lindholm
2023-04-21 14:37 ` [edk2-devel] " Rebecca Cran
2023-04-21 14:59 ` Marcin Juszkiewicz
2023-04-21 15:15 ` Rebecca Cran [this message]
2023-04-21 15:51 ` [PATCH v7 1/2] ArmLib: add functions to read system registers Marcin Juszkiewicz
2023-04-21 15:51 ` [PATCH v7 2/2] add ArmCpuInfo EFI application Marcin Juszkiewicz
2023-04-21 20:18 ` Leif Lindholm
2023-04-21 16:33 ` [edk2-devel] [PATCH v6 " Leif Lindholm
2023-04-13 9:31 ` [PATCH v5 0/2] add ArmCpuInfo application Marcin Juszkiewicz
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=391daf63-b07a-2bff-ad73-7fca2461d1c2@bsdio.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