linux-kernel - Re: [GIT PULL tip:x86/mm] Unify 32 and 64bit NUMA init paths

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110502150401.GA21680@elte.hu>
Date:	Mon, 2 May 2011 17:04:01 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Tejun Heo <tj@...nel.org>
Cc:	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
	x86@...nel.org, Yinghai Lu <yinghai@...nel.org>
Subject: Re: [GIT PULL tip:x86/mm] Unify 32 and 64bit NUMA init paths


* Tejun Heo <tj@...nel.org> wrote:

> Hello, Ingo.
> 
> On Mon, May 02, 2011 at 12:18:28PM +0200, Ingo Molnar wrote:
> > Yeah, it's fine to me if you do merges, but could you please do a x86/mm tree 
> > where all your merge commit messages are amended with a 'Merge reason' 
> > explanation?
> > 
> > See commit a4c98f8bbeafee12c979c90743f6fda94f7515c7 for an example of how Merge 
> > reason lines look like.
> > 
> > This is what we do for all merge commits in the -tip tree - that way it's clear 
> > in retrospect why a particular merge was done.
> 
> Branches updated as suggested.  The new HEAD is 356aec8b6e "x86, NUMA:
> Trim numa meminfo with max_pfn in a separate loop".
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git x86-mm

Doesnt build on 32-bit allyesconfig:

  ERROR: "physnode_map" [drivers/net/wan/dscc4.ko] undefined!
  ERROR: "physnode_map" [crypto/tcrypt.ko] undefined!

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/