linux-kernel - Re: [PATCH 1/2] autofs: Only declare function when CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100927123252.8e1826e8.akpm@linux-foundation.org>
Date:	Mon, 27 Sep 2010 12:32:52 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	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 Sat, 25 Sep 2010 17:55:57 +0200
Arnd Bergmann <arnd@...db.de> wrote:

> 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 usual deal: if it turns up in linux-next then I drop it.  If it
doesn't then I'll merge it into 2.6.37.

--
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/