public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: Evan Lloyd <Evan.Lloyd@arm.com>
Cc: "edk2-devel (edk2-devel@lists.01.org)" <edk2-devel@lists.01.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Sami Mujawar <Sami.Mujawar@arm.com>,
	Matteo Carlini <Matteo.Carlini@arm.com>
Subject: Re: [staging/DynamicTables] What about edk2-platforms.
Date: Fri, 15 Dec 2017 13:12:13 +0000	[thread overview]
Message-ID: <20171215131213.crwu2pqbjfoomvw3@bivouac.eciton.net> (raw)
In-Reply-To: <AM4PR0801MB1444C38FA12D7A592E2B0EEB8B0A0@AM4PR0801MB1444.eurprd08.prod.outlook.com>

On Thu, Dec 14, 2017 at 06:38:14PM +0000, Evan Lloyd wrote:
> 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?

As a third responder, I feel obliged to offer a third opinion.

My instinctive reaction is to set up a devel-dynamictables branch in
edk2-platforms, that rebases periodically on master and maintains
alignment as required with the edk2-staging branch.

/
    Leif


  parent reply	other threads:[~2017-12-15 13:07 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
2017-12-15  9:40   ` Ard Biesheuvel
2017-12-15 13:12 ` Leif Lindholm [this message]
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=20171215131213.crwu2pqbjfoomvw3@bivouac.eciton.net \
    --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