public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Pantelis Antoniou <panto@antoniou-consulting.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] Introducing Device Tree Overlays
Date: Fri, 28 Jun 2013 19:38:23 -0700	[thread overview]
Message-ID: <20130629023703.GA12849@roeck-us.net> (raw)
In-Reply-To: <1357327870-13615-1-git-send-email-panto@antoniou-consulting.com>

On Fri, Jan 04, 2013 at 09:31:04PM +0200, Pantelis Antoniou wrote:
> The following patchset introduces Device Tree overlays, a method
> of dynamically altering the kernel's live Device Tree.
> 
> This patchset is against mainline as of Friday Jan 4 2013.
> (4956964 Merge tag 'driver-core-3.8-rc2' of \
>  	git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core)
> 
> Note that a separate patch for the DTC compiler has been posted and
> is required to compile the DTS files according to the documentation.
> The patch is "dtc: Dynamic symbols & fixup support"
> 
> An implementation patchset for a beaglebone cape loader will follow,
> but if you want to check out a working kernel for the beaglebone please
> pull from:
> 
> git://github.com/pantoniou/linux-bbxm.git branch not-capebus-v8
> 
> Pantelis Antoniou (6):
>   OF: Introduce device tree node flag helpers.
>   OF: export of_property_notify
>   OF: Export all DT proc update functions
>   OF: Introduce utility helper functions
>   OF: Introduce Device Tree resolve support.
>   OF: Introduce DT overlay support.
> 
Hi Pantelis,

do you have an update of this patchset ? I want to seriously start testing it.
Digging through your tree on github is a bit cumbersome, and I am not sure
if I got all patches. It would also be nice to get an update with all the
comments addressed.

Thanks,
Guenter

  parent reply	other threads:[~2013-06-29  2:38 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04 19:31 [PATCH 0/6] Introducing Device Tree Overlays Pantelis Antoniou
2013-01-04 19:31 ` [PATCH 1/6] OF: Introduce device tree node flag helpers Pantelis Antoniou
2013-01-04 19:31 ` [PATCH 2/6] OF: export of_property_notify Pantelis Antoniou
2013-01-04 19:31 ` [PATCH 3/6] OF: Export all DT proc update functions Pantelis Antoniou
2013-03-16  9:45   ` Grant Likely
2013-03-19 11:42     ` Pantelis Antoniou
2013-03-19 17:08       ` Grant Likely
2013-03-16  9:53   ` Grant Likely
2013-01-04 19:31 ` [PATCH 4/6] OF: Introduce utility helper functions Pantelis Antoniou
2013-01-04 19:31 ` [PATCH 5/6] OF: Introduce Device Tree resolve support Pantelis Antoniou
2013-01-21  4:48   ` David Gibson
2013-01-21 10:59     ` Pantelis Antoniou
2013-01-22  4:05       ` David Gibson
2013-01-22 11:06         ` Pantelis Antoniou
2013-01-23  4:40           ` David Gibson
2013-01-23 10:58             ` Pantelis Antoniou
2013-03-16  9:24               ` Grant Likely
2013-03-19 11:51                 ` Pantelis Antoniou
2013-03-19 17:18                   ` Grant Likely
2013-03-21  9:12                     ` Pantelis Antoniou
2013-01-04 19:31 ` [PATCH 6/6] OF: Introduce DT overlay support Pantelis Antoniou
2013-01-06  2:24   ` Rob Landley
2013-01-07 10:45     ` Pantelis Antoniou
2013-01-22  3:50   ` David Gibson
2013-01-22 11:08     ` Pantelis Antoniou
2013-01-23  5:12       ` David Gibson
2013-01-23 11:01         ` Pantelis Antoniou
2013-01-25  2:34           ` David Gibson
2013-01-05  3:35 ` [PATCH 0/6] Introducing Device Tree Overlays Richard Cochran
2013-01-05  6:16   ` Joel A Fernandes
2013-01-05  9:35     ` Richard Cochran
2013-01-05 10:13       ` Pantelis Antoniou
2013-01-06  4:37       ` Rob Landley
2013-02-21 21:25 ` delicious quinoa
2013-02-21 21:53   ` Pantelis Antoniou
2013-02-22 15:57     ` delicious quinoa
2013-06-29  2:38 ` Guenter Roeck [this message]
2013-07-01  9:46   ` Pantelis Antoniou
2013-07-02  3:55     ` Guenter Roeck
2013-07-03  8:25   ` Pantelis Antoniou

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=20130629023703.GA12849@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=panto@antoniou-consulting.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox