[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201009251755.57690.arnd@arndb.de>
Date: Sat, 25 Sep 2010 17:55:57 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Márton Németh <nm127@...email.hu>,
"H. Peter Anvin" <hpa@...or.com>, Ian Kent <raven@...maw.net>
Subject: Re: [PATCH 1/2] autofs: Only declare function when CONFIG_COMPAT is defined
On Friday 24 September 2010 15:22:22 Frederic Weisbecker wrote:
> From: Márton Németh <nm127@...email.hu>
>
> The patch solves the following warnings message when CONFIG_COMPAT
> is not defined:
>
> fs/autofs/root.c:30: warning: ‘autofs_root_compat_ioctl’ declared ‘static’ but never defined
>
> Signed-off-by: Márton Németh <nm127@...email.hu>
> Cc: "H. Peter Anvin" <hpa@...or.com>
> Cc: Arnd Bergmann <arnd@...db.de>
> Signed-off-by: Frederic Weisbecker <fweisbec@...il.com>
Acked-by: Arnd Bergmann <arnd@...db.de>
My initial reaction was to put these into my bkl/vfs tree, but then I noticed
that they are against a 2.6.36 bug. Who's taking care of getting them upstream?
- Ian (maintainer)
- Arnd (who wrote the broken patch to start with)
- Frederic (who pushed the broken patch to Linus)
- Andrew (took them into -mm)
I don't care either way, just trying to make sure it gets there and we don't
all submit the same patch simultaneously.
The current state is annoying but harmless, so I could also just add the
patches to my 2.6.37 queue, which already has autofs patches for the BKL.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists