From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Cyrill Gorcunov <gorcunov@openvz.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Eric Paris <eparis@parisplace.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: Tree for Nov 27 (file notify)
Date: Wed, 28 Nov 2012 08:09:28 +1100 [thread overview]
Message-ID: <20121128080928.498fcbf68e9afac415bdc27b@canb.auug.org.au> (raw)
In-Reply-To: <50B4EDBF.8070304@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
[Just adding some more cc's]
On Tue, 27 Nov 2012 08:43:43 -0800 Randy Dunlap <rdunlap@infradead.org> wrote:
>
> On 11/26/2012 10:25 PM, Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20121126:
> >
>
>
> when CONFIG_PROC_FS is not enabled (also seen in mmotm):
>
> fs/notify/fanotify/fanotify_user.c:436:17: error: 'fanotify_show_fdinfo' undeclared here (not in a function)
> fs/notify/inotify/inotify_user.c:333:17: error: 'inotify_show_fdinfo' undeclared here (not in a function)
>
>
>
> --
> ~Randy
>
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-27 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 6:25 linux-next: Tree for Nov 27 Stephen Rothwell
2012-11-27 6:25 ` Stephen Rothwell
2012-11-27 16:43 ` linux-next: Tree for Nov 27 (file notify) Randy Dunlap
2012-11-27 21:09 ` Eric Paris
2012-11-27 21:09 ` Stephen Rothwell [this message]
2012-11-27 18:32 ` linux-next: Tree for Nov 27 (media/v4l2-core/videobuf2-dma-contig.c) Randy Dunlap
2012-11-27 21:15 ` Stephen Rothwell
2012-11-28 0:52 ` Kyungmin Park
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=20121128080928.498fcbf68e9afac415bdc27b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=eparis@parisplace.org \
--cc=gorcunov@openvz.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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.