From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: Evan Lloyd <Evan.Lloyd@arm.com>,
"edk2-devel (edk2-devel@lists.01.org)" <edk2-devel@lists.01.org>,
Leif Lindholm <leif.lindholm@linaro.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [staging/DynamicTables] What about edk2-platforms.
Date: Fri, 15 Dec 2017 01:43:58 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5A7DEDE64@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <AM4PR0801MB1444C38FA12D7A592E2B0EEB8B0A0@AM4PR0801MB1444.eurprd08.prod.outlook.com>
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.
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) <edk2-
> devel@lists.01.org>; Leif Lindholm
> <leif.lindholm@linaro.org>
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> 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
next prev parent reply other threads:[~2017-12-15 1:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 18:38 [staging/DynamicTables] What about edk2-platforms Evan Lloyd
2017-12-15 1:43 ` Kinney, Michael D [this message]
2017-12-15 9:40 ` Ard Biesheuvel
2017-12-15 13:12 ` Leif Lindholm
2017-12-15 17:19 ` Kinney, Michael D
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=E92EE9817A31E24EB0585FDF735412F5A7DEDE64@ORSMSX113.amr.corp.intel.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