public inbox for linux-next@vger.kernel.org 
 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,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix•com>,
	Yinghai Lu <yinghai@kernel•org>
Subject: linux-next: manual merge of the kmemcheck tree with the x86 tree
Date: Thu, 19 Mar 2009 18:49:46 +1100	[thread overview]
Message-ID: <20090319184946.de4d75f5.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 726 bytes --]

Hi all,

Today's linux-next merge of the kmemcheck tree got a conflict in
arch/x86/kernel/head_32.S between commits
2bd2753ff46346543ab92e80df9d96366e21baa5 ("x86: put initial_pg_tables
into .bss") and c090f532db3ab5b7be503f8ac84b0d33a18646c6 ("x86-32: make
sure we map enough to fit linear map pagetables") from the x86 tree and
commit a7fff94fffaa0cecb923d6c1bb9b7691f608b49a ("Revert "kmemcheck: use
set_memory_4k() instead of disabling PSE"") from the kmemcheck tree.

I fixed it up (by using the version from the x86 tree - which is also
what is done in tip/master) and can carry the fix as necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-03-19  7:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19  7:49 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-01  7:55 linux-next: manual merge of the kmemcheck tree with the x86 tree Stephen Rothwell
2009-03-06  6:24 Stephen Rothwell
2009-03-06  6:19 Stephen Rothwell
2009-03-06  6:04 Stephen Rothwell
2009-01-23  4:44 Stephen Rothwell
2009-01-23 14:21 ` Pekka Enberg
2009-01-23 15:53   ` 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=20090319184946.de4d75f5.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=jeremy.fitzhardinge@citrix$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mingo@elte$(echo .)hu \
    --cc=penberg@cs$(echo .)helsinki.fi \
    --cc=vegard.nossum@gmail$(echo .)com \
    --cc=yinghai@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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