[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080428195455.6e07cb8d.akpm@linux-foundation.org>
Date: Mon, 28 Apr 2008 19:54:55 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Brownell <david-b@...bell.net>
Cc: lkml <linux-kernel@...r.kernel.org>,
Trent Piepho <tpiepho@...escale.com>,
hartleys <hartleys@...ionengravers.com>,
Ben Nizette <bn@...sdigital.com>,
Mike Frysinger <vapier.adi@...il.com>,
Bryan Wu <cooloney@...nel.org>, Greg KH <greg@...ah.com>
Subject: Re: [patch/rfc 2.6.25-git] gpio: sysfs interface
On Mon, 28 Apr 2008 16:28:13 -0700 David Brownell <david-b@...bell.net> wrote:
> > If we had a strcmp() variant which treats a \n in the first arg as a \0
> > the above would become
> >
> > if (sysfs_streq(buf, "high"))
> > status = gpio_direction_output(gpio, 1);
> > else if (sysfs_streq(buf, "out") || sysfs_streq(buf, "low"))
> > status = gpio_direction_output(gpio, 0);
> > else if (sysfs_streq(buf, "in"))
> > status = gpio_direction_input(gpio);
>
> That would indeed be better. Maybe I should whip up a sysfs
> patch adding that, and have this depend on that patch. (I've
> CC'd Greg in case he has comments on that...)
Yes, it would be a standalone patch. The sort which generates oceans of
useful feedback ;) The sort which also generates hundreds of
use-new-toy-to-clean-up-old-code patches for me to merge :(
> Alternatively: strict_streq(), analogy to strict_strto*()?
Yeah, I couldn't think of a decent name. I do think it should return true
on finding a match so callers don't need to use ! or ==0. So its name
shouldn't look anything like "strcmp".
--
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/
Powered by blists - more mailing lists