The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Tejun Heo <tj@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	Yinghai Lu <yinghai@kernel.org>
Subject: Re: [GIT PULL tip:x86/mm] Unify 32 and 64bit NUMA init paths
Date: Mon, 2 May 2011 17:04:01 +0200	[thread overview]
Message-ID: <20110502150401.GA21680@elte.hu> (raw)
In-Reply-To: <20110502122319.GC22117@htj.dyndns.org>


* Tejun Heo <tj@kernel.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

  reply	other threads:[~2011-05-02 15:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02  9:13 [GIT PULL tip:x86/mm] Unify 32 and 64bit NUMA init paths Tejun Heo
2011-05-02 10:18 ` Ingo Molnar
2011-05-02 12:23   ` Tejun Heo
2011-05-02 15:04     ` Ingo Molnar [this message]
2011-05-02 15:09       ` Tejun Heo
2011-05-02 15:30         ` Tejun Heo

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=20110502150401.GA21680@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tj@kernel.org \
    --cc=x86@kernel.org \
    --cc=yinghai@kernel.org \
    /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