From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Permerror (SPF Permanent Error: More than 10 MX records returned) identity=mailfrom; client-ip=192.55.52.151; helo=mga17.intel.com; envelope-from=michael.d.kinney@intel.com; receiver=edk2-devel@lists.01.org Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 026682216D8D0 for ; Thu, 14 Dec 2017 17:39:18 -0800 (PST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Dec 2017 17:44:00 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,402,1508828400"; d="scan'208";a="13639350" Received: from orsmsx103.amr.corp.intel.com ([10.22.225.130]) by fmsmga001.fm.intel.com with ESMTP; 14 Dec 2017 17:44:00 -0800 Received: from orsmsx153.amr.corp.intel.com (10.22.226.247) by ORSMSX103.amr.corp.intel.com (10.22.225.130) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 14 Dec 2017 17:43:59 -0800 Received: from orsmsx113.amr.corp.intel.com ([169.254.9.187]) by ORSMSX153.amr.corp.intel.com ([169.254.12.223]) with mapi id 14.03.0319.002; Thu, 14 Dec 2017 17:43:59 -0800 From: "Kinney, Michael D" To: Evan Lloyd , "edk2-devel (edk2-devel@lists.01.org)" , Leif Lindholm , "Kinney, Michael D" CC: Ard Biesheuvel Thread-Topic: [edk2] [staging/DynamicTables] What about edk2-platforms. Thread-Index: AdN1CMoRkII2k+qYRWmRzAqmJ7nE3AAPLNEw Date: Fri, 15 Dec 2017 01:43:58 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.22.254.138] MIME-Version: 1.0 Subject: Re: [staging/DynamicTables] What about edk2-platforms. X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Dec 2017 01:39:19 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Evan, This is a good question. Another staging repo is possible, but may not be required. You could add the platform content to edk2-staging and get=20 everything working using that content. When edk2-staging=20 is ready for truck, you need to create the patches for the edk2 and edk2-platforms repos for review and commit. I think you can use filter-branch to extract the patch sets for each repo. Mike > -----Original Message----- > From: edk2-devel [mailto:edk2-devel- > bounces@lists.01.org] On Behalf Of Evan Lloyd > Sent: Thursday, December 14, 2017 10:38 AM > To: edk2-devel (edk2-devel@lists.01.org) devel@lists.01.org>; Leif Lindholm > > Cc: Ard Biesheuvel > Subject: [edk2] [staging/DynamicTables] What about > edk2-platforms. >=20 > We are about to submit a new (ACPI 6.2) version of > Sami's Dynamic Tables module. > As suggested in previous threads, the aim is to submit > it to edk2-staging. > To that end, following the instructions at > https://github.com/tianocore/edk2- > staging/blob/about/README > (paragraph 4 a) "Maintainer sends patch email to edk2- > devel", we need to generate a patch. >=20 > The problem is that the patch involves modules in both > edk2 and edk2-platforms. > What is the best strategy to use for that scenario? > Is there any plan to have an edk2-platforms-staging? > If not, we could roll the bits of platforms into edk2- > staging, but that may engender problems later. > Does anyone have any advice on how best to handle this, > please? >=20 > Regards, > Evan > IMPORTANT NOTICE: The contents of this email and any > attachments are confidential and may also be > privileged. If you are not the intended recipient, > please notify the sender immediately and do not > disclose the contents to any other person, use it for > any purpose, or store or copy the information in any > medium. Thank you. > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel