From: Andrew Morton <akpm@linux-foundation.org>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: linux-kernel@vger.kernel.org, ian@beware.dropbear.id.au
Subject: Re: [1/1] w1: w1 temp calculation overflow fix.
Date: Mon, 9 Feb 2009 14:48:03 -0800 [thread overview]
Message-ID: <20090209144803.821aa33e.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090209220830.GA15633@ioremap.net>
On Tue, 10 Feb 2009 01:08:30 +0300
Evgeniy Polyakov <zbr@ioremap.net> wrote:
> > Please provide changelogs. This bugfix is applicable to 2.6.28.x and
> > probably earlier. But due to the lack of any supporting information I
> > am not in a position to determine whether it should be backported.
>
> That's what was placed into the documentation iirc, code for the more
> advanced chip works ok. This code exists for way too long, but
> apparently did not grow higher than 32 degrees, so it is applicable for
> the earlier trees either.
I think the above means that the patch is appropriate for earlier trees.
But we still don't have a _reason_. Presumably the bug causes the
driver to malfunction in some manner.
There are two reasons for properly describing the patch:
a) the stable maintainers will want to understand why they should
backport the patch - does the bug affect anyone and if so, how?
b) people who are using earlier kernel versions and who experience a
bug will want to know whether this patch will fix their bug. To do
that, they will need a description of what the patch fixes!
So please, do describe the user-visible impact of the bug if that is at
all relevant or possible.
next prev parent reply other threads:[~2009-02-09 22:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 21:42 [1/1] w1: w1 temp calculation overflow fix Evgeniy Polyakov
2009-02-09 21:48 ` Harvey Harrison
2009-02-09 22:09 ` Evgeniy Polyakov
2009-02-09 21:56 ` Andrew Morton
2009-02-09 22:08 ` Evgeniy Polyakov
2009-02-09 22:48 ` Andrew Morton [this message]
2009-02-09 23:31 ` Andrew Morton
2009-02-10 8:54 ` Evgeniy Polyakov
2009-02-11 6:41 ` Ian Dall
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=20090209144803.821aa33e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ian@beware.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=zbr@ioremap.net \
/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