From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Pavel Machek <pavel@ucw.cz>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>, Ingo Molnar <mingo@elte.hu>,
"Darrick J. Wong" <djwong@us.ibm.com>, Andi Kleen <ak@suse.de>,
Rodrigo Luiz <troops.of.doom@gmail.com>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Maximilian Engelhardt <maxi@daemonizer.de>,
Gary Zambrano <zambrano@broadcom.com>,
Michael Buesch <mb@bu3sch.de>,
Thomas Gleixner <tglx@linutronix.de>,
Stephen Hemminger <shemminger@linux-foundation.org>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org,
Maciej Rutecki <maciej.rutecki@gmail.com>
Subject: Re: [1/3] 2.6.22-rc4: known regressions v2
Date: Wed, 13 Jun 2007 20:02:04 +0200 [thread overview]
Message-ID: <4670311C.4080505@googlemail.com> (raw)
In-Reply-To: <20070613075110.0a9f54c2.akpm@linux-foundation.org>
Andrew Morton pisze:
> On Tue, 12 Jun 2007 15:02:22 +0000 Pavel Machek <pavel@ucw.cz> wrote:
>
>> Hi!
>>
>> Can we add 'writing to /proc/acpi/thermal/*/trip_points' no longer
>> works to the list?
>
> I thought we had.
Len rejected this bug
http://bugzilla.kernel.org/show_bug.cgi?id=8495
>
>> Len did it intentionally but that does not make it
>> right. People are using it and we did not go through deprecation
>> period. Plus there's no reasonable alternative.
>
> Was that writeability causing any actual problems in 2.6.21?
>
Regards,
Michal
--
LOG
http://www.stardust.webpages.pl/log/
prev parent reply other threads:[~2007-06-13 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-09 17:40 [1/3] 2.6.22-rc4: known regressions v2 Michal Piotrowski
2007-06-09 18:08 ` Thomas Gleixner
2007-06-12 15:02 ` Pavel Machek
2007-06-13 14:51 ` Andrew Morton
2007-06-13 18:02 ` Michal Piotrowski [this message]
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=4670311C.4080505@googlemail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=djwong@us.ibm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=maxi@daemonizer.de \
--cc=mb@bu3sch.de \
--cc=miklos@szeredi.hu \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=shemminger@linux-foundation.org \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=troops.of.doom@gmail.com \
--cc=zambrano@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.