From: Olivier Galibert <galibert@pobox.com>
To: "Hack inc." <linux-kernel@vger.kernel.org>
Subject: Regressions between 2.6.30.2 and 2.6.31.4
Date: Sat, 17 Oct 2009 17:48:33 +0200 [thread overview]
Message-ID: <20091017154833.GA40799@dspnet.fr.eu.org> (raw)
I just updated from 2.6.30.2 to 2.6.31.4 and I had the dubious
pleasure to find out that the "don't change user interfaces" principle
has been ignored once again.
Stopping rfkill for wlan0 was:
echo 1 > /sys/class/net/wlan0/device/rfkill/rfkill*/state
now it's:
echo 1 > /sys/class/net/wlan0/device/ieee80211/phy*/rfkill*/state
and it was different for 29.4 (no /rfkill/ subdirectory). What will
it be for 32? Bets are open.
As for my sound card (intel hda), looks like someone decided to add
two controls for jack presence detection *in* *the* *middle* of the
existing controls. Numbered controls, mind you, because somehow names
must be too complex to use. That made alsactl decide not to restore
my levels. Always pleasant.
Will the alsa and the sysfs-using guys ever bother with compatibility?
OG.
reply other threads:[~2009-10-17 15:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20091017154833.GA40799@dspnet.fr.eu.org \
--to=galibert@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®