From: Randy Dunlap <rdunlap@xenotime.net>
To: Mike Galbraith <efault@gmx.de>
Cc: Valdis.Kletnieks@vt.edu, Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net
Subject: Re: Linux 3.0.8
Date: Wed, 26 Oct 2011 09:39:09 -0700 [thread overview]
Message-ID: <4EA837AD.6070700@xenotime.net> (raw)
In-Reply-To: <1319616850.4829.28.camel@marge.simson.net>
On 10/26/11 01:14, Mike Galbraith wrote:
> On Tue, 2011-10-25 at 04:41 -0400, Valdis.Kletnieks@vt.edu wrote:
>> On Tue, 25 Oct 2011 09:02:40 +0200, Greg KH said:
>>> On Mon, Oct 24, 2011 at 10:40:44PM -0700, Randy Dunlap wrote:
>>>> On 10/24/11 22:19, Greg KH wrote:
>>>>> All users of the 3.0 kernel series must upgrade.
>>>> I noticed that "must" word in 3.0.7 also. Please explain.
>>> Nothing new, I've been saying that for years.
>>
>> I think Randy means that out of the 29 commits for .7->.8, there's only one
>> (Hugh Dicken's mremap fix) and *maybe* Peter Zijlstra's cputimer fix, which
>> even *possibly* rise to the "all users" level, as everything else is against
>> XFS or CIFS or ARM or something else that's not an across-the-board issue.
>>
>> And the changelog for the mremap commit says that "but this lucky report
>> hints", which sort of implies it's a very hard-to-hit bug that nobody even knew
>> was there.
>>
>> So it's not obvious from just the shortlog that it's a "MUST upgrade" category.
>
> Seems like perfectly fine boilerplate to me. If I want the warmest
> fuzzy I can get, I must upgrade. Peter's patch fixed a box killer that
> I don't care to hit (dead bugs being kinda boring), so I must upgrade.
Sure, if it's just boilerplate, that's fine.
My mistake was thinking that it was something new & different.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-10-26 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 5:19 Linux 3.0.8 Greg KH
2011-10-25 5:20 ` Greg KH
2011-10-25 5:40 ` Randy Dunlap
2011-10-25 7:02 ` Greg KH
2011-10-25 8:41 ` Valdis.Kletnieks
2011-10-26 8:14 ` Mike Galbraith
2011-10-26 16:39 ` Randy Dunlap [this message]
2011-10-27 12:02 ` Paul Bolle
2011-10-27 12:08 ` Greg KH
2011-10-27 12:57 ` Paul Bolle
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=4EA837AD.6070700@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=efault@gmx.de \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.