linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org,
	Vegard Nossum <vegard.nossum@gmail.com>,
	Pekka Enberg <penberg@cs.helsinki.fi>, Pekka Paalanen <pq@iki.fi>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: manual merge of the kmemcheck tree
Date: Thu, 3 Jul 2008 08:26:57 +0200	[thread overview]
Message-ID: <20080703062657.GA26365@elte.hu> (raw)
In-Reply-To: <20080703161236.368d7926.sfr@canb.auug.org.au>


* Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Ingo,
> 
> Today's linux-next merge of the kmemcheck tree got a conflict in 
> arch/x86/mm/Makefile between commit 
> ff3a3e9ba5e4273a8bc10570adab4a390fb90757 ("x86 mmiotrace: move files 
> into arch/x86/mm/") from the ftrace tree and commit 
> 385e31b9eae0528bada07d16a189f3f40df23961 ("kmemcheck: add the 
> kmemcheck core") from the kmemcheck tree.
> 
> Just overlapping additions.

thanks Stephen. These are the conflict resolutions i've been carrying 
for a few months:

    Merge branch 'kmemcheck' into auto-latest

    Conflicts:

        arch/x86/mm/Makefile
        include/asm-x86/pgtable.h
        kernel/sysctl.c

the arch/x86/mm/Makefile and kernel/sysctl.c ones are trivial - but the 
pgtable.h is non-trivial: you might want to glean the resolution out of 
tip/auto-latest.

Shortly before the release of a stable kernel is the 'maximum dynamic 
pressure' point of the launch of the next Linux version - this is when 
the highest number of conflicts arise. [ And i hope these three are not 
too bad to break the rocket apart ;-) ]

	Ingo

  reply	other threads:[~2008-07-03  6:27 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03  6:12 linux-next: manual merge of the kmemcheck tree Stephen Rothwell
2008-07-03  6:26 ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-03  6:19 Stephen Rothwell
2008-07-11  6:32 Stephen Rothwell
2008-07-21  6:47 Stephen Rothwell
2008-07-22  6:16 Stephen Rothwell
2008-07-22  6:52 ` Ingo Molnar
2008-07-22  8:18   ` 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-28  4:09 Stephen Rothwell
2008-07-28  9:06 ` Ingo Molnar
2008-07-28 17:19   ` Stephen Rothwell
2008-08-13  5:22 Stephen Rothwell
2008-08-13  5:26 Stephen Rothwell
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-15  6:45 Stephen Rothwell
2008-08-15  6:43 ` Pekka Enberg
2008-08-15  8:17   ` Ingo Molnar
     [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-20  6:40 Stephen Rothwell
2008-10-21  5:15 Stephen Rothwell
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-28  5:14 Stephen Rothwell
2008-10-28  8:15 ` Ingo Molnar
2008-12-30 12:14 Stephen Rothwell
2008-12-30 12:18 Stephen Rothwell

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=20080703062657.GA26365@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-next@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=pq@iki.fi \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    --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).