From: Jeff Licquia <licquia@debian.org>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: Hugh Dickins <hugh@veritas.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
394392@bugs.debian.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: Alternative msync() fix for 2.6.18?
Date: Wed, 03 Jan 2007 09:32:07 -0500 [thread overview]
Message-ID: <1167834727.3798.6.camel@xenpc.internal.licquia.org> (raw)
In-Reply-To: <20061229140107.GG2062@deprecation.cyrius.com>
On Fri, 2006-12-29 at 15:01 +0100, Martin Michlmayr wrote:
> Yes, I agree. I'm CCing the linux-mm list in hope that someone can
> review your patch. In the meantime, I've asked the Debian LSB folks to
> verify that your patch fixes the LSB problem.
I am running the complete lsb-runtime-test suite against the new kernels
(as installed yesterday from the sid apt repo at
http://kernel-archive.buildserver.net/debian-kernel), but I also did a
run with just the msync test, which passed. I will report the results
for the full suite when they become available.
FWIW, here's uname:
Linux xenpc 2.6.18-4-xen-686 #1 SMP Mon Jan 1 02:33:53 UTC 2007 i686 GNU/Linux
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-01-03 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061226123106.GA32708@deprecation.cyrius.com>
[not found] ` <Pine.LNX.4.64.0612261305510.18364@blonde.wat.veritas.com>
[not found] ` <20061226132547.GC6256@deprecation.cyrius.com>
[not found] ` <Pine.LNX.4.64.0612261411580.20159@blonde.wat.veritas.com>
[not found] ` <Pine.LNX.4.64.0612270104020.11930@blonde.wat.veritas.com>
2006-12-29 14:01 ` Martin Michlmayr
2007-01-03 14:32 ` Jeff Licquia [this message]
2007-01-04 13:35 ` Jeff Licquia
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=1167834727.3798.6.camel@xenpc.internal.licquia.org \
--to=licquia@debian.org \
--cc=394392@bugs.debian.org \
--cc=a.p.zijlstra@chello.nl \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tbm@cyrius.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