From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
Daiane Angolini <daiane.list@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm-extra][PATCH] nitrogen6x.conf: Allow kernel provider override
Date: Wed, 30 Oct 2013 10:46:38 -0700 [thread overview]
Message-ID: <527145FE.9000407@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKrpBK9HG=iRDwF-iA47XgqSoYq05s1tKbRHWXto9y4qvQ@mail.gmail.com>
Hi Otavio,
On 10/30/2013 10:29 AM, Otavio Salvador wrote:
> On Wed, Oct 30, 2013 at 2:56 PM, Daiane Angolini <daiane.list@gmail.com> wrote:
>> On Wed, Oct 30, 2013 at 2:01 PM, Otavio Salvador
>> <otavio@ossystems.com.br> wrote:
>>> On Wed, Oct 30, 2013 at 12:44 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>> On 2013-10-30 08:33, Otavio Salvador wrote:
>>>>> On Wed, Oct 30, 2013 at 12:25 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>>>> On 2013-10-30 08:10, Otavio Salvador wrote:
>>>>>>> On Wed, Oct 30, 2013 at 11:41 AM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>>>>>>
>>>>>>>> This change lets the user override the choice of kernel in local.conf
>>>>>>>> Without it, there is no way to build any kernel, e.g. linux-imx, other
>>>>>>>> than the linux-boundary version.
>>>>>>>>
>>>>>>>> Signed-off-by: Gary Thomas <gary@mlbassoc.com>
>>>>>>>
>>
>> <snip>
>>
>> I do agree with both sides. But I think you didn´t presented the
>> complete set of possibilities. I mean, it´s not a "support" X
>> "flexibility" fight.
>>
>> If nitrogen-any deserves to be flexible, so all other deserves it the same way.
>>
>> If it´s "wrong" for one board. It´s "wrong" for any. So, please submit
>> the patch to fix all/every board.
>
> Agreed here.
>
Works for me.
Gary, do you want to take the patch? Otavio asked me 'cause he
was asking about our board...
>> As I really don´t have an strong position for this. I would say, let´s
>> change and see what´s happens.
>>
>> For support nightmare, we always need to say what is
>> u-boot/kernel/yocto problem in this ML, so the nightmare is already
>> here.
>
> :-(
>
Aww, it's not a nightmare. It's a jobs program ;)
>> But, in my opinion, it´s NOT a bug fix, and should NOT be merged in dora.
>
> Yes I agree it is not a bugfix but I think that it'd be better to be
> consistent with dora and master at this point. Most people will keep
> using dora for a while and it'd be better to have this deplyed now
> than see how it goes in 1.6 only.
>
> Comments?
>
Gary, did you ever think a single question mark would prompt so much
discussion?
I wish we had a clean "MAKEALL" to make sure nothing breaks, but that
seems unlikely.
Regards,
Eric
next prev parent reply other threads:[~2013-10-30 17:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 13:41 [meta-fsl-arm-extra][PATCH] nitrogen6x.conf: Allow kernel provider override Gary Thomas
2013-10-30 14:06 ` Eric Nelson
2013-10-30 14:10 ` Otavio Salvador
2013-10-30 14:25 ` Eric Nelson
2013-10-30 14:28 ` Otavio Salvador
2013-10-30 14:42 ` Eric Nelson
2013-10-30 14:25 ` Gary Thomas
2013-10-30 14:33 ` Otavio Salvador
2013-10-30 14:44 ` Gary Thomas
2013-10-30 16:01 ` Otavio Salvador
2013-10-30 16:16 ` Eric Nelson
2013-10-30 16:56 ` Daiane Angolini
2013-10-30 17:29 ` Otavio Salvador
2013-10-30 17:46 ` Eric Nelson [this message]
2013-10-30 17:51 ` Otavio Salvador
2013-10-30 18:04 ` Gary Thomas
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=527145FE.9000407@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--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.