From: Vladimir Zajac <eightgraph@gmail.com>
To: Thomas Renninger <trenn@suse.de>
Cc: rui.zhang@intel.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.30-rc4] thermal: fix off-by-1 error in trip point trigger condition
Date: Tue, 9 Jun 2009 19:06:21 +0200 [thread overview]
Message-ID: <200906091906.22162.eightgraph@gmail.com> (raw)
In-Reply-To: <200906091510.11285.trenn@suse.de>
On Tuesday 09 June 2009 15:10:10 Thomas Renninger wrote:
> This one should have
> CC: stable@kernel.org
> added.
> Vladimir, do you mind submitting this one for stable inclusion
> if not done already.
>
Inclusion into stable is not needed.
The bug was introduced in 2.6.30-rc1, stable release is not affected.
Vladimir
prev parent reply other threads:[~2009-06-09 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 17:34 [PATCH 2.6.30-rc4] thermal: fix off-by-1 error in trip point trigger condition Vladimir Zajac
2009-05-07 0:48 ` Zhang Rui
2009-05-10 9:54 ` Vladimir Zajac
2009-05-14 17:39 ` Len Brown
2009-06-09 13:10 ` Thomas Renninger
2009-06-09 17:06 ` Vladimir Zajac [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=200906091906.22162.eightgraph@gmail.com \
--to=eightgraph@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=trenn@suse.de \
/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