Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Clark Rawlins <clark.rawlins@escient.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] Support for a kernel-modules catagory
Date: Mon, 11 Jan 2010 10:44:11 -0500	[thread overview]
Message-ID: <1263224651.5210.3.camel@venture> (raw)
In-Reply-To: <a038bef51001110614y2d1e6130gc88bc5b0cc90d19@mail.gmail.com>

On Mon, 2010-01-11 at 09:14 -0500, Chris Packham wrote:
> On Sat, Jan 9, 2010 at 1:00 PM, Clark Rawlins <clark.rawlins@escient.com> wrote:
> > Add support for a catagory of packages called
> > "Extra kernel modules" in menuconfig and a
> > new subdirectory similar to the "editors"
> > subdirectory to hold the kernel-modules packages.
> > diff --git a/package/kernel-modules/Config.in b/package/kernel-modules/Config.in
> [snip]
> > new file mode 100644
> > index 0000000..ddd27c3
> > --- /dev/null
> > +++ b/package/kernel-modules/Config.in
> > @@ -0,0 +1,3 @@
> > +menu "Extra Kernel Modules"
> > +source "package/kernel-modules/cdfs/Config.in"
> > +endmenu
> 
> This depends on code in your next patch. Perhaps just start with an
> empty menu then add the cdfs part in your next patch. I'm not sure how
> pedantic buildroot is with creating git bisect points that build.

I will recreate these patches with this issue resolved.

      reply	other threads:[~2010-01-11 15:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-09 18:00 [Buildroot] [PATCH 1/2] Support for a kernel-modules catagory Clark Rawlins
2010-01-11 14:14 ` Chris Packham
2010-01-11 15:44   ` Clark Rawlins [this message]

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=1263224651.5210.3.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