linux-kernel - Re: [v4l-dvb-maintainer] [PATCH] media: replace remaining __FUNCTION_

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]

Date:	Mon, 3 Mar 2008 22:28:19 -0500
From:	"Michael Krufky" <mkrufky@...uxtv.org>
To:	"Harvey Harrison" <harvey.harrison@...il.com>
Cc:	"Mauro Carvalho Chehab" <mchehab@...radead.org>,
	"v4l-dvb-maintainer@...uxtv.org" <v4l-dvb-maintainer@...uxtv.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: [v4l-dvb-maintainer] [PATCH] media: replace remaining __FUNCTION__ occurences

On Mon, Mar 3, 2008 at 7:03 PM, Harvey Harrison
<harvey.harrison@...il.com> wrote:
> __FUNCTION__ is gcc-specific, use __func__
>
>  Signed-off-by: Harvey Harrison <harvey.harrison@...il.com>
>   162 files changed, 892 insertions(+), 892 deletions(-)


If we apply this, can it be broken down into several smaller patches?
I am in the midst of a large overhaul of the tuning subsystem, and if
this all gets applied at once, it will wreck havoc on my pending
changesets.

Other than that, I'm fine with this change if that's what we're doing
across the rest of the kernel...  Would just be easier to deal with if
it could be further broken down by subdirectory.

Regards,

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