linux-kernel - Re: [patch/rfc 2.6.25-git] gpio: sysfs interface

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0804291746410.20563@t2.domain.actdsltmp>
Date:	Tue, 29 Apr 2008 17:49:39 -0700 (PDT)
From:	Trent Piepho <tpiepho@...escale.com>
To:	David Brownell <david-b@...bell.net>
cc:	Ben Nizette <bn@...sdigital.com>,
	lkml <linux-kernel@...r.kernel.org>,
	hartleys <hartleys@...ionengravers.com>,
	Mike Frysinger <vapier.adi@...il.com>,
	Bryan Wu <cooloney@...nel.org>
Subject: Re: [patch/rfc 2.6.25-git] gpio: sysfs interface

On Tue, 29 Apr 2008, David Brownell wrote:
>
>> If anything,
>> the parsing code is simpler than what David has.
>
> Apples vs oranges.  Use the same command syntax if you're going
> to make comparisons; I can save even more with "+export/-unexport"
> syntax.  For comparable syntax, your stuff *IS* bigger.

If the code you wrote it not too complex, then why is the code I wrote, which
is not larger, too complex?


>> David's code for parsing the control file plus code for generating a mapping
>> range file would certainly be larger.
>
> The #3 option presumes some file listing chips and ranges too,
> since GPIOs are exported only on demand.  Ditto #2 and #4...

You never answered how one was supposed to get the proper device from a
script.
--
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/