All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: Jeremy Kerr <jk@ozlabs.org>
Cc: Emily Shaffer <emilyshaffer@google.com>,
	David Thompson <dthompson@mellanox.com>,
	openbmc <openbmc@lists.ozlabs.org>,
	Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>,
	"Naidoo, Nilan" <nilan.naidoo@intel.com>,
	Dong Wei <Dong.Wei@arm.com>
Subject: Re: Initial MCTP design proposal
Date: Mon, 11 Feb 2019 13:57:36 -0500	[thread overview]
Message-ID: <20190211185736.dafbfc74n76r33pu@thinkpad.dyn.fuzziesquirrel.com> (raw)
In-Reply-To: <2159944d88eadddab4e7dfa5b50c85a4fc0ca234.camel@ozlabs.org>

>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!

There was some interest in performing a formal code review on Gerrit of
what you have written thus far (or intend to distribute).

To that end I could create an initial empty repository in the openbmc
namespace and you could push your tree there for review, when you are
ready.  How does that sound?

  parent reply	other threads:[~2019-02-11 18:57 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
2019-02-11 18:57     ` Brad Bishop [this message]
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=20190211185736.dafbfc74n76r33pu@thinkpad.dyn.fuzziesquirrel.com \
    --to=bradleyb@fuzziesquirrel.com \
    --cc=Dong.Wei@arm.com \
    --cc=Supreeth.Venkatesh@arm.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.