From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: preferred KERNEL_FEATURES format: netfilter or netfilter.scc?
Date: Tue, 3 Mar 2015 04:12:27 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.11.1503030407310.18866@localhost> (raw)
kernel dev manual uses the KERNEL_FEATURES format of:
KERNEL_FEATURES += "features/netfilter.scc"
while ref manual variable glossary uses
KERNEL_FEATURES="features/netfilter"
is there a preference for the usage of the .scc suffix? (i'm assuming
they're both valid, i didn't actually check that. maybe i should check
that ...)
oh, wait, here's something from kernel-yocto.bbclass that seems to
require the presence of the .scc suffix:
# returns all the elements from the src uri that are .scc files
def find_sccs(d):
sources=src_patches(d, True)
sources_list=[]
for s in sources:
base, ext = os.path.splitext(os.path.basename(s))
if ext and ext in [".scc", ".cfg"]:
sources_list.append(s)
elif base and base in 'defconfig':
sources_list.append(s)
return sources_list
i should note that the introductory comment is incorrect since that
function clearly does not just find "sccs", it finds .cfg and
defconfig files as well, no?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2015-03-03 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 9:12 Robert P. J. Day [this message]
2015-03-03 10:39 ` preferred KERNEL_FEATURES format: netfilter or netfilter.scc? Robert P. J. Day
2015-03-03 14:29 ` Bruce Ashfield
2015-03-03 16:27 ` Robert P. J. Day
2015-03-03 16:30 ` Bruce Ashfield
2015-03-03 16:46 ` 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=alpine.LFD.2.11.1503030407310.18866@localhost \
--to=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.