[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1266862590.18491.37.camel@violet>
Date: Mon, 22 Feb 2010 19:16:30 +0100
From: Marcel Holtmann <marcel@...tmann.org>
To: Johannes Berg <johannes@...solutions.net>
Cc: "John W. Linville" <linville@...driver.com>, florian@...kler.org,
linux-wireless@...r.kernel.org,
Randy Dunlap <rdunlap@...otime.net>,
Alan Jenkins <alan-jenkins@...fmail.co.uk>,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: [PATCH 1/2] Document the rfkill sysfs ABI
Hi Johannes,
> > > > > This moves sysfs ABI info from Documentation/rfkill.txt to the
> > > > > ABI subfolder and reformats it.
> > > > >
> > > > > Signed-off-by: Florian Mickler <florian@...kler.org>
> > > >
> > > > This is fine with me.
> > >
> > > we have to be careful here. Some of these sysfs details needs to be
> > > deprecated and removed. Applications should use /dev/rfkill
> > actually.
> >
> > Maybe all of it should be in "obsolete"?
>
> Maybe, maybe not. Some people hate /dev/rfkill because it means they
> need to use a programming language (rather than shell scripts), and I
> don't care enough to fight with them.
>
> For all I care, it can be at the current status quo forever.
I am fine with having these information in sysfs, but then they should
be useful. So we should expose the hard and soft block states and not
some magic madeup state. Also the claim file has to go away.
And not that the rfkill utility is perfect for scripting, but
whatever ;)
Florian, feel free to export the details from /dev/rfkill as proper
sysfs attributes and make them ABI, then we can talk.
Regards
Marcel
--
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