linux-kernel - Re: [PATCH 2/3] gpiolib: add support for having symlinks under gpio class directory

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:	Wed, 9 Dec 2009 18:48:34 -0800
From:	Greg KH <gregkh@...e.de>
To:	Jani Nikula <ext-jani.1.nikula@...ia.com>
Cc:	dbrownell@...rs.sourceforge.net, linux-kernel@...r.kernel.org,
	dsilvers@...tec.co.uk, ben@...tec.co.uk,
	Artem.Bityutskiy@...ia.com, akpm@...ux-foundation.org
Subject: Re: [PATCH 2/3] gpiolib: add support for having symlinks under
	gpio class directory

On Wed, Dec 09, 2009 at 03:49:03PM +0200, Jani Nikula wrote:
> Extend the functionality of gpio_export_link() to allow exported GPIOs
> to have names using sysfs links under /sys/class/gpio.

No, please don't create symlinks under a class, that is not something
that any userspace tool is expecting.

I don't understand what you are trying to do here, why do you need a
symlink?  What is wrong with the original device names?

confused,

greg k-h
--
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/