From: Nikolay Dimitrov <picmaster@mail.bg>
To: Otavio Salvador <otavio@ossystems.com.br>,
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 20:10:47 +0300 [thread overview]
Message-ID: <5582FB97.5060300@mail.bg> (raw)
In-Reply-To: <CAP9ODKomCsKs8FgxuBg6xnnB6aTkhas36Fcd+VZ9kURohJ39Eg@mail.gmail.com>
Hi Otavio,
On 06/18/2015 04:58 PM, Otavio Salvador wrote:
[snip]
>
> 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
Understood. Then here's my proposal, which I hope aligns with what you
already outlined:
1. Drop SOC name from the provider name
...in order to have more SOCs benefit from the same efforts. First,
patches in non-soc-specific common areas can be reused as-is (ext4
patches anyone :D?), and second, it would be great to have 1 repository
where all these efforts are concentrated, not separate for each separate
SoC (also, there are drivers for IP-blocks which are reused 1:1 across
SoCs).
2. Make sure the provider name doesn't contain a delimited string of
"fsl", "imx" or "mx"
... to make sure the provider is not confused with the FSL provider, and
to give due credit to the upstream + community efforts.
3. Drop the GA release version from the provider name
...for several reasons:
- it will limit the ability to merge patches from different GA releases
(if/when such need arises)
- to not confuse it with FSL GA releases
- sooner or later due to upstream patches merged this code will be
further and further away from the FSL release point.
So I think that a provider name like...
linux-fslc_3.14.28
linux-fslc_3.17.4
linux-fslc_4.0
...seems practical.
(I can only make the educated guess that "fslc" = "Freescale community",
but "fsl-community" really seems quite long).
Regards,
Nikolay
next prev parent reply other threads:[~2015-06-18 17:10 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
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 [this message]
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=5582FB97.5060300@mail.bg \
--to=picmaster@mail.bg \
--cc=daiane.list@gmail.com \
--cc=meta-freescale@yoctoproject.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.