From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: Pete Batard <pete@akeo.ie>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
Leif Lindholm <leif@nuviainc.com>
Subject: Re: [PATCH 1/1] EmbeddedPkg/AcpiLib: add GICC table init macro for ACPI 6.3
Date: Mon, 30 Mar 2020 16:42:15 +0200 [thread overview]
Message-ID: <CAKv+Gu-57F+7xiGe4L6U8L4MfFSLbPAG+gD40T_POsDSTg6Z9Q@mail.gmail.com> (raw)
In-Reply-To: <413d1143-a4da-198a-841e-a4e96c3fd63e@akeo.ie>
On Mon, 30 Mar 2020 at 16:39, Pete Batard <pete@akeo.ie> wrote:
>
> On 2020.03.30 15:34, Ard Biesheuvel wrote:
>
...
> > Again, I am happy to merge this patch. The argument is about whether
> > we need to upgrade RPi4 to 6.3
> >
>
> Last time I checked, quite a few of the people who contributed code to
> the platform were of the opinion that we did.
>
Then they are cordially invited to argue their position, preferably
using arguments.
> I will re-send an e-mail to the group, off-list, so that you get an idea
> of what the current stance is on that topic, and then decide whether
> your want to uphold your current position.
>
Sure. I'd prefer on-list to be honest, but if you feel it needs to be
off-list, that is also fine.
next prev parent reply other threads:[~2020-03-30 14:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 13:01 [edk2-platforms][PATCH 1/1] EmbeddedPkg/AcpiLib: add GICC table init macro for ACPI 6.3 Pete Batard
2020-03-27 13:06 ` [PATCH " Pete Batard
2020-03-30 13:06 ` Ard Biesheuvel
2020-03-30 13:09 ` Pete Batard
2020-03-30 13:12 ` Ard Biesheuvel
2020-03-30 13:20 ` Ard Biesheuvel
2020-03-30 13:56 ` Pete Batard
2020-03-30 14:01 ` Ard Biesheuvel
2020-03-30 14:06 ` Pete Batard
2020-03-30 14:16 ` Ard Biesheuvel
2020-03-30 14:29 ` Pete Batard
2020-03-30 14:34 ` Ard Biesheuvel
2020-03-30 14:39 ` Pete Batard
2020-03-30 14:42 ` Ard Biesheuvel [this message]
2020-03-30 14:50 ` Pete Batard
2020-03-30 14:19 ` Ard Biesheuvel
2020-03-30 14:33 ` Pete Batard
2020-03-30 14:48 ` [edk2-platforms][PATCH " Ard Biesheuvel
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=CAKv+Gu-57F+7xiGe4L6U8L4MfFSLbPAG+gD40T_POsDSTg6Z9Q@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