From: "David C. Rankin" <drankinatty@suddenlinkmail.com>
To: kernel <linux-kernel@vger.kernel.org>
Subject: Re: Upgrade to recent 2.6.35 & 2.6.36 kernel causing boot failure with nv dmraid
Date: Tue, 09 Nov 2010 11:48:06 -0600 [thread overview]
Message-ID: <4CD98956.4030602@suddenlinkmail.com> (raw)
In-Reply-To: <4CD3D57C.2000002@suddenlinkmail.com>
On 11/05/2010 04:59 AM, David C. Rankin wrote:
> Anybody have even a guess on this one? I guarantee you, your guess will be much
> appreciated. (see the original post for details) Thanks.
Guys,
If anyone has a thought on this in the future, "please cc: me directly." I'm
going to go ahead and unsubscribe to cut down on mail volume. I knew this issue
was hit or miss whether a possible cause would stand out. Any ideas or help is
always appreciated. Thanks to all for looking at the thread.
--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
prev parent reply other threads:[~2010-11-09 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 5:53 Upgrade to recent 2.6.35 & 2.6.36 kernel causing boot failure with nv dmraid David C. Rankin
2010-11-04 6:12 ` David C. Rankin
2010-11-05 9:59 ` David C. Rankin
2010-11-09 17:48 ` David C. Rankin [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=4CD98956.4030602@suddenlinkmail.com \
--to=drankinatty@suddenlinkmail.com \
--cc=linux-kernel@vger.kernel.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.