All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Joshua Watt <jpewhacker@gmail.com>
Cc: meta-ti@yoctoproject.org, "Mertz, Timothy" <timothy.mertz@garmin.com>
Subject: Re: [morty][PATCH v2] Make ti-xdctools a native recipe
Date: Fri, 15 Dec 2017 17:59:46 -0500	[thread overview]
Message-ID: <20171215225945.GD361@edge> (raw)
In-Reply-To: <1513039988.18435.4.camel@gmail.com>

On Mon, Dec 11, 2017 at 06:53:08PM -0600, Joshua Watt wrote:
> On Mon, 2017-12-11 at 17:39 -0500, Denys Dmytriyenko wrote:
> > Thanks! Can you please detail the changes between v1 and v2 of the
> > patch? We 
> > are still investigating v1 of the patch and how it affects our
> > releases...
> 
> Sorry, just rebased and took the opertunity to add the branch specifier
> (morty) to the patch subject since I forgot it the first time. There
> are no functional changes.

Thanks, have you tried building anything with this change?

Right off the bat it breaks ipumm-fw, as it expects xdctools to reside in the 
same sysroot as BIOS, which is the target one. Fixing it.

Also, I'm making corresponding changes in meta-arago, which uses xdctools as 
well. Hopefully there's not much breakage there...

-- 
Denys


  reply	other threads:[~2017-12-15 23:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28 19:58 Make ti-xdctools a native recipe Joshua Watt
2017-12-04 14:08 ` Joshua Watt
2017-12-11 22:28 ` [morty][PATCH v2] " Joshua Watt
2017-12-11 22:39   ` Denys Dmytriyenko
2017-12-12  0:53     ` Joshua Watt
2017-12-15 22:59       ` Denys Dmytriyenko [this message]
2017-12-16  0:09         ` Joshua Watt
2017-12-18 18:08           ` Denys Dmytriyenko
2017-12-18 18:50             ` Joshua Watt

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=20171215225945.GD361@edge \
    --to=denys@ti.com \
    --cc=jpewhacker@gmail.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=timothy.mertz@garmin.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 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.