All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve McIntyre <steve.mcintyre-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: "Mills, William" <wmills-l0cyMroinI0@public.gmane.org>
Cc: "devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"dte-all-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
	<dte-all-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	"Kristo, Tero" <t-kristo-l0cyMroinI0@public.gmane.org>,
	"Valkeinen, Tomi" <tomi.valkeinen-l0cyMroinI0@public.gmane.org>,
	"Menon, Nishanth" <nm-l0cyMroinI0@public.gmane.org>,
	"Murphy, Dan" <dmurphy-l0cyMroinI0@public.gmane.org>,
	"tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org"
	<tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
	"tom.rini-OWPKS81ov/FWk0Htik3J/w@public.gmane.org"
	<tom.rini-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
Subject: Re: Device Tree Evolution Project - call notes - 29th January
Date: Mon, 10 Feb 2020 18:30:51 +0000	[thread overview]
Message-ID: <20200210183051.GC18978@linaro.org> (raw)
In-Reply-To: <3b257f2a0ccc4f9f9ca0be2de8c9e382-l0cyMroinI0@public.gmane.org>

On Mon, Feb 10, 2020 at 04:58:26PM +0000, William Mills wrote:
>Steve,
>
>Can TI get on the agenda for this week's meeting?
>
>We have a simple approach to make progress on boot loader applied overlays.
>It is a small repo with just the overlays.
>It builds the dtb's from the upstream kernel repo and the overlays from this repo.
>We are going to do this at git.ti.com so we can make progress.
>However we would like to suggest this as a simple way forward to collectively host things the kernel maintainers do not want in the kernel.
>Does it make sense to host something like this in devicetree.org github account?

I think so, yes - I see Grant has already responded there.

>I think this is a very reasonable way forward and more practical than:
>* moving all DT's out of the kernel (or sync'ing two homes etc)
>* reworking overlay support to be the "one final good way"
>* everyone keeping this stuff in their own vendor trees, each doing something different and generating N solutions
>
>We will push the repo somewhere public before the meeting.

Cool. :-)

>(CC'ing Tom and Tony does not constituent their endorsement, we are starting to talk with them now also)

ACK!

Cheers,
-- 
Steve McIntyre                                steve.mcintyre-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs


  parent reply	other threads:[~2020-02-10 18:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-30 13:56 Device Tree Evolution Project - call notes - 29th January Steve McIntyre
     [not found] ` <20200130135605.GQ3697-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2020-02-10 16:58   ` Mills, William
     [not found]     ` <3b257f2a0ccc4f9f9ca0be2de8c9e382-l0cyMroinI0@public.gmane.org>
2020-02-10 17:51       ` Grant Likely
2020-02-10 18:30       ` Steve McIntyre [this message]
2020-02-11 16:31       ` Rob Herring
     [not found]         ` <CAL_JsqLNHi0ac0E5k9-355vS_GObz7Tu5Av2FLKZ6b-1wjm1Jw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-02-11 16:37           ` Tony Lindgren
2020-02-11 17:44           ` Francois Ozog
     [not found]             ` <CAHFG_=UhJzrBqZy1+-Jm0uKaCN+SMgXKryWG17xN=29s1W2Umw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-02-11 21:24               ` Tom Rini
2020-02-11 21:53               ` Rob Herring
     [not found]                 ` <CAL_JsqKR5RC+B-vjY3a5pyBnGBgXianh3FPLvfTm9m5p8WUKxA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-02-12  0:27                   ` William Mills
2020-02-12  2:49           ` Frank Rowand
     [not found]             ` <36cb9cd4-542e-c8da-9615-f26d6ee3e44e-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-02-12 14:54               ` Francois Ozog

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=20200210183051.GC18978@linaro.org \
    --to=steve.mcintyre-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
    --cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=dmurphy-l0cyMroinI0@public.gmane.org \
    --cc=dte-all-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=nm-l0cyMroinI0@public.gmane.org \
    --cc=t-kristo-l0cyMroinI0@public.gmane.org \
    --cc=tom.rini-OWPKS81ov/FWk0Htik3J/w@public.gmane.org \
    --cc=tomi.valkeinen-l0cyMroinI0@public.gmane.org \
    --cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org \
    --cc=wmills-l0cyMroinI0@public.gmane.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.