From: Clark Rawlins <clark.rawlins@escient.com>
To: buildroot@busybox.net
Subject: [Buildroot] Out of tree kernel modules
Date: Fri, 08 Jan 2010 13:16:59 -0500 [thread overview]
Message-ID: <1262974619.12983.12.camel@venture> (raw)
I have a few out of tree kernel modules I want to add to buildroot, and
there doesn't seem to be a good place in the configuration hierarchy to
put them. Would adding another category like buildroot already does for
editors called "Extra Kernel Modules" that list available
packages/modules. These make fragments would then live in a separate
directory made for these packages called packages/kernel-modules.
reply other threads:[~2010-01-08 18:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1262974619.12983.12.camel@venture \
--to=clark.rawlins@escient.com \
--cc=buildroot@busybox.net \
/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