mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ian Campbell <ijc@hellion.org.uk>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Grant Likely <grant.likely@secretlab.ca>,
	barebox@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: Devicetree Maintenance in barebox
Date: Mon, 10 Feb 2014 11:38:32 +0000	[thread overview]
Message-ID: <1392032312.5117.49.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <20140207141028.GT8533@titan.lakedaemon.net>

On Fri, 2014-02-07 at 09:10 -0500, Jason Cooper wrote:
> Hi Sascha,
> 
> + Grant Likely, Ian Campbell, devicetree ML
> 
> This discussion started on the barebox bootloader mailinglist
> 
> On Fri, Feb 07, 2014 at 08:13:32AM +0100, Sascha Hauer wrote:
> > It's becoming more obvious that devicetree maintenance is painful
> > because we have to sync them to the kernel regularly. My hope was that
> > this would get simpler once the devicetrees get their own repository
> > outside the kernel, but it seems that won't happen anytime soon.
> 
> hmm.  Ian Campbell has a tree he is working on:
> 
>   git://xenbits.xen.org/people/ianc/device-tree-rebasing.git

This is automatically extracted out of the linux git tree (using
git-filter-branch), maintaining all the history etc. I intend to keep
this running until such a time as the DTS files are migrated out of
Linux.

For the time being though patches to this tree need to go through the
Linux tree in the normal way.

(also, as the name states it is potentially rebasing, although there
hasn't been an actual need since the early days when I was still getting
things working)

Ian.


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2014-02-10 11:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07  7:13 Sascha Hauer
2014-02-07  7:39 ` Alexander Shiyan
2014-02-07  8:47   ` Sascha Hauer
2014-02-07  9:01     ` Alexander Shiyan
2014-02-07  7:49 ` Jean-Christophe PLAGNIOL-VILLARD
2014-02-07 14:10 ` Jason Cooper
2014-02-07 17:51   ` Jean-Christophe PLAGNIOL-VILLARD
2014-02-09 17:58   ` Jon Loeliger
2014-02-10 11:35     ` Ian Campbell
2014-02-10 15:06     ` Jason Cooper
2014-02-10 11:38   ` Ian Campbell [this message]
2014-02-17 19:42 ` Jason Cooper

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=1392032312.5117.49.camel@kazak.uk.xensource.com \
    --to=ijc@hellion.org.uk \
    --cc=barebox@lists.infradead.org \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@secretlab.ca \
    --cc=jason@lakedaemon.net \
    /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