public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@googlemail.com>
To: Thorsten Glaser <tg@mirbsd.de>
Cc: Michael Schmitz <schmitzmic@googlemail.com>,
	KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
	David Rientjes <rientjes@google.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Roman Zippel <zippel@linux-m68k.org>,
	linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org,
	schwab@linux-m68k.org
Subject: Re: [patch] m68k, mm: set all online nodes in N_NORMAL_MEMORY
Date: Mon, 25 Apr 2011 14:41:35 +1200	[thread overview]
Message-ID: <4DB4DF5F.809@gmail.com> (raw)
In-Reply-To: <Pine.BSM.4.64L.1104241131460.8787@herc.mirbsd.org>

Hello Thorsten,
>> Tested on my ARAnyM test setup so far. I'd like to wait for an independent
>> kernel image built by Thorsten before I test on the actual hardware. Sorry but
>> you'll have to restart your build Thorsten :-)
>>     
>
> Heh okay, if you want. But only cross-compiling :D
>   
Thought so. That's fine actually. Your cross toolchain will be a lot 
more recent than mine.
>
> KOSAKI Motohiro dixit:
>
>   
>> I think you are right. however I doubt m68k need to care memoryless node check.
>> probably following patch just work.
>>     
>
> That’s what we have now. Compiles, boots, works fine.
>
>
> So, which of these do you guys want?
>   
Whatever is cleaner and easier to understand. I'm a poor judge of code 
elegance.

Cheers,

  Michael

  reply	other threads:[~2011-04-25  2:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1303317178.2587.30.camel@mulgrave.site>
     [not found] ` <alpine.DEB.2.00.1104201410350.31768@chino.kir.corp.google.com>
     [not found]   ` <20110421220351.9180.A69D9226@jp.fujitsu.com>
     [not found]     ` <alpine.DEB.2.00.1104211237250.5829@chino.kir.corp.google.com>
     [not found]       ` <alpine.DEB.2.00.1104211500170.5741@router.home>
     [not found]         ` <alpine.DEB.2.00.1104211411540.20201@chino.kir.corp.google.com>
2011-04-21 22:02           ` [patch] m68k, mm: set all online nodes in N_NORMAL_MEMORY David Rientjes
2011-04-24  1:59             ` Michael Schmitz
2011-04-24  3:14               ` KOSAKI Motohiro
2011-04-24  4:01                 ` Michael Schmitz
2011-04-24  5:05                   ` Michael Schmitz
2011-04-24  6:04                     ` KOSAKI Motohiro
2011-04-24 11:32                 ` Thorsten Glaser
2011-04-25  2:41                   ` Michael Schmitz [this message]
2011-04-25 14:22                     ` Thorsten Glaser
2011-04-24 12:18               ` Thorsten Glaser
2011-04-25 20:56               ` David Rientjes
2011-04-26  2:51                 ` Michael Schmitz
2011-04-26 10:50                   ` Thorsten Glaser
2011-04-27 13:19                     ` Geert Uytterhoeven
2011-04-27 15:09                       ` Thorsten Glaser
2011-04-27 15:11                       ` Thorsten Glaser
2011-04-28  2:35                         ` Ben Hutchings
2011-04-28  3:05                       ` Michael Schmitz

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=4DB4DF5F.809@gmail.com \
    --to=schmitzmic@googlemail.com \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=kosaki.motohiro@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=rientjes@google.com \
    --cc=schwab@linux-m68k.org \
    --cc=tg@mirbsd.de \
    --cc=zippel@linux-m68k.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