From: Christoph Hellwig <hch@infradead.org>
To: Bob Copeland <me@bobcopeland.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH 7/7] omfs: update kbuild to include OMFS
Date: Sun, 13 Apr 2008 04:10:45 -0400 [thread overview]
Message-ID: <20080413081045.GH9622@infradead.org> (raw)
In-Reply-To: <1208041121-26787-8-git-send-email-me@bobcopeland.com>
> --- /dev/null
> +++ b/fs/omfs/Makefile
> @@ -0,0 +1,7 @@
> +#
> +# Makefile for the Linux omfs filesystem routines.
> +#
> +
> +obj-$(CONFIG_OMFS_FS) += omfs.o
> +
> +omfs-objs := bitmap.o checksum.o dir.o file.o inode.o
No need to comment a trivial makefile. Also please use omfs-y +=
instead of omfs-objs :=
prev parent reply other threads:[~2008-04-13 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-12 22:58 [PATCH 7/7] omfs: update kbuild to include OMFS Bob Copeland
2008-04-13 8:10 ` Christoph Hellwig [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=20080413081045.GH9622@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@bobcopeland.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).