LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm snapshot broken-out-2007-03-18-02-44.tar.gz uploaded
Date: Tue, 20 Mar 2007 13:47:53 +1100	[thread overview]
Message-ID: <45FF4B59.3060107@yahoo.com.au> (raw)
In-Reply-To: <20070319180234.6b7826b2.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Mon, 19 Mar 2007 17:58:52 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
> 
> 
>>The kernel without Nick's patchset but with the assert runs OK too.  Under
>>the principle of mm-has-been-too-flakey-lately, I'll drop the patches:
>>
>>mm-debug-check-for-the-fault-vs-invalidate-race.patch
>>mm-simplify-filemap_nopage.patch
>>mm-fix-fault-vs-invalidate-race-for-linear-mappings.patch
>>mm-merge-populate-and-nopage-into-fault-fixes-nonlinear.patch
>>mm-merge-populate-and-nopage-into-fault-fixes-nonlinear-tidy.patch
>>mm-merge-nopfn-into-fault.patch
>>mm-merge-nopfn-into-fault-fix.patch
>>mm-remove-legacy-cruft.patch
> 
> 
> ug, too many rejects.  I'll leave them in, minus
> mm-debug-check-for-the-fault-vs-invalidate-race.patch
> 

Hang on a sec... I'll try fixing the thing before you next make a
release.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2007-03-20  2:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200703180946.l2I9kTVc020636@shell0.pdx.osdl.net>
2007-03-18 18:35 ` mm snapshot broken-out-2007-03-18-02-44.tar.gz uploaded Michal Piotrowski
     [not found]   ` <6bffcb0e0703190845s6bdc1a65p71937d1dffbf6d9e@mail.gmail.com>
2007-03-19 15:54     ` Pekka J Enberg
2007-03-19 16:29       ` Michal Piotrowski
2007-03-19 16:34         ` Michal Piotrowski
2007-03-19 16:39           ` Pekka J Enberg
2007-03-19 16:38         ` Pekka J Enberg
2007-03-19 16:45           ` Michal Piotrowski
     [not found]             ` <6bffcb0e0703191024w527638f8yacc3a8fea9fd451d@mail.gmail.com>
2007-03-19 18:02               ` Michal Piotrowski
2007-03-19 18:10                 ` Pekka J Enberg
2007-03-19 19:27                   ` Michal Piotrowski
2007-03-19 23:25   ` Andrew Morton
2007-03-20 11:43     ` Sam Ravnborg
2007-03-19 19:23 ` Michal Piotrowski
2007-03-19 21:08   ` Andrew Morton
     [not found]     ` <6bffcb0e0703191437i2ee706d4xaec3bc11ca7c3234@mail.gmail.com>
2007-03-20  1:58       ` Andrew Morton
2007-03-20  2:02         ` Andrew Morton
2007-03-20  2:47           ` Nick Piggin [this message]
2007-03-20  4:56             ` Andrew Morton
2007-03-20  5:17               ` Nick Piggin
2007-03-20  5:18                 ` Nick Piggin
2007-03-20  9:07                 ` Michal Piotrowski
2007-03-19 19:56 ` Michal Piotrowski
2007-03-20  7:17 ` Michal Piotrowski
2007-03-20 16:36   ` Andrew Morton
2007-03-20 18:22     ` Andi Kleen

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=45FF4B59.3060107@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.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;
as well as URLs for NNTP newsgroup(s).