public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: Michael Kubacki <mikuback@linux.microsoft.com>,
	 Michael Kinney <michael.d.kinney@intel.com>,
	Andrew Fish <afish@apple.com>
Cc: devel@edk2.groups.io, Leif Lindholm <quic_llindhol@quicinc.com>,
	 Sami Mujawar <sami.mujawar@arm.com>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [edk2-devel] [PATCH v2 4/7] ArmVirtPkg.ci.yaml: Add debug macro exception
Date: Tue, 19 Sep 2023 14:46:06 +0000	[thread overview]
Message-ID: <CAMj1kXFWSnNzCuSXVzuAgVQVeqXqi2zKn_VJ0tgh1-XGJ+Gwqw@mail.gmail.com> (raw)
In-Reply-To: <0c073095-9f42-c740-72d4-a74a8c1b4ccc@linux.microsoft.com>

On Mon, 18 Sept 2023 at 22:35, Michael Kubacki
<mikuback@linux.microsoft.com> wrote:
>
> Thanks Ard. I still need a Reviewed-by on this patch to complete the series.
>

Actually, you don't but I suppose there is some difference of
interpretation here.

In the Linux community (where these tags originated), an ack from a
maintainer means 'no objections, feel free to apply this to code that
I maintain'. In this case, I am not 100% sure what the change means,
so I am not comfortable claiming that I reviewed it, but given that
this is your area of expertise rather than mine, I trust that you know
what you are doing. Hence the acked-by.

In other cases, I may rely on another person's expertise and their
reviewed-by to decide whether or not to merge something, rather than
review it myself. In this case, the acked-by is implied by the fact
that I decided to merge the PR (and therefore somewhat redundant). But
it comes down to the same thing.

If there is a Tianocore rule that says every patch needs a reviewed-by
from a maintainer, we should probably fix that. It is *not* the job of
a maintainer to review everything (and this wouldn't scale to begin
with) - rather, it is their job to ensure that everything that gets
merged has been reviewed sufficiently, either by themselves or by
other people they have confidence in.



> On 9/13/2023 1:10 PM, Ard Biesheuvel wrote:
> > On Wed, 13 Sept 2023 at 19:07, <mikuback@linux.microsoft.com> wrote:
> >>
> >> From: Michael Kubacki <michael.kubacki@microsoft.com>
> >>
> >> Adds a CI YAML entry to acknowledge a case where a macro is expanded
> >> that contains a print specifier.
> >>
> >> Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
> >> Cc: Leif Lindholm <quic_llindhol@quicinc.com>
> >> Cc: Sami Mujawar <sami.mujawar@arm.com>
> >> Cc: Gerd Hoffmann <kraxel@redhat.com>
> >> Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
> >
> > Acked-by: Ard Biesheuvel <ardb@kernel.org>
> >
> >> ---
> >>   ArmVirtPkg/ArmVirtPkg.ci.yaml | 8 ++++++++
> >>   1 file changed, 8 insertions(+)
> >>
> >> diff --git a/ArmVirtPkg/ArmVirtPkg.ci.yaml b/ArmVirtPkg/ArmVirtPkg.ci.yaml
> >> index 1e799dc4e194..506b0e72f0bb 100644
> >> --- a/ArmVirtPkg/ArmVirtPkg.ci.yaml
> >> +++ b/ArmVirtPkg/ArmVirtPkg.ci.yaml
> >> @@ -125,5 +125,13 @@
> >>           ],           # words to extend to the dictionary for this package
> >>           "IgnoreStandardPaths": [],   # Standard Plugin defined paths that should be ignore
> >>           "AdditionalIncludePaths": [] # Additional paths to spell check (wildcards supported)
> >> +    },
> >> +
> >> +    "DebugMacroCheck": {
> >> +      "StringSubstitutions": {
> >> +          # DynamicTablesPkg/Include/ConfigurationManagerObject.h
> >> +          # Reason: Expansion of macro that contains a print specifier.
> >> +          "FMT_CM_OBJECT_ID": "0x%lx"
> >> +      }
> >>       }
> >>   }
> >> --
> >> 2.42.0.windows.2
> >>
> >
> >
> > 
> >


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#108845): https://edk2.groups.io/g/devel/message/108845
Mute This Topic: https://groups.io/mt/101341655/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  parent reply	other threads:[~2023-09-19 14:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 17:06 [edk2-devel] [PATCH v2 0/7] Add DebugMacroCheck Michael Kubacki
2023-09-13 17:06 ` [edk2-devel] [PATCH v2 1/7] RedfishPkg/PlatformHostInterfaceBmcUsbNicLib: Fix DEBUG macro args Michael Kubacki
2023-09-14  2:50   ` Chang, Abner via groups.io
2023-09-13 17:06 ` [edk2-devel] [PATCH v2 2/7] pip-requirements.txt: Add regex Michael Kubacki
2023-09-13 17:06 ` [edk2-devel] [PATCH v2 3/7] SecurityPkg.ci.yaml: Add debug macro exception Michael Kubacki
2023-09-13 17:06 ` [edk2-devel] [PATCH v2 4/7] ArmVirtPkg.ci.yaml: " Michael Kubacki
2023-09-13 17:10   ` Ard Biesheuvel
2023-09-18 22:35     ` Michael Kubacki
2023-09-19  0:05       ` Michael D Kinney
2023-09-19 14:46       ` Ard Biesheuvel [this message]
2023-09-19 14:52         ` Leif Lindholm
2023-09-19 15:10           ` Michael D Kinney
2023-09-19 15:12           ` Michael Kubacki
2023-09-13 17:06 ` [edk2-devel] [PATCH v2 5/7] DynamicTablesPkg.ci.yaml: " Michael Kubacki
2023-09-14  8:42   ` Sami Mujawar
     [not found]   ` <1784B757CEFF413A.31544@groups.io>
2023-09-14  9:22     ` Sami Mujawar
2023-09-18 19:27       ` Michael Kubacki
2023-09-18 22:36       ` Michael Kubacki
2023-09-19  0:26         ` Michael D Kinney
2023-09-13 17:06 ` [edk2-devel] [PATCH v2 6/7] OvmfPkg/PlatformCI: Disable DebugMacroCheck Michael Kubacki
2023-09-13 17:06 ` [edk2-devel] [PATCH v2 7/7] BaseTools/Plugin: Add DebugMacroCheck 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=CAMj1kXFWSnNzCuSXVzuAgVQVeqXqi2zKn_VJ0tgh1-XGJ+Gwqw@mail.gmail.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