linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, Eric Paris <eparis@parisplace.org>
Subject: Re: linux-next: Tree for Nov 27 (file notify)
Date: Tue, 27 Nov 2012 16:09:01 -0500	[thread overview]
Message-ID: <1354050541.2849.8.camel@localhost> (raw)
In-Reply-To: <50B4EDBF.8070304@infradead.org>

On Tue, 2012-11-27 at 08:43 -0800, Randy Dunlap 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

It is something coming in from Andrew's tree.  I believe they already
have a patch.

-Eric

  reply	other threads:[~2012-11-27 21:09 UTC|newest]

Thread overview: 7+ 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 16:43 ` linux-next: Tree for Nov 27 (file notify) Randy Dunlap
2012-11-27 21:09   ` Eric Paris [this message]
2012-11-27 21:09   ` Stephen Rothwell
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=1354050541.2849.8.camel@localhost \
    --to=eparis@redhat.com \
    --cc=eparis@parisplace.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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).