From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: edk2-devel-groups-io <devel@edk2.groups.io>,
"Gao, Liming" <liming.gao@intel.com>
Cc: "pete@akeo.ie" <pete@akeo.ie>,
"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>
Subject: Re: [edk2-devel] [edk2-platforms: PATCH v2 2/2] RaspberryPi/RPi3: Update DSC/FDF to use NetworkPkg DSC/FDF
Date: Mon, 10 Jun 2019 12:23:27 +0200 [thread overview]
Message-ID: <CAKv+Gu_9jEwhNMDmGiqf2-5NNfAvQubj_eRMJji39neVRQzz+g@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu_G0J+CisgEZScRe61n1hOhRFhZT5mpz_tuj3rCQNxwjA@mail.gmail.com>
On Mon, 10 Jun 2019 at 09:49, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>
> On Mon, 10 Jun 2019 at 02:33, Liming Gao <liming.gao@intel.com> wrote:
> >
> > Pete:
> > The change is good. Reviewed-by: Liming Gao <liming.gao@intel.com>
> >
> > In fact, I send this patch before. https://edk2.groups.io/g/devel/message/41480?p=,,,20,0,0,0::Created,,Network,20,2,0,31819937
>
> Apologies for that, I will look at those now.
>
> > But, I don't get the response. Then, I think this platform is out of maintain.
> >
>
> On the contrary: Pete just spent a tremendous amount of energy
> contributing it, so it is certainly not unmaintained. I just lost
> track of all the patches flying around right before we entered the
> soft freeze.
OK, I will take Pete's version of the patches, since it also fixes the
AXIS usb networking issue.
next prev parent reply other threads:[~2019-06-10 10:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 15:07 [edk2-platforms: PATCH v2 0/2] Minor updates to platform Pete Batard
2019-06-07 15:07 ` [edk2-platforms: PATCH v2 1/2] RaspberryPi/RPi3: Enable RAM Disk Pete Batard
2019-06-07 15:07 ` [edk2-platforms: PATCH v2 2/2] RaspberryPi/RPi3: Update DSC/FDF to use NetworkPkg DSC/FDF Pete Batard
2019-06-10 0:33 ` [edk2-devel] " Liming Gao
2019-06-10 7:49 ` Ard Biesheuvel
2019-06-10 10:23 ` Ard Biesheuvel [this message]
2019-06-10 13:35 ` Liming Gao
2019-06-10 14:11 ` Leif Lindholm
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_9jEwhNMDmGiqf2-5NNfAvQubj_eRMJji39neVRQzz+g@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