From: CaT <cat@zip.com.au>
To: Chris Wright <chrisw@sous-sol.org>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org, torvalds@osdl.org
Subject: Re: Linux 2.6.15.1
Date: Mon, 16 Jan 2006 11:09:23 +1100 [thread overview]
Message-ID: <20060116000923.GL2035@zip.com.au> (raw)
In-Reply-To: <20060115235125.GN3335@sorel.sous-sol.org>
On Sun, Jan 15, 2006 at 03:51:25PM -0800, Chris Wright wrote:
> * CaT (cat@zip.com.au) wrote:
> > Was there a fix for the 2.6.16 cfq issues? It's a bad idea for me to use
> > AS on servers as it does weird things on the hardware we have (as I've
> > previously reported).
>
> There's one relevant fix queued up for next -stable from
> this thread:
Cool.
> http://marc.theaimsgroup.com/?t=113657885100003&r=1&w=2
>
> Is that what you're referring to?
Yup, thanks. That's the bug I was referring to.
--
"To the extent that we overreact, we proffer the terrorists the
greatest tribute."
- High Court Judge Michael Kirby
prev parent reply other threads:[~2006-01-16 0:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 7:04 Linux 2.6.15.1 Chris Wright
2006-01-15 7:06 ` Chris Wright
2006-01-15 8:08 ` CaT
2006-01-15 23:51 ` Chris Wright
2006-01-16 0:09 ` CaT [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=20060116000923.GL2035@zip.com.au \
--to=cat@zip.com.au \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@osdl.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