From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=2607:f8b0:4001:c0b::232; helo=mail-it0-x232.google.com; envelope-from=ard.biesheuvel@linaro.org; receiver=edk2-devel@lists.01.org Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 054A62216D8C2 for ; Fri, 15 Dec 2017 01:35:51 -0800 (PST) Received: by mail-it0-x232.google.com with SMTP id p139so18224015itb.1 for ; Fri, 15 Dec 2017 01:40:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ng5ByhYvWcrqrazcGzY/Km14/I8jinSxM/rnofwW6ME=; b=GUXcyLsdo3aKZl6t79mzx5TM9G7ofsD/Fj06AHg30t6wr/EyQmU4ktTwa3GN2aPa5a ZWHEUYFnqoO6wjIQnyv7vb1uroDYOF+TIYdcSdk73do6vtGkt4s5Y23wrazyGD1yWHhD QGZlfSWxj447OayDcTSIMYwz86BfDrp6/AxCk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ng5ByhYvWcrqrazcGzY/Km14/I8jinSxM/rnofwW6ME=; b=lBieXGhYeDDeojAim2SUdzKpKeSMrN3q4xrCjRRC8GhpbcRGEPTqU2536hcFNlVqAB T5PXjUcezvmqhk02vosYTiKV/c9FCKUs7g9T8QxSjUx53qeL54V535fcWxzE2PPJwCY/ Pi4Vg/LGrwm6Q0V9k2Nj3U7ucz67ebt6136nkjaQ540aPuNrGGjVoGx1hI0jEOllDfpZ uqpheaL3m9nv30wRjQy7rA/gm0cF1WJD39KUdzHj57WWmsjBI95XdUMjnuXZn3f5gLFq eufX/dTkm5/TNp+ENkPEpzy1MMzWICqjJiAe7YPwFvWxGKkhjtP9FcE/ZwnxGZzmFXGU xqkA== X-Gm-Message-State: AKGB3mLv401zIk4MYMweCWqTeO4LiZyOEkkxr7Y+/fn6GwEoXMsyOu/h oTzldfT7xW+DsUrEyuOF1zzcPBWPt58+9LxoixG0Iw== X-Google-Smtp-Source: ACJfBou0UhRi/0St8uyTnbz/qdwwerPnLUn4KjuPGTnnkYFbP83RX1TEB5zpzN69ary1ryGLwbxWLzzo8eLFGN3ylGI= X-Received: by 10.36.78.212 with SMTP id r203mr7481436ita.58.1513330832467; Fri, 15 Dec 2017 01:40:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.135.199 with HTTP; Fri, 15 Dec 2017 01:40:31 -0800 (PST) In-Reply-To: References: From: Ard Biesheuvel Date: Fri, 15 Dec 2017 10:40:31 +0100 Message-ID: To: "Kinney, Michael D" Cc: Evan Lloyd , "edk2-devel (edk2-devel@lists.01.org)" , Leif Lindholm 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 09:35:52 -0000 Content-Type: text/plain; charset="UTF-8" On 15 December 2017 at 02:43, Kinney, Michael D wrote: > 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 > everything working using that content. When edk2-staging > 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. > I don't think that is workable, if I understand Evan's use case correctly. The feature implementation will likely consist of core feature code (intended for edk2), and changes to existing platform code in edk2-platforms to make use of it. The only way to add this to edk2-staging is to import the entire platform from edk2-platforms to live alongside the EDK2 packages and layer the platform changes on top. >> -----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. >> >> 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. >> >> 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? >> >> 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