From: Supreeth Venkatesh <supreeth.venkatesh@arm.com>
To: Deepak Kodihalli <dkodihal@linux.vnet.ibm.com>,
Jeremy Kerr <jk@ozlabs.org>, "Tanous, Ed" <ed.tanous@intel.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Initial MCTP design proposal
Date: Thu, 07 Mar 2019 14:40:27 -0600 [thread overview]
Message-ID: <fe67a0a67bf7208a1a8be74d1f737fc37aea96b1.camel@arm.com> (raw)
In-Reply-To: <76923984-3d27-581b-0541-ae571a441e2d@linux.vnet.ibm.com>
On Thu, 2019-03-07 at 14:16 +0530, Deepak Kodihalli wrote:
> On 07/03/19 1:34 AM, Ed Tanous wrote:
> >
> > On 2/12/19 12:43 AM, Jeremy Kerr wrote:
> > > > 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?
> >
> > I would like to see this happen. Once it does, I'll likely push
> > reviews
> > for the commits in this tree to it (which includes both Jeremys
> > commits
> > as well as my own.
> > https://github.com/edtanous/libmctp/commits/pr1
> >
> >
> > >
> > > Yep, I'd be happy to do this when we decide on a good time to do
> > > the
> > > reviews.
> >
> > I vote the time is now. Any objections?
+1
>
> I agree to this as well. I've got two PLDM stacks on my laptop
> (requester and responder) talking to each other over libmctp (over
> the
> serial binding - making use of fifos instead of an actual serial
> connection). I'd like to push a couple small commits to libmctp as
> well
> (I made a PR for one of them at the moment).
>
> Regards,
> Deepak
>
Thanks,
Supreeth
next prev parent reply other threads:[~2019-03-07 20:40 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
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 [this message]
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=fe67a0a67bf7208a1a8be74d1f737fc37aea96b1.camel@arm.com \
--to=supreeth.venkatesh@arm.com \
--cc=dkodihal@linux.vnet.ibm.com \
--cc=ed.tanous@intel.com \
--cc=jk@ozlabs.org \
--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.