linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Vegard Nossum <vegard.nossum@gmail.com>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Ingo Molnar <mingo@elte.hu>
Cc: linux-next@vger.kernel.org, Akinobu Mita <akinobu.mita@gmail.com>
Subject: linux-next: manual merge of the kmemcheck tree
Date: Tue, 30 Dec 2008 23:14:52 +1100	[thread overview]
Message-ID: <20081230231452.8c8b9c58.sfr@canb.auug.org.au> (raw)

Hi all,

Today's linux-next merge of the kmemcheck tree got a conflict in
mm/Makefile between commit 773ff60e841461cb1f9374a713ffcda029b8c317
("SLUB: failslab support") from the slab tree and commit
e6df1035b1b488cafde1e69f1a25f2706c3ac1f7 ("kmemcheck: add mm functions")
from the kmemcheck tree.

I fixed it up (see below) and can carry the fix as necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

diff --cc mm/Makefile
index 51c2770,399aaf1..0000000
--- a/mm/Makefile
+++ b/mm/Makefile
@@@ -28,7 -28,7 +28,8 @@@ obj-$(CONFIG_SLOB) += slob.
  obj-$(CONFIG_MMU_NOTIFIER) += mmu_notifier.o
  obj-$(CONFIG_SLAB) += slab.o
  obj-$(CONFIG_SLUB) += slub.o
 +obj-$(CONFIG_FAILSLAB) += failslab.o
+ obj-$(CONFIG_KMEMCHECK) += kmemcheck.o
  obj-$(CONFIG_MEMORY_HOTPLUG) += memory_hotplug.o
  obj-$(CONFIG_FS_XIP) += filemap_xip.o
  obj-$(CONFIG_MIGRATION) += migrate.o

             reply	other threads:[~2008-12-30 12:14 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30 12:14 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-30 12:18 linux-next: manual merge of the kmemcheck tree Stephen Rothwell
2008-10-28  5:14 Stephen Rothwell
2008-10-28  8:15 ` Ingo Molnar
2008-10-21  5:29 Stephen Rothwell
2008-10-21  7:32 ` Ingo Molnar
2008-10-21  8:07   ` Vegard Nossum
2008-10-21  8:28     ` Ingo Molnar
2008-10-21  5:15 Stephen Rothwell
2008-08-20  6:40 Stephen Rothwell
     [not found] <20080815164909.3d8beb10.sfr@canb.auug.org.au>
2008-08-15  7:04 ` Vegard Nossum
2008-08-15  8:00   ` Stephen Rothwell
2008-08-15  6:45 Stephen Rothwell
2008-08-15  6:43 ` Pekka Enberg
2008-08-15  8:17   ` Ingo Molnar
2008-08-13  5:29 Stephen Rothwell
2008-08-13  7:32 ` Ingo Molnar
2008-08-13  7:31   ` Pekka Enberg
2008-08-13  7:58     ` Ingo Molnar
2008-08-13  8:14       ` Pekka Enberg
2008-08-13  8:58         ` Ingo Molnar
2008-08-13 11:37           ` Pekka Enberg
2008-08-13 11:52             ` Ingo Molnar
2008-08-13 11:57               ` Pekka Enberg
2008-08-13 12:05                 ` Ingo Molnar
2008-08-13  7:41   ` Stephen Rothwell
2008-08-13  5:26 Stephen Rothwell
2008-08-13  5:22 Stephen Rothwell
2008-07-28  4:09 Stephen Rothwell
2008-07-28  9:06 ` Ingo Molnar
2008-07-28 17:19   ` Stephen Rothwell
2008-07-28  4:01 Stephen Rothwell
2008-07-28  9:05 ` Ingo Molnar
2008-07-28  9:17   ` Vegard Nossum
2008-07-28  9:29     ` Ingo Molnar
2008-07-22  6:16 Stephen Rothwell
2008-07-22  6:52 ` Ingo Molnar
2008-07-22  8:18   ` Stephen Rothwell
2008-07-21  6:47 Stephen Rothwell
2008-07-11  6:32 Stephen Rothwell
2008-07-03  6:19 Stephen Rothwell
2008-07-03  6:12 Stephen Rothwell
2008-07-03  6:26 ` Ingo Molnar

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=20081230231452.8c8b9c58.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akinobu.mita@gmail.com \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    --cc=vegard.nossum@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).