All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
	Dmitry Shmidt <dimitrysh@google.com>,
	Nicolas Dechense <nicolas.dechesne@linaro.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	Daniel Thompson <daniel.thompson@linaro.org>,
	Loic Poulain <loic.poulain@linaro.org>
Subject: Re: Revisiting Devicetree Overlay Manager
Date: Wed, 25 Apr 2018 10:30:16 -0700	[thread overview]
Message-ID: <CALAqxLUcHtjEix9qcSU0yF-ymKBvk8f4DjUY=ci_Hq1++twktw@mail.gmail.com> (raw)
In-Reply-To: <20180419143804.brdgezjaxqalarum@linaro.org>

On Thu, Apr 19, 2018 at 7:38 AM, Manivannan Sadhasivam
<manivannan.sadhasivam@linaro.org> wrote:
> Hello Everyone,
>
> I have just started working on the Devicetree Overlay Manager support in
> kernel. The idea is to merge overlays at boot time specified via some
> interface like kernel command line. The motivation for this work comes from
> Overlay Manager [1] submitted by John last year. The mechanism which I have
> been working on is an extension to John's work. It focusses on addressing

Just a quick correction here: I only submitted the work last year, the
overlay manager work is all by Dmitry Shmidt.

thanks
-john

      parent reply	other threads:[~2018-04-25 17:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 14:38 Revisiting Devicetree Overlay Manager Manivannan Sadhasivam
2018-04-25  7:34 ` Manivannan Sadhasivam
2018-04-25 17:26   ` Frank Rowand
2018-05-18  3:53     ` Frank Rowand
2018-05-22 19:32       ` Alan Tull
2018-05-22 21:13         ` Frank Rowand
2018-04-25 17:30 ` John Stultz [this message]

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='CALAqxLUcHtjEix9qcSU0yF-ymKBvk8f4DjUY=ci_Hq1++twktw@mail.gmail.com' \
    --to=john.stultz@linaro.org \
    --cc=daniel.thompson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dimitrysh@google.com \
    --cc=frowand.list@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=loic.poulain@linaro.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=nicolas.dechesne@linaro.org \
    --cc=pantelis.antoniou@konsulko.com \
    --cc=robh+dt@kernel.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.