From: Otavio Salvador <otavio@ossystems.com.br>
To: Daiane Angolini <daiane.list@gmail.com>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH 3/4] linux-fslc-mx6 (3.14-1.0.x): Add recipe
Date: Thu, 18 Jun 2015 10:58:45 -0300 [thread overview]
Message-ID: <CAP9ODKomCsKs8FgxuBg6xnnB6aTkhas36Fcd+VZ9kURohJ39Eg@mail.gmail.com> (raw)
In-Reply-To: <CA+jg_OWx4hT8K4BRC0Wo+zTrHYxAv7-DLPv1AZutzNE7RZrTwA@mail.gmail.com>
On Thu, Jun 18, 2015 at 10:40 AM, Daiane Angolini <daiane.list@gmail.com> wrote:
> On Wed, Jun 17, 2015 at 4:45 PM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>> On Wed, Jun 17, 2015 at 4:25 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
>>> So, in terms of functionality this kernel sits somewhere between
>>> mainline and FSL releases, is that correct?
>>
>> Yes; it is FSL release + stable releases + vendor/community fixes
>
> I've been thinking about this issue. And this provider (for imx6 only)
> may make sense to have "fslc" sufix, exactly because it has freescale
> + community patches
>
> However, the other (currently linux-fslc) does not make sense. Maybe
> linux-cmt makes more sense today.
>
> I remember one of the arguments to not use only "linux" and use a
> prefix was that it's not a pure mainline provider (it clones from
> github) and because it leave the "linux" only for internal kernels
>
> Any other suggestion?
I think we need to consider some things here:
linux-fslc is a kernel tree we maintain
u-boot-fslc is a u-boot tree we maintain
both have same goals and the idea is to provide a place to share
patches and backports.
The motivation to make the 3.14 is because FSL is not taking the fixes
and security updates from stable, so a place to merge those seems to
be beneficial. I don't want a plethora of names as it makes harder for
people to contribute and share work so I propose two solutions:
linux-fslc_4.0.bb
linux-fslc-mx6_3.14-1.0.x.bb
or
linux-fslc_4.0.bb
linux-fslc_3.14-1.0.x-mx6.bb
Both works.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
next prev parent reply other threads:[~2015-06-18 13:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 18:02 [meta-fsl-arm][PATCH 1/4] core-image-weston: Fail gracefully if using incompatible DISTRO_FEATURES Otavio Salvador
2015-06-17 18:02 ` [meta-fsl-arm][PATCH 2/4] fsl-default-providers.inc: Move content to imx-base.inc and mxs-base.inc Otavio Salvador
2015-06-17 18:33 ` Nikolay Dimitrov
2015-06-17 18:38 ` Otavio Salvador
2015-06-17 19:27 ` Nikolay Dimitrov
2015-06-17 18:02 ` [meta-fsl-arm][PATCH 3/4] linux-fslc-mx6 (3.14-1.0.x): Add recipe Otavio Salvador
2015-06-17 18:28 ` Nikolay Dimitrov
2015-06-17 18:30 ` Otavio Salvador
2015-06-17 18:38 ` Nikolay Dimitrov
2015-06-17 18:39 ` Otavio Salvador
2015-06-17 19:25 ` Nikolay Dimitrov
2015-06-17 19:32 ` Daiane Angolini
2015-06-17 19:45 ` Otavio Salvador
2015-06-18 13:40 ` Daiane Angolini
2015-06-18 13:58 ` Otavio Salvador [this message]
2015-06-18 15:32 ` Nikolay Dimitrov
2015-06-18 16:21 ` Otavio Salvador
2015-06-18 16:38 ` Nikolay Dimitrov
2015-06-18 16:47 ` Otavio Salvador
2015-06-18 16:47 ` Ann Thornton
2015-06-18 17:10 ` Nikolay Dimitrov
2015-06-18 17:40 ` Otavio Salvador
2015-06-17 18:02 ` [meta-fsl-arm][PATCH 4/4] imx-base.inc: Use linux-fslc-mx6 for all i.MX6 by default Otavio Salvador
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=CAP9ODKomCsKs8FgxuBg6xnnB6aTkhas36Fcd+VZ9kURohJ39Eg@mail.gmail.com \
--to=otavio@ossystems.com.br \
--cc=daiane.list@gmail.com \
--cc=meta-freescale@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.