All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Krummenacher <max.oss.09@gmail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-fsl-arm-extra PATCH] linux-toradex (3.14.28): Restrict recipe parsing for compatible machines
Date: Tue, 19 Jan 2016 16:15:41 +0100	[thread overview]
Message-ID: <CAEHkU3XUUF7ncDm-b6Q+WxhndJ9HrV7kTaxOVh12AaRCf72nkQ@mail.gmail.com> (raw)
In-Reply-To: <CAP9ODKraxYP8yXLvfuKB3pjMDRo6W9kWNkNLoFv7cy-d-GsXmA@mail.gmail.com>

Hi Otavio

2016-01-19 15:15 GMT+01:00 Otavio Salvador <otavio.salvador@ossystems.com.br>:
> On Mon, Jan 18, 2016 at 9:52 PM, Max Krummenacher <max.oss.09@gmail.com> wrote:
>> Am Montag, den 18.01.2016, 15:51 -0200 schrieb Otavio Salvador:
>>> While it is good, as design, allow for easier reuse of the recipe by
>>> custom designs (specially SoM-based ones) it requires that we provide
>>> common 'defconfig' files.
>>>
>>
>> Wouldn't it then be better to provide such a common defconfig
>> additionally?
>> If yes I could prepare an alternative patch which adds
>> recipes-kernel/linux/linux-toradex-3.14.28/defconfig
>> instead of restricting compatible machine.
>> I would probably take the current linux-fslc one to cover a greater
>> range of drivers and options than what we use for our machines.
>
> This is indeed an option and I would appreciate it. One even better
> one, in my POV, would be if both machines could use a single
> defconfig. Would this be possible?
>
Yes this is possible, one is a subset of the other.
I'm still not happy though about size etc. as I outlined in the
discussion for the initial commit:
https://lists.yoctoproject.org/pipermail/meta-freescale/2015-December/016795.html
If you have strong feelings towards the 'one size fits all' solution I
might get persuaded (or pressed)
to go for it.

Max

> --
> 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


  reply	other threads:[~2016-01-19 15:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 17:51 [meta-fsl-arm-extra PATCH] linux-toradex (3.14.28): Restrict recipe parsing for compatible machines Otavio Salvador
2016-01-18 23:52 ` Max Krummenacher
2016-01-19 14:15   ` Otavio Salvador
2016-01-19 15:15     ` Max Krummenacher [this message]
2016-01-19 15:20       ` 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=CAEHkU3XUUF7ncDm-b6Q+WxhndJ9HrV7kTaxOVh12AaRCf72nkQ@mail.gmail.com \
    --to=max.oss.09@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio.salvador@ossystems.com.br \
    --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.