From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [RFC PATCH 0/1] kernel.bbclass: remove default module_autoload and module_conf values
Date: Thu, 26 Jul 2012 14:04:30 -0400 [thread overview]
Message-ID: <cover.1343325569.git.bruce.ashfield@windriver.com> (raw)
Richard,
This is just what the subject implies, a RFC patch. While working
on some updates and docs, I (once gain) ran across the module_autoload
and module_conf default values in kernel.bbclass.
I've always wondered if that was the best place for these, since the
kernel.bbclass builds many different kernel versions.
I've simply removed them here, without relocating them to any other
recipe, since I can't see that they are really all that useful for
most targest.
This is a RFC, because I haven't done any research into what this
may or may not break outside of oe-core and reference boards.
Cheers,
Bruce
The following changes since commit fb53d69d9c726e6a663ea276cc440676e20f8326:
documentation/dev-manual/dev-manual-intro.xml: typo fixed. (2012-07-26 18:53:04 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel-rfc
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-rfc
Bruce Ashfield (1):
kernel.bbclass: remove default module_autoload and module_conf values
meta/classes/kernel.bbclass | 19 -------------------
1 files changed, 0 insertions(+), 19 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-07-26 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 18:04 Bruce Ashfield [this message]
2012-07-26 18:04 ` [PATCH 1/1] kernel.bbclass: remove default module_autoload and module_conf values Bruce Ashfield
2012-07-27 22:39 ` Darren Hart
2012-08-01 23:15 ` Khem Raj
2012-08-02 2:58 ` Bruce Ashfield
2012-08-02 3:12 ` Khem Raj
2012-08-02 3:23 ` Bruce Ashfield
2012-08-16 17:46 ` [RFC PATCH 0/1] " Saul Wold
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=cover.1343325569.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox