From: Patrick Williams <patrick@stwcx.xyz>
To: TOM JOSEPH <tomjose@linux.vnet.ibm.com>
Cc: "Mauery, Vernon" <vernon.mauery@intel.com>,
benjaminfair@google.com,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
anoo@us.ibm.com, Brad Bishop <bradleyb@fuzziesquirrel.com>
Subject: Re: IPMI implementation of Get Device ID command
Date: Mon, 24 Aug 2020 16:27:02 -0500 [thread overview]
Message-ID: <20200824212702.GD3532@heinlein> (raw)
In-Reply-To: <4cde2763-88b0-447b-1aba-5bb884fae251@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
On Mon, Aug 24, 2020 at 05:27:55PM +0530, TOM JOSEPH wrote:
> My proposal is to add major and minor version to the dev_id.json and
> this can be populated in the meta-xxx layer (something like this
> https://github.com/openbmc/openbmc/blob/master/meta-ibm/recipes-phosphor/ipmi/phosphor-ipmi-config.bbappend).
> If the format of the VERSION_ID does not match the master tag format,
> then major and minor version will be picked from the dev_id.json. With
> this approach every company can share the upstream implementation of the
> command. Thoughts?
Hi Tom,
Would you be able to work out an example where the git-describe is used
to create this, similar to what we do with os-release? I think this is
going to be the typical use case and we had a huge trouble getting
os-release to be done "correctly" at the beginning. I think having a
well-tested example to copy from should limit the issues others will
have in trying to implement their own.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-08-24 21:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 17:34 IPMI implementation of Get Device ID command TOM JOSEPH
2020-08-14 21:48 ` Patrick Williams
2020-08-14 22:26 ` Benjamin Fair
2020-08-14 23:11 ` Mauery, Vernon
2020-08-24 11:57 ` TOM JOSEPH
2020-08-24 17:31 ` Benjamin Fair
2020-08-24 21:27 ` Patrick Williams [this message]
2020-09-01 12:53 ` TOM JOSEPH
2020-09-01 16:27 ` 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=20200824212702.GD3532@heinlein \
--to=patrick@stwcx.xyz \
--cc=anoo@us.ibm.com \
--cc=benjaminfair@google.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=tomjose@linux.vnet.ibm.com \
--cc=vernon.mauery@intel.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.