All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sgi.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andrew Morton <akpm@osdl.org>,
	hch@infradead.org, linux-kernel@vger.kernel.org,
	linux-xfs@oss.sgi.com
Subject: Re: xfs: Makefile-linux-2.6 => Makefile?
Date: Mon, 16 Jan 2006 21:40:43 -0600	[thread overview]
Message-ID: <43CC673B.8050808@sgi.com> (raw)
In-Reply-To: <20060116231952.GA8752@mars.ravnborg.org>

Sam Ravnborg wrote:
>>Sam, is there any way to make this work with some code for the module in a 
>>subdirectory?
> 
> 
> Hi Eric.
> I forgot to point out one ugly solution for this.
> You can include a dummy Kbuild (Makefile) in each directory to support
> this. I recall that reiser4 had similar question and this was the
> solution I pointed out for them too.
> No - I am not in favour of it. But for local development it could make
> sense.
> So it may solve the "Eric" part of it, but not the "Andrew" part of it
> since these file will never get in the mainstream kernel (hopefully).
> 
> 	Sam

Thanks, Sam - I'd considered that, too.  We may do it locally.

-Eric

  reply	other threads:[~2006-01-17  3:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 16:42 xfs: Makefile-linux-2.6 => Makefile? Sam Ravnborg
2006-01-09 16:46 ` Christoph Hellwig
2006-01-09 17:19   ` Sam Ravnborg
2006-01-09 21:01   ` Sam Ravnborg
2006-01-09 21:05     ` Christoph Hellwig
2006-01-09 21:18       ` Sam Ravnborg
2006-01-09 21:03   ` Eric Sandeen
2006-01-09 21:20     ` Sam Ravnborg
2006-01-09 21:23       ` Eric Sandeen
2006-01-09 21:45         ` Sam Ravnborg
2006-01-10  7:45     ` Andrew Morton
2006-01-10 15:14       ` Eric Sandeen
2006-01-10 16:34       ` Eric Sandeen
2006-01-10 20:02         ` Sam Ravnborg
2006-01-16 23:19         ` Sam Ravnborg
2006-01-17  3:40           ` Eric Sandeen [this message]
2006-01-10 20:00       ` Sam Ravnborg

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=43CC673B.8050808@sgi.com \
    --to=sandeen@sgi.com \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=sam@ravnborg.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.