linux-kernel - Re: [PATCH] power: Rename get_current to fix build failure / name conflict

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, 14 Jun 2010 17:12:22 +0200
From:	Peter Huewe <PeterHuewe@....de>
To:	Mike Rapoport <mike@...pulab.co.il>
Cc:	Anton Vorontsov <cbouatmailru@...il.com>,
	Wolfram Sang <w.sang@...gutronix.de>,
	Tejun Heo <tj@...nel.org>, Ryan Mallon <ryan@...ewatersys.com>,
	linux-kernel@...r.kernel.org, linux-sh@...r.kernel.org,
	sfr@...b.auug.org.au,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] power: Rename get_current to fix build failure / name conflict

Am Donnerstag 13 Mai 2010 07:27:28 schrieb Mike Rapoport:
> Peter Huewe wrote:
> > From: Peter Huewe <peterhuewe@....de>
> >
> > This patch changes the name of get_current function pointer to
> > get_battery_current to resolve a name conflict with the get_current
> > macro defined in current.h.
> >
> > This conflict resulted in a build-failure[1] for the sh4 arch
> > allyesconfig which is resolved by this patch.
> >
> > To be consistent the other function pointers (_voltage,_capacity) were
> > renamed too.
> >
> > Signed-off-by: Peter Huewe <peterhuewe@....de> 
> Acked-by: Ryan Mallon <ryan@...ewatersys.com>
> Acked-by: Mike Rapoport <mike@...pulab.co.il>

Unfortunately this build-failure still exists, in Linux-next and hit Linus' 
Tree :/

References:
http://kisskb.ellerman.id.au/kisskb/buildresult/2709436/
http://kisskb.ellerman.id.au/kisskb/buildresult/2687686/

Thanks,
Peter


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