All of lore.kernel.org
 help / color / mirror / Atom feed
From: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>
To: Jeremy Kerr <jk@ozlabs.org>, Brad Bishop <bradleyb@fuzziesquirrel.com>
Cc: openbmc <openbmc@lists.ozlabs.org>,
	Emily Shaffer <emilyshaffer@google.com>,
	David Thompson <dthompson@mellanox.com>,
	Dong Wei <Dong.Wei@arm.com>,
	"Naidoo, Nilan" <nilan.naidoo@intel.com>,
	Deepak Kodihalli <dkodihal@linux.vnet.ibm.com>
Subject: RE: Initial MCTP design proposal
Date: Fri, 8 Feb 2019 15:55:43 +0000	[thread overview]
Message-ID: <AM4PR08MB27880C633DDB02D3E29A08DE80690@AM4PR08MB2788.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <2159944d88eadddab4e7dfa5b50c85a4fc0ca234.camel@ozlabs.org>

Jeremy,

Thanks for posting the review.
May I suggest requesting MCTP repository in OpenBMC github for effective collaboration similar to PLDM rather than using personal github repo?
This will also avoid duplicating effort and will also encourage participation from multiple contributors.

Thanks,
Supreeth

-----Original Message-----
From: Jeremy Kerr <jk@ozlabs.org>
Sent: Friday, February 8, 2019 12:48 AM
To: Brad Bishop <bradleyb@fuzziesquirrel.com>
Cc: openbmc <openbmc@lists.ozlabs.org>; Emily Shaffer <emilyshaffer@google.com>; David Thompson <dthompson@mellanox.com>; Dong Wei <Dong.Wei@arm.com>; Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>; Naidoo, Nilan <nilan.naidoo@intel.com>
Subject: Re: Initial MCTP design proposal

Hi Brad,

> Were you planning on submitting this to the docs repository as a
> design?

Yes! :)

> Do you need some help with that?

Just a nudge into doing so, which your email provided!

I've just pushed to gerrit:

  https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/18089

- this is the doc that I'd originally sent out (top of this thread), and incorporating suggestions discussed there.

In the meantime, I've mainly been working on the prototype sketches for the MCTP library, and I've just pushed that too:

  http://github.com/jk-ozlabs/libmctp

It's very prototypey at this stage, and I'm open to input and pull requests. I'm going to be quite permissive with accepting changes at this early stage...

If we go ahead with the MCTP designs, and want to use this, I'd propose moving it from my personal github repo into /openbmc/ (after suitable updates to get it into OpenBMC standards, of course). Patches welcome!

Cheers,


Jeremy

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.

  reply	other threads:[~2019-02-08 15:55 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07  2:41 Initial MCTP design proposal Jeremy Kerr
2018-12-07  4:15 ` Naidoo, Nilan
2018-12-07  5:06   ` Jeremy Kerr
2018-12-07  5:40     ` Naidoo, Nilan
2018-12-07  5:13 ` Deepak Kodihalli
2018-12-07  7:41   ` Jeremy Kerr
2018-12-07 17:09   ` Supreeth Venkatesh
2018-12-07 18:53     ` Emily Shaffer
2018-12-07 20:06       ` Supreeth Venkatesh
2018-12-07 21:19       ` Jeremy Kerr
2018-12-11  1:14       ` Stewart Smith
2018-12-11 18:26         ` Tanous, Ed
2018-12-18  0:10           ` Stewart Smith
2018-12-10  6:14     ` Deepak Kodihalli
2018-12-10 17:40       ` Supreeth Venkatesh
2018-12-11  7:38         ` Deepak Kodihalli
2018-12-12 22:50           ` Supreeth Venkatesh
2018-12-07 16:38 ` Supreeth Venkatesh
2019-02-07 15:51 ` Brad Bishop
2019-02-08  6:48   ` Jeremy Kerr
2019-02-08 15:55     ` Supreeth Venkatesh [this message]
2019-02-11 18:57     ` Brad Bishop
2019-02-12  8:43       ` Jeremy Kerr
2019-03-06 20:04         ` Ed Tanous
2019-03-07  8:46           ` Deepak Kodihalli
2019-03-07 19:35             ` Ed Tanous
2019-03-08  4:58               ` Deepak Kodihalli
2019-03-08  5:21                 ` Deepak Kodihalli
2019-03-07 20:40             ` Supreeth Venkatesh
2019-03-18 12:12           ` Brad Bishop

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=AM4PR08MB27880C633DDB02D3E29A08DE80690@AM4PR08MB2788.eurprd08.prod.outlook.com \
    --to=supreeth.venkatesh@arm.com \
    --cc=Dong.Wei@arm.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=dkodihal@linux.vnet.ibm.com \
    --cc=dthompson@mellanox.com \
    --cc=emilyshaffer@google.com \
    --cc=jk@ozlabs.org \
    --cc=nilan.naidoo@intel.com \
    --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.