From: reste donewell <rest@donewell.de>
To: xfs@oss.sgi.com
Subject: Re: Problems with kernel 3.6.x (vm ?) (was : Is kernel 3.6.1 or filestreams option toxic ?)
Date: Wed, 28 Nov 2012 10:39:38 +0100 [thread overview]
Message-ID: <1354095578.31691.19.camel@localhost> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 182 bytes --]
Hi,
The proposed patch, wich works, still hasn't landed in Kernel version
3.6.6.
I think it should go to stable release.
Anybody working on this ?
Thanks in advance,
Eric Thiele
[-- Attachment #1.2: Type: text/html, Size: 442 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-11-28 9:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 9:39 reste donewell [this message]
2012-11-28 20:37 ` Problems with kernel 3.6.x (vm ?) (was : Is kernel 3.6.1 or filestreams option toxic ?) Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2012-10-22 14:14 Is kernel 3.6.1 or filestreams option toxic ? Yann Dupont
2012-10-23 8:24 ` Problems with kernel 3.6.x (vm ?) (was : Is kernel 3.6.1 or filestreams option toxic ?) Yann Dupont
2012-10-23 8:24 ` Yann Dupont
2012-10-25 15:21 ` Yann Dupont
2012-10-25 20:55 ` Yann Dupont
2012-10-25 21:10 ` Dave Chinner
2012-10-26 10:03 ` Yann Dupont
2012-10-26 22:05 ` Yann Dupont
2012-10-28 23:48 ` Dave Chinner
2012-10-29 1:25 ` Dave Chinner
2012-10-29 8:11 ` Yann Dupont
2012-10-29 12:21 ` Dave Chinner
2012-10-29 12:18 ` Dave Chinner
2012-10-29 12:43 ` Yann Dupont
2012-10-30 1:33 ` Dave Chinner
2012-10-31 11:45 ` Gaudenz Steinlin
2012-11-05 13:57 ` Yann Dupont
2012-10-29 8:07 ` Yann Dupont
2012-10-29 8:17 ` Yann Dupont
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=1354095578.31691.19.camel@localhost \
--to=rest@donewell.de \
--cc=xfs@donewell.de \
--cc=xfs@oss.sgi.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 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.