From: Pavel Roskin <proski@gnu.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Andrey Borzenkov <arvidjaar@mail.ru>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wireless: sysfs was displaying different values for level and noise than procfs
Date: Thu, 20 Nov 2008 11:15:01 -0500 [thread overview]
Message-ID: <1227197701.10629.1.camel@dv> (raw)
In-Reply-To: <1227164258.17336.20.camel@johannes.berg>
On Thu, 2008-11-20 at 07:57 +0100, Johannes Berg wrote:
> Actually, I was hoping to deprecate the sysfs interface, there are tons
> of apps relying on procfs unfortunately and very few, if any, relying on
> sysfs.
OK, then I would not bother changing it at all.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-11-20 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 15:31 [PATCH] wireless: sysfs was displaying different values for level and noise than procfs Andrey Borzenkov
2008-11-19 19:13 ` Pavel Roskin
2008-11-19 19:45 ` Andrey Borzenkov
2008-11-19 20:08 ` John W. Linville
2008-11-19 21:51 ` Pavel Roskin
2008-11-20 6:57 ` Johannes Berg
2008-11-20 16:15 ` Pavel Roskin [this message]
2008-11-20 12:08 ` Holger Schurig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1227197701.10629.1.camel@dv \
--to=proski@gnu.org \
--cc=arvidjaar@mail.ru \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).