linux-kernel - Re: [PATCH] m68k/gpio: remove arch specific sysfs bus device

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] [day] [month] [year] [list]

Message-ID: <57056402.8020308@uclinux.org>
Date:	Thu, 7 Apr 2016 05:31:14 +1000
From:	Greg Ungerer <gerg@...inux.org>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	linux-m68k@...r.kernel.org, Guenter Roeck <linux@...ck-us.net>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Alexandre Courbot <gnurou@...il.com>
Subject: Re: [PATCH] m68k/gpio: remove arch specific sysfs bus device

On 06/04/16 16:57, Linus Walleij wrote:
> On Wed, Apr 6, 2016 at 4:32 AM, Greg Ungerer <gerg@...inux.org> wrote:
>
>> From: Greg Ungerer <gerg@...by.(none)>
>>
>> The ColdFire architecture specific gpio support code registers a sysfs
>> bus device named "gpio". This clashes with the new generic API device
>> added in commit 3c702e99 ("gpio: add a userspace chardev ABI for GPIOs").
>>
>> The old ColdFire sysfs gpio device was never used for anything specific,
>> and no links or other nodes were created under it. The new API sysfs gpio
>> device has all the same default sysfs links (device, drivers, etc) and
>> they are properly populated.
>>
>> Remove the old ColdFire sysfs gpio registration.
>>
>> Signed-off-by: Greg Ungerer <gerg@...inux.org>
>
> Acked-by: Linus Walleij <linus.walleij@...aro.org>

Thanks Linus. I will push via the m68knommu git tree.

Regards
Greg