All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
	Denys Dmytriyenko <denys@ti.com>
Subject: Re: [PATCH] u-boot: update to version 2014.07
Date: Tue, 16 Sep 2014 19:23:06 -0400	[thread overview]
Message-ID: <20140916232306.GX2480@denix.org> (raw)
In-Reply-To: <CAP9ODKqbfGW2FkmtTwMA08PL+Gu2AmYaFTJysYUExXXo5F3_mw@mail.gmail.com>

On Mon, Sep 15, 2014 at 11:41:22AM -0300, Otavio Salvador wrote:
> On Mon, Sep 15, 2014 at 11:36 AM, Burton, Ross <ross.burton@intel.com> wrote:
> > On 15 September 2014 15:33, Otavio Salvador <otavio@ossystems.com.br> wrote:
> >> I think it is a way better base for work but I really don't care as I
> >> use my own recipe in fsl-arm and so does TI.
> >
> > And that's the problem really isn't it. :)  Why do you both use your
> > own recipe, instead of keeping the u-boot in oe-core up to date?

The way we use it in meta-ti, is to include u-boot.inc file and add any SRCREV 
bumps or patches on top. So, the base gets reused.


> Well we both require patches; this does not mean we ought to not keep
> OE-Core in sync (or close to).
> 
> This is the reason why I advocate for the inclusion. Denys were
> working on this update for a while but he must have been pulled out of
> it due work commitments as usual ... so it ended sent now.

Correct. I meant to finish and submit it last month, but got pulled into 
resolving other critical issues, hence the delay, sorry.

I've submitted a v2 version that splits the changes into 2 patches - cleanup 
and update. Please provide comments.

-- 
Denys


  reply	other threads:[~2014-09-16 23:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-14  3:34 [PATCH] u-boot: update to version 2014.07 Denys Dmytriyenko
2014-09-14 21:40 ` Burton, Ross
2014-09-15 13:33   ` Otavio Salvador
2014-09-15 13:33     ` Otavio Salvador
2014-09-15 14:21     ` Burton, Ross
2014-09-15 14:33       ` Otavio Salvador
2014-09-15 14:36         ` Burton, Ross
2014-09-15 14:41           ` Otavio Salvador
2014-09-16 23:23             ` Denys Dmytriyenko [this message]
2014-11-05 14:56 ` Burton, Ross
2014-11-05 15:09   ` Burton, Ross
2014-11-07 19:43     ` Denys Dmytriyenko
2014-11-07 19:41   ` Denys Dmytriyenko
2014-11-07 20:43     ` Burton, Ross
2014-11-07 20:52       ` Otavio Salvador
2014-11-07 20:54       ` Denys Dmytriyenko
2014-11-07 22:30         ` Denys Dmytriyenko
2014-11-09 22:57           ` Burton, Ross
2016-07-10 16:49           ` Venkatesh
2016-07-10 21:28             ` Denys Dmytriyenko

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=20140916232306.GX2480@denix.org \
    --to=denis@denix.org \
    --cc=denys@ti.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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.