From: Andrew Morton <akpm@osdl.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org, marcelo.tosatti@cyclades.com,
lee.schermerhorn@hp.com
Subject: Re: page migration reorg patch
Date: Wed, 15 Mar 2006 19:34:59 -0800 [thread overview]
Message-ID: <20060315193459.74993bfc.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0603151828001.30650@schroedinger.engr.sgi.com>
Christoph Lameter <clameter@sgi.com> wrote:
>
> On Wed, 15 Mar 2006, Andrew Morton wrote:
>
> > If you can rework this patch against
> > http://www.zip.com.au/~akpm/linux/patches/stuff/x.bz2 (my current queue up
> > to and including slab-leaks3-locking-fix.patch, against 2.6.16-rc6) then
> > I'll be able to insert it in the right place and then fix up subsequent
> > fallout, thanks.
>
> BTW compilation fails with:
>
> drivers/scsi/sata_vsc.c: At top level:
> drivers/scsi/sata_vsc.c:254: unknown field `eh_timed_out' specified in
> initializer
> drivers/scsi/sata_vsc.c:254: warning: initialization from incompatible
> pointer type
>
That's fairly typical for a new batch of git pulls :(
>
> The patch (including the two amendments) against the x.bz2 patch:
Thanks for doing that.
Yes, mm/mempolicy.c did get a bit uglified.
--
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:[~2006-03-16 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 1:42 Christoph Lameter
2006-03-16 1:48 ` Christoph Lameter
2006-03-16 1:59 ` Christoph Lameter
2006-03-16 1:55 ` Andrew Morton
2006-03-16 2:32 ` Christoph Lameter
2006-03-16 3:34 ` Andrew Morton [this message]
2006-03-16 9:31 ` Andrew Morton
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=20060315193459.74993bfc.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-mm@kvack.org \
--cc=marcelo.tosatti@cyclades.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