All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Kerr <jk@ozlabs.org>
To: openbmc@lists.ozlabs.org
Subject: DBUS interface documentation
Date: Mon, 11 Jan 2016 18:20:30 +1100	[thread overview]
Message-ID: <569357BE.1030403@ozlabs.org> (raw)

Hi all,

We're building up quite a collection of dbus interfaces for OpenBMC, but 
our interface documentation is disappointingly sparse:

   https://github.com/openbmc/docs/blob/master/dbus-interfaces.md

If you've implemented (or are implementing) a DBUS API, could you also 
submit a pull request to update this document with the new API?

This will also allow us to have a bit of a review of the new interfaces 
before they're committed.

Regards,


Jeremy

             reply	other threads:[~2016-01-11  7:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11  7:20 Jeremy Kerr [this message]
2016-01-12  0:57 ` DBUS interface documentation Stewart Smith

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=569357BE.1030403@ozlabs.org \
    --to=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.