From: Hugh Dickins <hugh@veritas.com>
To: Chris Rankin <rankincj@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-stable release plans?
Date: Wed, 24 Jan 2007 16:12:46 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0701241607160.17843@blonde.wat.veritas.com> (raw)
In-Reply-To: <964414.64865.qm@web52908.mail.yahoo.com>
On Wed, 24 Jan 2007, Chris Rankin wrote:
>
> I suppose what I'm *really* asking is what the basis is for assuming that this *isn't* a kernel
> bug and can therefore be safely ignored, seeing as the oops is real, the hardware is fine and the
> kernel is untainted? That seems to cover the bases from where I'm sitting.
All I'm claiming is that it's no more a reason to avoid 2.6.19*
than to avoid any other release (the kernels before 2.6.7 happened
to have no such check, but that doesn't imply they were any safer).
It may indeed be due to a kernel bug, but I can't tell you where: sorry.
Hugh
next prev parent reply other threads:[~2007-01-24 16:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 15:53 Chris Rankin
2007-01-24 16:12 ` Hugh Dickins [this message]
2007-01-24 17:33 ` Chris Rankin
2007-01-24 16:28 ` Mark Rustad
2007-01-24 22:37 ` Chris Rankin
2007-01-24 23:11 ` Alan
2007-01-24 23:05 ` Chris Rankin
2007-01-24 23:32 ` Mark Rustad
2007-01-24 23:45 ` Chris Rankin
2007-01-25 1:00 ` Ken Moffat
2007-01-25 9:16 ` Chris Rankin
2007-01-25 19:36 ` Ken Moffat
2007-01-26 13:02 ` Chris Rankin
2007-01-25 23:26 ` Alistair John Strachan
2007-01-25 3:05 ` Mark Rustad
2007-01-25 21:04 ` Matt Mackall
2007-02-02 4:02 ` Valdis.Kletnieks
2007-02-02 6:47 ` Jon Masters
2007-02-02 8:17 ` Valdis.Kletnieks
[not found] <BC3E207A-1A56-4032-9619-910E80281E9C@gmail.com>
2007-01-25 8:51 ` Chris Rankin
-- strict thread matches above, loose matches on Subject: below --
2007-01-24 15:06 Chris Rankin
2007-01-24 15:40 ` Hugh Dickins
2007-01-24 13:30 Chris Rankin
2007-01-24 14:37 ` Hugh Dickins
2007-01-22 22:13 Chuck Ebbert
2007-01-23 0:23 ` Jesper Juhl
2007-01-23 20:33 ` Chuck Ebbert
2007-01-23 20:56 ` Adrian Bunk
2007-01-24 4:50 ` Daniel Barkalow
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=Pine.LNX.4.64.0701241607160.17843@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rankincj@yahoo.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 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®