From: Bill Davidsen <davidsen@tmr.com>
To: Greg KH <gregkh@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.16.11
Date: Thu, 27 Apr 2006 17:51:23 -0400 [thread overview]
Message-ID: <44513CDB.4050104@tmr.com> (raw)
In-Reply-To: <20060424203358.GA17597@kroah.com>
Greg KH wrote:
> We (the -stable team) are announcing the release of the 2.6.16.11 kernel
> (because just one -stable kernel a day is obviously not enough...)
>
> The diffstat and short summary of the fixes are below.
>
> I'll also be replying to this message with a copy of the patch between
> 2.6.16.10 and 2.6.16.11, as it is small enough to do so.
>
> The updated 2.6.16.y git tree can be found at:
> rsync://rsync.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.16.y.git
> and can be browsed at the normal kernel.org git web browser:
> www.kernel.org/git/
>
> thanks,
>
> greg k-h
Looks good, I dropped it on an ASUS laptop running FC4 and everything
works, including the selinux stuff. However, I did note these things:
1 - sounds has stopped working on the FC4 kernel (again) 2.6.16.11 ok
2 - at boot, the 2.6.16.11 kernel stops after the "storage" text in the
"initializing" line, and hangs long enough for me to say "Oh .... it
hung" before continuing.
3 - ipw2200 wireless continues to work flawlessly. I mention this
because there was a time when every patch was an adventure.
Thanks for the patches.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
prev parent reply other threads:[~2006-05-02 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 20:33 Linux 2.6.16.11 Greg KH
2006-04-24 20:35 ` Greg KH
2006-04-24 21:24 ` Nick Warne
2006-04-27 21:51 ` Bill Davidsen [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=44513CDB.4050104@tmr.com \
--to=davidsen@tmr.com \
--cc=gregkh@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox