public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Marcin Wojtas <mw@semihalf.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Hua Jing <jinghua@marvell.com>,
	Grzegorz Jaszczyk <jaz@semihalf.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	Leif Lindholm <leif.lindholm@linaro.org>,
	Nadav Haklai <nadavh@marvell.com>,
	Neta Zur Hershkovits <neta@marvell.com>
Subject: Re: [platforms PATCH 1/2] Marvell/Drivers: MvFvbDxe: Adjust to new dependencies
Date: Tue, 17 Apr 2018 09:20:50 +0200	[thread overview]
Message-ID: <8f48b191-a74a-d7c1-0103-c15a6505549a@redhat.com> (raw)
In-Reply-To: <CAPv3WKfBh=cUuHza_AZVGeqbc8kcWkOrucZ2ReKqiKLJxoUVLQ@mail.gmail.com>

On 04/17/18 07:15, Marcin Wojtas wrote:
> 2018-04-16 21:41 GMT+02:00 Laszlo Ersek <lersek@redhat.com>:

>> There's also a bit of whitespace mangling here that's not compatible
>> with either multiline function call style that we like in edk2, but
>> perhaps edk2-platforms treats that more laxly.
>>
> 
> We had some discussions last year - I followed the coding standards:
> 
> Function (
>   Argument1,
>   Argument2,
>   Argument3
>   );

Right, this is option #1.

> But was requested to place Argument1 to the function line and the last
> bracket to Argument3 line:
> 
> Function (Argument1,
>   Argument2,
>   Argument3);

In this case I prefer compressing the arguments as much as possible, for
example

  Status = ProtocolInstance->LongMemberFunctionName (Argument1,
                               Argument2, Argument3, Argument4,
                               Argument5, Argument6);

So either break the first argument and the closing paren as well to new
lines, or else keep all arguments compressed -- break them to new lines
only when the max line width dictates so.

No need to resubmit the patch because of this, I just wanted to clarify
my remark.

Thanks
Laszlo


  parent reply	other threads:[~2018-04-17  7:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16  5:09 [platforms PATCH 0/2] Armada7k8k adjustments to EDK2 Marcin Wojtas
2018-04-16  5:09 ` [platforms PATCH 1/2] Marvell/Drivers: MvFvbDxe: Adjust to new dependencies Marcin Wojtas
2018-04-16  5:40   ` Ard Biesheuvel
2018-04-16  6:13     ` Marcin Wojtas
2018-04-16 19:41     ` Laszlo Ersek
2018-04-17  5:15       ` Marcin Wojtas
2018-04-17  5:32         ` Ard Biesheuvel
2018-04-17  6:04           ` Marcin Wojtas
2018-04-17  6:05             ` Ard Biesheuvel
2018-04-17  7:20         ` Laszlo Ersek [this message]
2018-04-16  5:09 ` [platforms PATCH 2/2] Marvell/Armada: RealTimeClockLib: Depend on gEfiCpuArchProtocolGuid Marcin Wojtas
2018-04-16  5:40   ` Ard Biesheuvel
2018-04-16 19:43   ` Laszlo Ersek

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=8f48b191-a74a-d7c1-0103-c15a6505549a@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