public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Abner Chang" <abner.chang@hpe.com>
To: Laszlo Ersek <lersek@redhat.com>,
	Bret Barkelew <Bret.Barkelew@microsoft.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	liming.gao <liming.gao@intel.com>,
	"announce@edk2.groups.io" <announce@edk2.groups.io>
Cc: Leif Lindholm <leif@nuviainc.com>,
	"afish@apple.com" <afish@apple.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Guptha, Soumya K" <soumya.k.guptha@intel.com>
Subject: Re: [edk2-announce] Re: Soft Feature Freeze starts now for edk2-stable202008
Date: Wed, 19 Aug 2020 11:29:52 +0000	[thread overview]
Message-ID: <CS1PR8401MB11446502214D6FCC41D446D2FF5D0@CS1PR8401MB1144.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <03b3deed-8506-94c3-d14a-eca9198b48a2@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]

Hmm.. I had a one commit (which is not the feature) just reviewed by Leif but not pushing yet. Is that possible to push before the Hard Feature freeze and also be included in 202008 stable tag? I guess it gets the chance according to the article of SoftFeatureFreeze on Wiki page.
Patch attached FYR

Abner

> -----Original Message-----
> From: announce@edk2.groups.io [mailto:announce@edk2.groups.io] On
> Behalf Of Laszlo Ersek
> Sent: Wednesday, August 19, 2020 5:59 PM
> To: Bret Barkelew <Bret.Barkelew@microsoft.com>; devel@edk2.groups.io;
> liming.gao <liming.gao@intel.com>; announce@edk2.groups.io
> Cc: Leif Lindholm <leif@nuviainc.com>; afish@apple.com; Kinney, Michael D
> <michael.d.kinney@intel.com>; Guptha, Soumya K
> <soumya.k.guptha@intel.com>
> Subject: Re: [edk2-announce] [EXTERNAL] Re: Soft Feature Freeze starts
> now for edk2-stable202008
> 
> On 08/18/20 17:10, Bret Barkelew wrote:
> > I agree with the process and withdraw my request, replacing it instead with
> a disapproving head shake and deep sigh.
> 
> We as a community definitely deserve your disapproval, as our review
> response times have been abysmal. :(
> 
> > I’ll go back to pushing on this after the tag.
> 
> Thanks for your persistence!
> Laszlo
> 
> 
> 


[-- Attachment #2: 0001-EmbeddedPkg-libfdt-Add-strncmp-macro-to-use-AsciiStr.patch --]
[-- Type: application/octet-stream, Size: 1984 bytes --]

From e6531052d0185569065239087c82cec4dfc926a1 Mon Sep 17 00:00:00 2001
From: Abner Chang <abner.chang@hpe.com>
Date: Tue, 4 Aug 2020 17:06:39 +0800
Subject: [PATCH] EmbeddedPkg/libfdt: Add strncmp macro to use AsciiStrnCmp

For the implementation which utilizes libfdt provided in EmbeddedPkg
however it uses strncmp function in the libfdt helper library,
libfdt_env.h should provide the macro implied with edk2 strncmp
implementation.

The example is RISC-V OpenSBI library. edk2 RISC-V port uses OpenSBI
library and incorporate with edk2 libfdt. edk2 libfdt_env.h provides
the necessary macros to build OpenSBI which uses fdt functions in edk2
environment. However, OpenSBI also has libfdt helper library that uses
strncmp function which is not defined in edk2 libfdt_env.h. This commit
addresses the build issue caused by missing strncmp macro in
libfdt_env.h.

Check below three commits for the corresponding changes on OpenSBI,
https://github.com/riscv/opensbi/commit/8e47649eff96c303e02fbd58cdc6c4ed341066ec
https://github.com/riscv/opensbi/commit/2845d2d2cf4fb74a89452ba223995aa4a118c07e
https://github.com/riscv/opensbi/commit/2cfd2fc9048806353298a1b967abf985901e36e8

Signed-off-by: Abner Chang <abner.chang@hpe.com>
Reviewed-by: Leif Lindholm <leif@nuviainc.com>

Cc: Leif Lindholm <leif@nuviainc.com>
Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>
Cc: Daniel Schaefer <daniel.schaefer@hpe.com>
---
 EmbeddedPkg/Include/libfdt_env.h | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/EmbeddedPkg/Include/libfdt_env.h b/EmbeddedPkg/Include/libfdt_env.h
index 11a9764733..7feff52bc0 100644
--- a/EmbeddedPkg/Include/libfdt_env.h
+++ b/EmbeddedPkg/Include/libfdt_env.h
@@ -76,4 +76,8 @@ static inline size_t strnlen (const char* str, size_t strsz ) {
   return AsciiStrnLenS (str, strsz);
 }
 
+static inline size_t strncmp (const char* str1, const char* str2, size_t strsz ) {
+  return AsciiStrnCmp (str1, str2, strsz);
+}
+
 #endif /* _LIBFDT_ENV_H */
-- 
2.25.0


  reply	other threads:[~2020-08-19 11:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-14  8:16 Soft Feature Freeze starts now for edk2-stable202008 Liming Gao
2020-08-17 18:14 ` Bret Barkelew
2020-08-17 20:46   ` Laszlo Ersek
2020-08-17 21:33     ` [EXTERNAL] " Bret Barkelew
2020-08-18 10:29       ` Laszlo Ersek
2020-08-18 15:10         ` Bret Barkelew
2020-08-19  9:59           ` Laszlo Ersek
2020-08-19 11:29             ` Abner Chang [this message]
2020-08-19 11:48               ` [edk2-announce] " Leif Lindholm
2020-08-19 13:19                 ` Laszlo Ersek
2020-08-19 13:34                   ` Abner Chang
2020-08-19 14:29                     ` Laszlo Ersek
2020-08-19 14:58                       ` Abner Chang
2020-08-19 16:20                         ` Liming Gao
2020-08-19 17:18                           ` Laszlo Ersek
2020-08-19 13:36                   ` Laszlo Ersek
2020-08-19 14:56                     ` Abner Chang
2020-08-19 13:25                 ` Abner Chang

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=CS1PR8401MB11446502214D6FCC41D446D2FF5D0@CS1PR8401MB1144.NAMPRD84.PROD.OUTLOOK.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