All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Brad Bishop <brad@bwbmail.net>
Cc: openbmc@lists.ozlabs.org
Subject: Re: BSP layers
Date: Tue, 29 Sep 2015 09:44:51 -0500	[thread overview]
Message-ID: <20150929144451.GF14293@asimov.ibm.com> (raw)
In-Reply-To: <722865DA-D254-4972-9020-E6D01F95EC60@bwbmail.net>

[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]

On Fri, Sep 25, 2015 at 02:47:59PM -0400, Brad Bishop wrote:
> I have a couple new layer repositories:
> 
> https://github.com/bradbishop/meta-aspeed <https://github.com/bradbishop/meta-aspeed>
> https://github.com/bradbishop/meta-openpower <https://github.com/bradbishop/meta-openpower>
> 
> Appreciate any feedback.
> 
> Thx! - brad
> 

Brad,

I noticed in the layer.conf files we are manually assigning priority.
Do we want to allow the automatic assignment or is there some guidelines
on what the priority should be?

Seems that you have:
    * BMC Hardware Layer - 7
    * Host Machine Class - 8
    * Host Machine Specific - 9
    * OEM Machine Enhancment - 10 (not there, but imagined by me).

Based on the conference call we had last week, I think we should go
ahead and make github.com/openbmc repositories for these two you have.
I can create that if you want.

What is your proposal for where these repositories live in
openbmc/openbmc?  meta-openbmc-bsp for meta-aspeed?  I'm unsure if
meta-openpower belongs under a meta-openbmc-machines or
meta-phosphor/meta-machines?

-- 
Patrick Williams

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-09-29 14:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25 18:47 BSP layers Brad Bishop
2015-09-29 14:44 ` Patrick Williams [this message]
2015-09-29 17:42   ` Brad Bishop
2015-09-30  0:44 ` Joel Stanley
2015-10-01  0:02   ` Brad Bishop
2015-10-15  5:58     ` Joel Stanley
2015-10-15  6:28       ` Joel Stanley

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-all 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=20150929144451.GF14293@asimov.ibm.com \
    --to=patrick@stwcx.xyz \
    --cc=brad@bwbmail.net \
    --cc=openbmc@lists.ozlabs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.