From: "Laszlo Ersek" <lersek@redhat.com>
To: Rebecca Cran <rebecca@os.amperecomputing.com>,
devel@edk2.groups.io, Pedro Falcato <pedro.falcato@gmail.com>
Cc: Michael Kubacki <mikuback@linux.microsoft.com>,
Michael Kinney <michael.d.kinney@intel.com>,
Andrew Fish <afish@apple.com>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>,
"Leif Lindholm (Quic)" <quic_llindhol@quicinc.com>
Subject: Re: [edk2-devel] edk2 uncrustify update (73.0.8)?
Date: Wed, 15 Nov 2023 09:52:37 +0100 [thread overview]
Message-ID: <cd8f766b-0037-9ddb-3fe7-e866cb3d3d7c@redhat.com> (raw)
In-Reply-To: <45488f96-0251-4cb4-9816-11733aeeb501@os.amperecomputing.com>
On 11/14/23 16:12, Rebecca Cran wrote:
> On 11/14/2023 7:51 AM, Laszlo Ersek via groups.io wrote:
>
>> Funnily enough, my stance is quite the opposite. I happen to disagree
>> with some patterns that uncrustify enforces, but I'm thankful that at
>> any given state of CI (= using any given version of uncrustify), we
>> can't have any more debates about patch formatting (that is, it's
>> especially its central nature that I like). I've found uncrustify
>> relatively easy to use locally, too.
>
> There's _one_ place we can still have a debate, but I'm hoping we can
> easily agree, and update CI to enforce it.
>
> I'd like to scrub the tree of all the NT-style function documentation
> blocks and replace them with Doxygen style.
>
> As an example of the NT style, see OvmfPkg/QemuVideoDxe/Gop.c:
>
> EFI_STATUS
> EFIAPI
> QemuVideoGraphicsOutputQueryMode (
> IN EFI_GRAPHICS_OUTPUT_PROTOCOL *This,
> IN UINT32 ModeNumber,
> OUT UINTN *SizeOfInfo,
> OUT EFI_GRAPHICS_OUTPUT_MODE_INFORMATION **Info
> )
>
> /*++
>
> Routine Description:
>
> Graphics Output protocol interface to query video mode
>
> Arguments:
> This - Protocol instance pointer.
> ModeNumber - The mode number to return information on.
> Info - Caller allocated buffer that returns
> information about ModeNumber.
> SizeOfInfo - A pointer to the size, in bytes, of the Info
> buffer.
>
> Returns:
> EFI_SUCCESS - Mode information returned.
> EFI_BUFFER_TOO_SMALL - The Info buffer was too small.
> EFI_DEVICE_ERROR - A hardware error occurred trying to retrieve
> the video mode.
> EFI_NOT_STARTED - Video display is not initialized. Call
> SetMode ()
> EFI_INVALID_PARAMETER - One of the input args was NULL.
>
> --*/
> {
> QEMU_VIDEO_PRIVATE_DATA *Private;
> QEMU_VIDEO_MODE_DATA *ModeData;
> ...
>
I strongly support that motion; the cited comment style is an eyesore.
Laszlo
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#111243): https://edk2.groups.io/g/devel/message/111243
Mute This Topic: https://groups.io/mt/102559740/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2023-11-15 8:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 11:58 [edk2-devel] edk2 uncrustify update (73.0.8)? Laszlo Ersek
2023-11-13 12:29 ` Marcin Juszkiewicz
2023-11-13 19:14 ` Rebecca Cran via groups.io
2023-11-13 20:37 ` Michael Kubacki
2023-11-13 19:07 ` Pedro Falcato
2023-11-13 20:21 ` Michael Kubacki
2023-11-13 21:05 ` Michael D Kinney
2023-11-14 14:51 ` Laszlo Ersek
2023-11-14 15:12 ` Rebecca Cran via groups.io
2023-11-15 8:52 ` Laszlo Ersek [this message]
[not found] ` <17974449E158DE38.1153@groups.io>
2023-11-13 19:10 ` Pedro Falcato
2023-11-13 20:08 ` Michael Kubacki
2023-11-13 20:37 ` Rebecca Cran
2023-11-13 21:33 ` Pedro Falcato
2023-11-14 15:01 ` Laszlo Ersek
2023-11-16 8:29 ` Pedro Falcato
2023-11-16 17:36 ` Michael Kubacki
2023-11-23 2:07 ` Pedro Falcato
2023-11-17 9:08 ` Laszlo Ersek
2023-11-23 1:44 ` Pedro Falcato
2023-11-14 1:46 ` Michael Kubacki
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=cd8f766b-0037-9ddb-3fe7-e866cb3d3d7c@redhat.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