public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>
Subject: Re: FW: [PATCH v2 2/3] MdePkg: Support FDT library.
Date: Thu, 13 Apr 2023 19:31:43 +0100	[thread overview]
Message-ID: <CAKbZUD0Q8RFO-cVD=VzJthmxEAwjkxj8MRxY9u0H69KKLfHxog@mail.gmail.com> (raw)
In-Reply-To: <CAKbZUD1D5s7DdJ-bTquZHZKQ1t1DJL-UXhKHk58V+-zVVT_rdg@mail.gmail.com>

+CC edk2-devel, It seems that you dropped it accidentally.

On Thu, Apr 13, 2023 at 7:30 PM Pedro Falcato <pedro.falcato@gmail.com> wrote:
>
> On Thu, Apr 13, 2023 at 5:53 PM Kinney, Michael D
> <michael.d.kinney@intel.com> wrote:
> >
> > Hi Pedro,
> >
> > Any comments in this new version?  Have your concerns been addressed, especially libc conformance.
> >
> > Mike
>
> Mike,
>
> I'm really sorry but I'm dealing with serious personal issues so I
> can't give you much feedback
>
> However I skimmed through the patch and it looks okay to me, if you
> add my copyright to the file with the libc implementations (as those
> were taken from LibcLib's patch). And possibly my signed-off-by but
> I'll leave that to your criteria.
>
> I still don't see much point in the libfdt wrapping code. Benny says
> it's due to EDK2 style, you say it's for stability/modularity reasons.
> I personally don't see much point in writing whole wrappers due to
> style, and libfdt is AIUI very much something  that has been mostly
> stable over time. In any case, do what you think is best. I'll trust
> your judgement and I won't block this patch for it.
>
> So with all that addressed, Acked-by: Pedro Falcato <pedro.falcato@gmail.com>
>
> Thank you,
> Pedro



-- 
Pedro

  parent reply	other threads:[~2023-04-13 18:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 18:36 [PATCH v2 0/3] Support FDT library Benny Lin
2023-04-12 18:36 ` [PATCH v2 1/3] Tianocore: " Benny Lin
2023-04-18 17:17   ` Leif Lindholm
2023-04-12 18:36 ` [PATCH v2 2/3] MdePkg: " Benny Lin
     [not found]   ` <CO1PR11MB49294AA24E91272B15E634EFD2989@CO1PR11MB4929.namprd11.prod.outlook.com>
     [not found]     ` <CAKbZUD1D5s7DdJ-bTquZHZKQ1t1DJL-UXhKHk58V+-zVVT_rdg@mail.gmail.com>
2023-04-13 18:31       ` Pedro Falcato [this message]
2023-04-14 13:03         ` [edk2-devel] FW: " Benny Lin
2023-04-12 18:36 ` [PATCH v2 3/3] .pytool: " Benny Lin

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='CAKbZUD0Q8RFO-cVD=VzJthmxEAwjkxj8MRxY9u0H69KKLfHxog@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