From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] i.MX: Refactor and update library versions
Date: Sat, 5 Oct 2013 13:36:30 +0200 [thread overview]
Message-ID: <20131005133630.7f799fd6@skate> (raw)
In-Reply-To: <524F4541.1090004@boundarydevices.com>
Dear Eric Nelson,
On Fri, 04 Oct 2013 15:46:25 -0700, Eric Nelson wrote:
> On 09/29/2013 03:54 PM, Eric Nelson wrote:
> > This patch set restructures several libraries to share common
> > Makefile fragments in package/freescale-imx and bumps the
> > library versions to match the Freescale 3.0.35_4.1.0 release
> > for i.MX6.
> >
>
> Thomas and Arnout: do you want these to stay in /package?
I don't have a strong opinion on this one. If they use the
FREESCALE_IMX_MIRROR / FREESCALE_IMX_VERSION variable, I would find it
more logical to have them under package/freescale-imx/, but it's really
not a strong requirement.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-05 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 22:54 [Buildroot] [PATCH 0/4] i.MX: Refactor and update library versions Eric Nelson
2013-09-29 22:54 ` [Buildroot] [PATCH 1/4] i.MX: move Freescale i.MX packages into freescale-imx/ Eric Nelson
2013-09-29 22:54 ` [Buildroot] [PATCH 2/4] i.MX: Use FREESCALE_IMX_MIRROR_SITE for newly-moved packages Eric Nelson
2013-09-29 22:54 ` [Buildroot] [PATCH 3/4] i.MX6: Use canonical site for Freescale packages Eric Nelson
2013-09-29 22:54 ` [Buildroot] [PATCH 4/4] i.MX: Bump library versions to latest release (3.0.35-4.1.0) Eric Nelson
2013-10-04 22:46 ` [Buildroot] [PATCH 0/4] i.MX: Refactor and update library versions Eric Nelson
2013-10-05 11:36 ` Thomas Petazzoni [this message]
2013-10-05 14:52 ` Eric Nelson
2013-10-06 8:58 ` Thomas Petazzoni
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=20131005133630.7f799fd6@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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 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.