linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Hirokazu Takata <takata@linux-m32r.org>
Cc: linux-kernel@vger.kernel.org, fujiwara@linux-m32r.org,
	takata@linux-m32r.org
Subject: Re: [PATCH 2.6.17-rc1-mm1] m32r: Fix cpu_possible_map and cpu_present_map initialization for SMP kernel
Date: Fri, 7 Apr 2006 15:03:37 -0700	[thread overview]
Message-ID: <20060407150337.7cc0c462.akpm@osdl.org> (raw)
In-Reply-To: <20060407.194745.233672521.takata.hirokazu@renesas.com>

Hirokazu Takata <takata@linux-m32r.org> wrote:
>
> This patch fixes a boot problem of the m32r SMP kernel
> 2.6.16-rc1-mm3 or later.

This sounds like something which needs to be backported into 2.6.16.x,
correct?

Also, should "m32r: security fix of {get,put}_user macros" go into 2.6.16.x?

  reply	other threads:[~2006-04-07 22:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-07 10:47 [PATCH 2.6.17-rc1-mm1] m32r: Fix cpu_possible_map and cpu_present_map initialization for SMP kernel Hirokazu Takata
2006-04-07 22:03 ` Andrew Morton [this message]
2006-04-10  0:37   ` Hirokazu Takata

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=20060407150337.7cc0c462.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=fujiwara@linux-m32r.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=takata@linux-m32r.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;
as well as URLs for NNTP newsgroup(s).