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  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:	Wed, 01 Jun 2016 20:24:20 -0500
From:	Scott Wood <>
To:	Arnd Bergmann <>,
Cc:	Ulf Hansson <>,
	Yangbo Lu <>,
	Mark Rutland <>,
	Xiaobo Xie <>,
	"" <>,
	"" <>,
	Qiang Zhao <>,
	Russell King <>,
	Bhupesh Sharma <>,
	Joerg Roedel <>,
	Claudiu Manoil <>,
	"" <>,
	Rob Herring <>,
	Santosh Shilimkar <>,
	"" <>,
	"" <>,
	"" <>,
	Yang-Leo Li <>,
	"" <>,
	Kumar Gala <>,
Subject: Re: [PATCH 4/4] Revert "powerpc/fsl: Move fsl_guts.h out of

On Mon, 2016-05-30 at 15:18 +0200, Arnd Bergmann wrote:
> All users of this driver are PowerPC specific and the header file
> has no business in the global include/linux/ hierarchy, so move
> it back before anyone starts using it on ARM.
> This reverts commit 948486544713492f00ac8a9572909101ea892cb0.
> Signed-off-by: Arnd Bergmann <>
> ---
> This part of the series is not required for the eSDHC quirk,
> but it restores the asm/fsl_guts.h header so it doesn't accidentally
> get abused for this in the future. I found two drivers outside of
> arch/powerpc that already accessed the registers directly, but the
> functions look fairly contained, and can be easily hidden in an
> #ifdef CONFIG_PPC


Besides adding ifdef pollution for no good reason, this register block is used
on some ARM chips as well.  Why is it a problem if "anyone starts using it on

BTW, of all the mailing lists you included on this CC, you seem to have left
off the PPC list (I've added it).


Powered by blists - more mailing lists