linux-kernel - Re: [PATCH] ia64: rename platform_name to ia64_platform

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: <1343204319.1693.6.camel@joe2Laptop>
Date:	Wed, 25 Jul 2012 01:18:39 -0700
From:	Joe Perches <joe@...ches.com>
To:	Fengguang Wu <fengguang.wu@...el.com>
Cc:	"Luck, Tony" <tony.luck@...el.com>, linux-ia64@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>, alsa-devel@...a-project.org
Subject: Re: [PATCH] ia64: rename platform_name to ia64_platform_name

On Wed, 2012-07-25 at 16:06 +0800, Fengguang Wu wrote:
> The macro name is too generic and conflicts with
> snd_soc_dai_link.platform_name, which triggers lots of ALSA build errors.

Is platform_name particularly special?

Perhaps it's be better to rename all the other
platform_<foo> uses to ia64_platform_<foo>

[]

> diff --git a/arch/ia64/include/asm/machvec.h b/arch/ia64/include/asm/machvec.h
[]
> @@ -120,7 +120,7 @@ extern void machvec_tlb_migrate_finish (struct mm_struct *);
>  # ifdef MACHVEC_PLATFORM_HEADER
>  #  include MACHVEC_PLATFORM_HEADER
>  # else
> -#  define platform_name		ia64_mv.name
> +#  define ia64_platform_name	ia64_mv.name
>  #  define platform_setup	ia64_mv.setup
>  #  define platform_cpu_init	ia64_mv.cpu_init
>  #  define platform_irq_init	ia64_mv.irq_init

Maybe something like:

$ git ls-files arch/ia64 | \
  xargs sed -r -i 's/\bplatform_([a-z_]+)\b/ia64_platform_\1/g'

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