All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: kernel-dev manual: SCC Description File Reference seems incomplete
Date: Wed, 01 May 2013 13:49:12 -0700	[thread overview]
Message-ID: <51817FC8.5000905@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1304230955180.16781@oneiric>

Hi Robert,

Please Cc me on kernel-dev manual email (in general Cc'ing the author is
a good way to help ensure your comments get addressed).

Bruce has responded already, and I don't have anything to add in this case.

Thanks,

On 04/23/2013 06:59 AM, Robert P. J. Day wrote:
> 
>   currently psyching up to work my way through the kernel dev manual,
> and i noticed this:
> 
> http://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#scc-reference
> 
> that reference list seems incomplete. at a *brief* glance:
> 
> * no mention of the "force" directive
> * no mention "include" directive has optional following keywords, such
>   as "nocfg" or "inherit"
> * no mention of kconf keyword "required", which i've seen on occasion
> 
>   again, that was a very brief observation, not meant to be a complete
> list.
> 
> rday
> 

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel


  parent reply	other threads:[~2013-05-01 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 13:59 kernel-dev manual: SCC Description File Reference seems incomplete Robert P. J. Day
2013-04-23 14:01 ` Bruce Ashfield
2013-04-23 14:02   ` Robert P. J. Day
2013-05-01 20:49 ` Darren Hart [this message]
2013-05-01 20:52   ` Robert P. J. Day

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=51817FC8.5000905@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=rpjday@crashcourse.ca \
    --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.