All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
	linux-kernel@vger.kernel.org, sudoyang@gmail.com
Subject: Re: compiling only one module in kernel version 2.6?
Date: Thu, 18 Aug 2005 13:54:38 -0400	[thread overview]
Message-ID: <1124387678.5186.76.camel@localhost.localdomain> (raw)
In-Reply-To: <20050818174255.GA8457@mars.ravnborg.org>

On Thu, 2005-08-18 at 19:42 +0200, Sam Ravnborg wrote:
> On Wed, Aug 17, 2005 at 01:54:50AM -0400, Steven Rostedt wrote:
> > On Wed, 2005-08-17 at 01:48 -0400, Steven Rostedt wrote:
> > > On Tue, 2005-08-16 at 22:41 -0700, Randy.Dunlap wrote:
> > > > 
> > > > Sam only added make .ko build support very recently,
> > > > so it could easily depend on what kernel verison Fong is using.
> > > 
> > > That could very well explain it. I'm doing this on 2.6.13-rc6-rt6
> > > (2.6.13-rc6 with Ingo's rt6 patch applied).  So I really do have a
> > > recent kernel.
> > > 
> > 
> > I just did this on a 2.6.9 vanilla kernel, and it still worked.
> 
> Hi Steve.
> 
> make fs/reiserfs/
> and
> make fs/reiserfs/resiserfs.ko
> 
> does not do the same thing. Only the latter result in a .ko file.

I never said I did a "make fs/reiserfs". I did a 
"make SUBDIRS=fs/reiserfs"  which does produce a .ko file.  

But even shorter is to do a "make M=fs/reiserfs", which also works.

But, I guess what was added was the ability to just type the module
itself.  That's cool, but I haven't had the need to do that (yet).

-- Steve



  reply	other threads:[~2005-08-18 17:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-17  2:09 compiling only one module in kernel version 2.6? Fong Vang
2005-08-17  3:18 ` Steven Rostedt
2005-08-17  5:41   ` Randy.Dunlap
2005-08-17  5:48     ` Steven Rostedt
2005-08-17  5:54       ` Steven Rostedt
2005-08-17  6:06         ` Randy.Dunlap
2005-08-18 17:42         ` Sam Ravnborg
2005-08-18 17:54           ` Steven Rostedt [this message]
2005-08-18 18:11             ` Randy.Dunlap

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=1124387678.5186.76.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=sam@ravnborg.org \
    --cc=sudoyang@gmail.com \
    /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.