All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Jate Sujjavanich <Jate.Sujjavanich@myfuelmaster.com>
Cc: "'yocto@yoctoproject.org'" <yocto@yoctoproject.org>
Subject: Re: yocto-bsp and kconf-check
Date: Thu, 29 Aug 2013 11:51:44 -0400	[thread overview]
Message-ID: <521F6E10.3090704@windriver.com> (raw)
In-Reply-To: <6C2434209962DC46B88345CA85C334A201CAAD7035ED@Courier.syntech.org>

On 13-08-29 11:36 AM, Jate Sujjavanich wrote:
> It appears that the yocto-bsp script generates a kernel configuration that creates some warnings during kern-tools' kconf_check. The {{machine}}.cfg file has many non-hardware options, therefore the script warns.
>
> It seems like many of these should be in the standard kernel configuration. Is this correct, and does the yocto-bsp data need to be updated?

Which kernel version ? But the answer is not necessarily, if a machine 
config
is specifying something that hasn't been tagged "hardware" or that
has a specified exception, you get a warning.

It's not about them being common or not, it's about BSPs following a
base policy versus having wild, per-board behaviour.

Cheers,

Bruce

>
> - Jate
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



  reply	other threads:[~2013-08-29 15:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29 15:36 yocto-bsp and kconf-check Jate Sujjavanich
2013-08-29 15:51 ` Bruce Ashfield [this message]
2013-08-29 18:56   ` Jate Sujjavanich
2013-08-29 19:45     ` Bruce Ashfield
2013-08-29 21:39       ` Jate Sujjavanich
2013-08-30  4:47         ` Bruce Ashfield
2013-08-29 19:46 ` Tom Zanussi

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=521F6E10.3090704@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=Jate.Sujjavanich@myfuelmaster.com \
    --cc=yocto@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.