All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sai Dasari <sdasari@fb.com>
To: Andrew Geissler <geissonator@gmail.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Stewart Smith <stewart@linux.vnet.ibm.com>,
	Joel Stanley <joel.stan@gmail.com>, Jeremy Kerr <jk@ozlabs.org>
Subject: Re: OpenBMC Hackathon @ OpenPower Summit?
Date: Tue, 18 Sep 2018 21:13:52 +0000	[thread overview]
Message-ID: <16FCAE4F-97EB-4D32-BB14-5C24578773A6@fb.com> (raw)
In-Reply-To: <CALLMt=p+dH3e-C2M8L9Zv43vTDw9rcd9MpfcqFXge2aTkzk6Hw@mail.gmail.com>



On 9/18/18, 1:21 PM, "Andrew Geissler" <geissonator@gmail.com> wrote:

    
    Hey Sai, looks like Stewart, Joel, Jeremy, and myself will all be attending.
    
    We're just building the agenda now but we were thinking some basic
    overviews, then some kernel hacking, SDK/QEMU hacking (systemd,
    journald, service intros), and some customization hacking (adding new
    machine layer, customizing web UI for your system).  Any other
    thoughts/ideas from the group appreciated.  The overall goal is to
    teach people unfamiliar with openbmc how to dive in and start hacking
    at it. The OpenBMC community hackathon will be at the Intel summit
    middle of next month up in Oregon.
Thanks Andrew! Overall goal is awesome and look forward to meet at summit!
    
    
    


  reply	other threads:[~2018-09-18 21:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-18 19:55 OpenBMC Hackathon @ OpenPower Summit? Sai Dasari
2018-09-18 20:20 ` Andrew Geissler
2018-09-18 21:13   ` Sai Dasari [this message]
2018-09-25 14:24     ` Andrew Geissler
2018-09-25 17:16       ` Sai Dasari
2018-10-04  9:03         ` OpenBMC on OCP Leopard server Jean-Marie Verdun
2018-10-05  0:29           ` Sai Dasari

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=16FCAE4F-97EB-4D32-BB14-5C24578773A6@fb.com \
    --to=sdasari@fb.com \
    --cc=geissonator@gmail.com \
    --cc=jk@ozlabs.org \
    --cc=joel.stan@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=stewart@linux.vnet.ibm.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.