All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: Liz Kammer <eakammer@google.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Vernon Mauery <vernon.mauery@linux.intel.com>,
	wak@google.com
Subject: Re: sdbusplus port for host-ipmid
Date: Thu, 15 Feb 2018 11:52:35 +1030	[thread overview]
Message-ID: <CACPK8Xc1TeFAPSBuZqdy5ECdfGEpk6Yp59o06O+dt=Dzw2+X-w@mail.gmail.com> (raw)
In-Reply-To: <20180214171707.GF113334@mauery>

Hi Liz,

On Thu, Feb 15, 2018 at 3:47 AM, Vernon Mauery
<vernon.mauery@linux.intel.com> wrote:
> On 12-Feb-2018 11:01 PM, Liz Kammer wrote:
>>
>> Hi Everyone,
>>
>> Is anyone working on the sd_bus.h -> sdbusplus port for host-ipmid? I am
>> hoping to work on this issue
>> https://github.com/openbmc/phosphor-host-ipmid/issues/109, but I don't
>> want
>> to step on toes.

I was searching through gerrit for something else and came across this
patch from William:

 https://gerrit.openbmc-project.xyz/#/c/8938/

I won't assume that because you have the same domain name in your
email address that you're aware of each other's work. But perhaps you
are! Either way perhaps you and William can let us know which parts
you're working on and keep everyone on the list updated.

> I am happy to hear you are working on this. I don't know if anyone else is
> working on it or not, but I do know that host-ipmid is under very active
> development. You will have fewer collisions with others if you make and push
> incremental changes (like for one file at a time). If you push one big
> patchset, it will likely conflict with every other commit in review.

That's good advice.

Cheers,

Joel

  reply	other threads:[~2018-02-15  1:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 23:01 sdbusplus port for host-ipmid Liz Kammer
2018-02-14 17:17 ` Vernon Mauery
2018-02-15  1:22   ` Joel Stanley [this message]
2018-02-16 21:10     ` Liz Kammer

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='CACPK8Xc1TeFAPSBuZqdy5ECdfGEpk6Yp59o06O+dt=Dzw2+X-w@mail.gmail.com' \
    --to=joel@jms.id.au \
    --cc=eakammer@google.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=vernon.mauery@linux.intel.com \
    --cc=wak@google.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.