From: Leif Lindholm <leif.lindholm@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: edk2-devel-01 <edk2-devel@lists.01.org>,
Laszlo Ersek <lersek@redhat.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <liming.gao@intel.com>
Subject: Re: [PATCH 1/3] MdePkg/Misc: Move ARM* BaseMemoryLibStm to MdePkg
Date: Fri, 2 Sep 2016 19:32:15 +0100 [thread overview]
Message-ID: <20160902183215.GG4715@bivouac.eciton.net> (raw)
In-Reply-To: <CAKv+Gu9HLDJQyDM0_SM4phFkTaZRmMQ5FKOikqeAujYurJu3mg@mail.gmail.com>
On Fri, Sep 02, 2016 at 07:11:02PM +0100, Ard Biesheuvel wrote:
> >> Added the fact that the Stm is not in great shape, I would really
> >> prefer to get rid of it rather than 'promote' it to the standard ARM
> >> implementation. Note that we will need another round of updates to the
> >> platform .DSCs when we remove the Stm version again.
> >
> > My main concern is leaving the master branch unusable for ARM during
> > the Labor Day weekend. If we don't resolve this tonight, with the best
> > will in the world we won't be back to a functioning master before
> > Tuesday evening.
>
> I agree that fixing the branch now would be nice. I just don't
> understand why fixing BaseMemoryLibStm in place is not a better
> solution, especially if we are nuking it anyway next week. That way,
> we have to change all the platforms only a single time.
Mainly because we don't _know_ that it will be resolved next week and
I'm currently having some trust issues regarding these libraries.
If that's what it takes to get consensus, sure, I'll go along with
that. I'm fully aware I'm being slightly irrational here.
So where to now? Just push 2-3 from Wednesday?
/
Leif
next prev parent reply other threads:[~2016-09-02 18:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 14:29 [PATCH 0/3] MdePkg/Misc: fix Arm BaseMemoryLib Leif Lindholm
2016-09-02 14:29 ` [PATCH 1/3] MdePkg/Misc: Move ARM* BaseMemoryLibStm to MdePkg Leif Lindholm
2016-09-02 15:02 ` Ard Biesheuvel
2016-09-02 15:23 ` Leif Lindholm
2016-09-02 16:07 ` Ard Biesheuvel
2016-09-02 18:05 ` Leif Lindholm
2016-09-02 18:11 ` Ard Biesheuvel
2016-09-02 18:32 ` Leif Lindholm [this message]
2016-09-02 18:45 ` Ard Biesheuvel
2016-09-02 19:18 ` Leif Lindholm
2016-09-02 19:24 ` Laszlo Ersek
2016-09-02 14:29 ` [PATCH 2/3] MdePkg/BaseMemoryLibStm: implement new IsZeroGuid() API function Leif Lindholm
2016-09-02 14:29 ` [PATCH 3/3] MdePkg/BaseMemoryLibStm: implement new IsZeroBuffer() " Leif Lindholm
2016-09-02 14:48 ` [PATCH 0/3] MdePkg/Misc: fix Arm BaseMemoryLib Laszlo Ersek
2016-09-02 14:53 ` Laszlo Ersek
2016-09-02 16:02 ` Leif Lindholm
2016-09-02 15:49 ` Kinney, Michael D
2016-09-02 15:57 ` Leif Lindholm
2016-09-02 15:59 ` Andrew Fish
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=20160902183215.GG4715@bivouac.eciton.net \
--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