From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: felipe.contreras@gmail.com, raven@themaw.net
Subject: + autofs4-fix-compilation-warning.patch added to -mm tree
Date: Mon, 13 Sep 2010 15:48:45 -0700 [thread overview]
Message-ID: <201009132248.o8DMmjNF025710@imap1.linux-foundation.org> (raw)
The patch titled
] autofs4: fix compilation warning
has been added to the -mm tree. Its filename is
autofs4-fix-compilation-warning.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: ] autofs4: fix compilation warning
From: Felipe Contreras <felipe.contreras@gmail.com>
fs/autofs4/root.c:31: warning: `autofs4_root_compat_ioctl' declared `static' but never defined
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Ian Kent <raven@themaw.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/autofs4/root.c | 2 ++
1 file changed, 2 insertions(+)
diff -puN fs/autofs4/root.c~autofs4-fix-compilation-warning fs/autofs4/root.c
--- a/fs/autofs4/root.c~autofs4-fix-compilation-warning
+++ a/fs/autofs4/root.c
@@ -28,7 +28,9 @@ static int autofs4_dir_unlink(struct ino
static int autofs4_dir_rmdir(struct inode *,struct dentry *);
static int autofs4_dir_mkdir(struct inode *,struct dentry *,int);
static long autofs4_root_ioctl(struct file *,unsigned int,unsigned long);
+#ifdef CONFIG_COMPAT
static long autofs4_root_compat_ioctl(struct file *,unsigned int,unsigned long);
+#endif
static int autofs4_dir_open(struct inode *inode, struct file *file);
static struct dentry *autofs4_lookup(struct inode *,struct dentry *, struct nameidata *);
static void *autofs4_follow_link(struct dentry *, struct nameidata *);
_
Patches currently in -mm which might be from felipe.contreras@gmail.com are
autofs4-fix-compilation-warning.patch
reply other threads:[~2010-09-13 22:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201009132248.o8DMmjNF025710@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=felipe.contreras@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=raven@themaw.net \
/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