From: Michal Marek <mmarek-AlSwsSmVLrQ@public.gmane.org>
To: Boaz Harrosh <bharrosh-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
Cc: Al Viro <viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>,
linux-fsdevel
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
NFS list <linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
open-osd <osd-dev-yNzVSZO3znNg9hUCZPvPmw@public.gmane.org>
Subject: Re: [PATCH] fs/Makefile: Always inspect exofs/
Date: Thu, 27 Oct 2011 12:54:32 +0200 [thread overview]
Message-ID: <4EA93868.8070404@suse.cz> (raw)
In-Reply-To: <4EA5FAD7.4020806-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
On 25.10.2011 01:55, Boaz Harrosh wrote:
>
> fs/exofs directory has multiple targets now, of which the
> ore.ko will be needed by the pnfs-objects-layout-driver
> (fs/nfs/objlayout).
>
> As suggested by: Michal Marek <mmarek-AlSwsSmVLrQ@public.gmane.org> convert
> inclusion of exofs/ from obj-$(CONFIG_EXOFS_FS) => obj-$(y).
I suggested obj-y verbatim, at least this is what I meant. obj-$(y)
expands to "obj-" and will do nothing.
Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-10-27 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 23:55 [PATCH] fs/Makefile: Always inspect exofs/ Boaz Harrosh
[not found] ` <4EA5FAD7.4020806-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2011-10-27 10:54 ` Michal Marek [this message]
[not found] ` <4EA93868.8070404-AlSwsSmVLrQ@public.gmane.org>
2011-10-27 23:25 ` Boaz Harrosh
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=4EA93868.8070404@suse.cz \
--to=mmarek-alswssmvlrq@public.gmane.org \
--cc=bharrosh-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=osd-dev-yNzVSZO3znNg9hUCZPvPmw@public.gmane.org \
--cc=viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.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 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).