All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Ben_Pai@wistron.com
Cc: bradleyb@fuzziesquirrel.com, openbmc@lists.ozlabs.org,
	Claire_Ku@wistron.com, wangat@tw.ibm.com
Subject: Re: phosphor-bittware repository
Date: Mon, 11 May 2020 08:05:09 -0500	[thread overview]
Message-ID: <20200511130509.GD10214@heinlein> (raw)
In-Reply-To: <b7e1bb0b82394f8ca3a193cb9ed5c218@wistron.com>

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

Hello Ben,

On Thu, May 07, 2020 at 06:07:44AM +0000, Ben_Pai@wistron.com wrote:
> Could you please help to create a new repository for phosphor-bittware?

Out of curiousity for others who aren't aware of what 'bittware' is,
could you describe a little about this repository?  It seems to be a
hardware vendor, so it would be interesting to know what the BMC will be
doing with it.

Examples:
  * What is the overall purpose of the code in this repository?
  * Is there an existing architecture that this code will be following
    or is there some new design that you are persuing (and needs to be
    document)?
  * Are there existing phosphor-dbus-interfaces that you will be
    implementing?  Are there new dbus interfaces you are proposing to
    implement the functionality you want from this repository?

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-05-11 13:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07  6:07 phosphor-bittware repository Ben_Pai
2020-05-11 13:05 ` Patrick Williams [this message]
2020-05-12  9:09 Ben_Pai
2020-05-12 12:20 ` Patrick Williams
2020-05-19  6:47 Ben_Pai
2020-05-19 15:44 ` Patrick Williams

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=20200511130509.GD10214@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=Ben_Pai@wistron.com \
    --cc=Claire_Ku@wistron.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=wangat@tw.ibm.com \
    /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.