From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mx.groups.io with SMTP id smtpd.web11.5507.1624442565032206099 for ; Wed, 23 Jun 2021 03:02:45 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=FwSYtsce; spf=pass (domain: redhat.com, ip: 216.205.24.124, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1624442564; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=AfraQVx7MtVYjmh8wBl0eHQkQmejVWJ3uIfvLFyZ6VE=; b=FwSYtsceG6dfPXVq9DbE7ymEoiz50pTWB89n4OwY0pJ14STPHzp0iOAOJ4BT+Z7qCOj7Nf 3Kz5et4Aktj76Vg0ocU9o29s6k5UzU9PMUdBm7z/GONmEh2QdGoh6R0hgT8dW4dLJRvvYb i3Cdd633zGCV0l2rv1Lzx2tTBT9/NZw= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-407-ffd-Kr0mOfaJV9DgquJtjg-1; Wed, 23 Jun 2021 06:02:40 -0400 X-MC-Unique: ffd-Kr0mOfaJV9DgquJtjg-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 680D2801B0A; Wed, 23 Jun 2021 10:02:38 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-112-200.ams2.redhat.com [10.36.112.200]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 31BF019D7C; Wed, 23 Jun 2021 10:02:35 +0000 (UTC) Subject: Re: [edk2-devel] [PATCH v2 1/6] EDK2 Code First: PI Specification: EFI_MM_COMMUNICATE_HEADER Update To: devel@edk2.groups.io, kuqin12@gmail.com Cc: Michael D Kinney , Liming Gao , Zhiguang Liu , Andrew Fish , Leif Lindholm , Hao A Wu References: <20210618090243.2517-1-kuqin12@gmail.com> <20210618090243.2517-2-kuqin12@gmail.com> From: "Laszlo Ersek" Message-ID: <82e2e6ef-2334-0b12-2b5d-27aa8fdac783@redhat.com> Date: Wed, 23 Jun 2021 12:02:34 +0200 MIME-Version: 1.0 In-Reply-To: <20210618090243.2517-2-kuqin12@gmail.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=lersek@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 06/18/21 11:02, Kun Qin wrote: > REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3430 > > This change includes specification update markdown file that describes > the proposed PI Specification v1.7 Errata A in detail and potential > impact to the existing codebase. > > Cc: Michael D Kinney > Cc: Liming Gao > Cc: Zhiguang Liu > Cc: Andrew Fish > Cc: Laszlo Ersek > Cc: Leif Lindholm > Cc: Hao A Wu > > Signed-off-by: Kun Qin > --- > > Notes: > v2: > - Updated change impact analysis regarding SmmLockBoxDxeLib [Hao] > > BZ3430-SpecChange.md | 90 ++++++++++++++++++++ > 1 file changed, 90 insertions(+) Placing such a document in the edk2 root directory looks very strange to me. https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Code-First-Process#tianocore-github [...] Specification text changes are held within the affected source repository, using the GitHub flavor of markdown, in a file (or split across several files) with .md suffix [...] The wiki does not seem to specify what directory should contain the spec change document. Should we create a "CodeFirst" top-level directory? Thanks, Laszlo