From: Randy Dunlap <randy.dunlap@oracle.com>
To: Eric Paris <eparis@redhat.com>
Cc: Alexander Beregalov <a.beregalov@gmail.com>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: next-20090630: audit/fsnotify build failure
Date: Tue, 30 Jun 2009 12:06:48 -0700 [thread overview]
Message-ID: <4A4A6248.90706@oracle.com> (raw)
In-Reply-To: <1246384996.22562.19.camel@dhcp235-23.rdu.redhat.com>
Eric Paris wrote:
> On Tue, 2009-06-30 at 16:27 +0400, Alexander Beregalov wrote:
>> Hi
>>
>> kernel/audit_watch.c: In function 'audit_get_parent':
>> kernel/audit_watch.c:85: error: implicit declaration of function
>> 'fsnotify_get_mark'
>
> Should be fixed for you by:
>
> http://git.infradead.org/users/eparis/notify.git?a=commitdiff;h=aae48cb2b8719e8a374faea141373b7ce0b89bc6
> http://git.infradead.org/users/eparis/notify.git?a=commitdiff;h=de85e5bc3690c3063aea790279e898adb5bac0ba
>
>> $ egrep "NOTIFY|AUDIT" .config
>> CONFIG_AUDIT_ARCH=y
>> CONFIG_AUDIT=y
>> # CONFIG_AUDITSYSCALL is not set
>> # CONFIG_FSNOTIFY is not set
>> CONFIG_INOTIFY=y
>
> Unrelated note, CONFIG_INOTIFY in linux-next is completely and totally
> useless.....
Please explain.
Looks like it still controls building fs/notify/inotify/inotify.o,
based on fs/notify/inotify/Makefile.
--
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/
next prev parent reply other threads:[~2009-06-30 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 12:27 next-20090630: audit/fsnotify build failure Alexander Beregalov
2009-06-30 12:31 ` Eric Paris
2009-06-30 18:03 ` Eric Paris
2009-06-30 19:06 ` Alexander Beregalov
2009-06-30 19:06 ` Randy Dunlap [this message]
2009-06-30 19:17 ` Eric Paris
2009-07-01 12:07 ` Alexander Beregalov
2009-07-01 12:38 ` Eric Paris
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=4A4A6248.90706@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=a.beregalov@gmail.com \
--cc=eparis@redhat.com \
--cc=linux-next@vger.kernel.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.