From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124])
 by mx.groups.io with SMTP id smtpd.web10.4984.1645781790754227668
 for <devel@edk2.groups.io>;
 Fri, 25 Feb 2022 01:36:31 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=XTYn86DQ;
 spf=pass (domain: redhat.com, ip: 170.10.129.124, mailfrom: kraxel@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1645781789;
	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:
	 in-reply-to:in-reply-to:references:references;
	bh=kHLNzWvh6TDA2mdGgt36pUiC71gjExHxeu5/ZoqK+oI=;
	b=XTYn86DQsdEGpCt2YWUSrsLB2CxphumFNRbwB3rgTxHs69yiOgNQ+ZSDOlDNrVlCLL7vfe
	+gqEpnL/LapfMxIuQWFIpg5RfTwlIi3UI3aQr29YevWxlM0K7jvTE3muINO4BZHqcuYXJ4
	lls/x50vYqyx5xXN1R28K4+gTJJ984I=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS
 (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 us-mta-73-T2UZr9PgOgOEd0VDOZYluQ-1; Fri, 25 Feb 2022 04:36:28 -0500
X-MC-Unique: T2UZr9PgOgOEd0VDOZYluQ-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 ED4295124;
	Fri, 25 Feb 2022 09:36:26 +0000 (UTC)
Received: from sirius.home.kraxel.org (unknown [10.39.195.81])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id A5DF72376D;
	Fri, 25 Feb 2022 09:36:26 +0000 (UTC)
Received: by sirius.home.kraxel.org (Postfix, from userid 1000)
	id D85E918003BE; Fri, 25 Feb 2022 10:36:24 +0100 (CET)
Date: Fri, 25 Feb 2022 10:36:24 +0100
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: sebastien.boeuf@intel.com
Cc: devel@edk2.groups.io, jiewen.yao@intel.com, jordan.l.justen@intel.com
Subject: Re: [PATCH v3 2/7] OvmfPkg: Xen: Use a new fdf include for the PVH ELF header
Message-ID: <20220225093624.tpqd5fkq3fwgs2sq@sirius.home.kraxel.org>
References: <cover.1645712595.git.sebastien.boeuf@intel.com>
 <1812e28c757eccc6d8cae17e2f45c9ffe5bd12e1.1645712595.git.sebastien.boeuf@intel.com>
MIME-Version: 1.0
In-Reply-To: <1812e28c757eccc6d8cae17e2f45c9ffe5bd12e1.1645712595.git.sebastien.boeuf@intel.com>
X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23
Authentication-Results: relay.mimecast.com;
	auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=kraxel@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Feb 24, 2022 at 03:28:21PM +0100, sebastien.boeuf@intel.com wrote:
> From: Sebastien Boeuf <sebastien.boeuf@intel.com>
> 
> Instead of having the PVH ELF header part of the fdf file directly, we
> move it to a dedicated include file. This is the first step in
> automating the generation of the header.
> 
> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>

Acked-by: Gerd Hoffmann <kraxel@redhat.com>