From: Denys Dmytriyenko <denys@ti.com>
To: Jacob Stiffler <j-stiffler@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [RFC 0/2] LLD cleanup and device split
Date: Thu, 29 Oct 2015 10:31:35 -0400 [thread overview]
Message-ID: <20151029143135.GB8780@edge> (raw)
In-Reply-To: <5632115B.4080604@ti.com>
On Thu, Oct 29, 2015 at 08:30:19AM -0400, Jacob Stiffler wrote:
> Any comments?
>
> If not, I will submit similar patches for all of the LLDs.
In general it looks fine, but are you going to export each and every LLD's
URL, branch and commit into variables?
> On 10/27/2015 12:56 PM, Jacob Stiffler wrote:
> >I plan to clean up the LLD recipes and split up the device-specific
> >libraries to only the relevant machine. There are quite a few LLDs
> >which will need this clean up so I wanted to submit an RFC before
> >proceeding with the rest of them.
> >
> >Jacob Stiffler (2):
> > cppi-lld: Clean up recipes
> > cppi-lld: Only build binaries relevent to the machine
> >
> > recipes-bsp/cppi-lld/cppi-lld-test_git.bb | 2 ++
> > recipes-bsp/cppi-lld/cppi-lld.inc | 24 ++++++++++++++++++------
> > recipes-bsp/cppi-lld/cppi-lld_git.bb | 13 +++++++++++--
> > 3 files changed, 31 insertions(+), 8 deletions(-)
> >
>
> --
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
next prev parent reply other threads:[~2015-10-29 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 16:56 [RFC 0/2] LLD cleanup and device split Jacob Stiffler
2015-10-27 16:56 ` [RFC 1/2] cppi-lld: Clean up recipes Jacob Stiffler
2015-10-27 16:56 ` [RFC 2/2] cppi-lld: Only build binaries relevent to the machine Jacob Stiffler
2015-10-29 12:30 ` [RFC 0/2] LLD cleanup and device split Jacob Stiffler
2015-10-29 14:31 ` Denys Dmytriyenko [this message]
2015-10-29 15:01 ` Jacob Stiffler
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=20151029143135.GB8780@edge \
--to=denys@ti.com \
--cc=j-stiffler@ti.com \
--cc=meta-ti@yoctoproject.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.