public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: akpm@osdl.org, jamagallon@ono.com, linux-kernel@vger.kernel.org,
	sam@ravnborg.org
Subject: Re: [PATCH] ignore smp_locks section warnings from init/exit code
Date: Thu, 8 Jun 2006 00:21:09 -0400	[thread overview]
Message-ID: <20060608042109.GA6337@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20060607193225.989add4c.rdunlap@xenotime.net>

On Wed, Jun 07, 2006 at 07:32:25PM -0700, Randy.Dunlap wrote:
> > make ARCH=um allmodconfig
> /var/linsrc/linux-2617-rc6mm1/arch/um/Makefile:113: *** missing separator.  Stop.
> 
> is that known/fixed?

No.  rc6-mm1 builds fine here.  I just checked with a fresh tree.

Are you sure you have a clean tree?

				Jeff

  reply	other threads:[~2006-06-08  4:21 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-07 17:47 2.6.17-rc6-mm1 Andrew Morton
2006-06-07 21:23 ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 22:07   ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-07 22:36     ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 23:54     ` 2.6.17-rc6-mm1 Stefan Richter
2006-06-08  0:31       ` 2.6.17-rc6-mm1 Chris Wright
2006-06-08  6:30         ` 2.6.17-rc6-mm1 Stefan Richter
2006-06-08  7:26       ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-07 21:54 ` 2.6.17-rc6-mm1 Rafael J. Wysocki
2006-06-07 22:11   ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-08  3:19     ` 2.6.17-rc6-mm1 Valdis.Kletnieks
2006-06-08 15:13       ` lockdep wierdness - was 2.6.17-rc6-mm1 Valdis.Kletnieks
2006-06-08 10:06     ` NTFS possible circular locking deadlock (Was: Re: 2.6.17-rc6-mm1) Duncan Sands
2006-06-12 14:35       ` Ingo Molnar
2006-06-08 12:54     ` 2.6.17-rc6-mm1 Rafael J. Wysocki
2006-06-07 22:31 ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 22:40   ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-07 23:23     ` [PATCH] ignore smp_locks section warnings from init/exit code Randy.Dunlap
2006-06-08  0:04       ` Randy.Dunlap
2006-06-08  2:11       ` Jeff Dike
2006-06-08  2:32         ` Randy.Dunlap
2006-06-08  4:21           ` Jeff Dike [this message]
2006-06-08  4:29             ` Randy.Dunlap
2006-06-08 15:44               ` Randy.Dunlap
2006-06-08 18:35         ` Sam Ravnborg
2006-06-11 23:25           ` Jeff Dike
2006-06-12  0:17             ` Randy.Dunlap
2006-06-12  2:29               ` Jeff Dike
2006-06-12  2:52                 ` Randy.Dunlap
2006-06-08  2:25     ` 2.6.17-rc6-mm1 Andi Kleen
2006-06-08  2:46       ` 2.6.17-rc6-mm1 Randy.Dunlap
2006-06-08  5:43         ` 2.6.17-rc6-mm1 Andi Kleen
2006-06-08  6:46       ` 2.6.17-rc6-mm1 Gerd Hoffmann
2006-06-07 23:14 ` 2.6.17-rc6-mm1 Martin Bligh
2006-06-07 23:55   ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-08  1:09     ` 2.6.17-rc6-mm1 Grant Coady
2006-06-08  5:00 ` 2.6.17-rc6-mm1 Dave Jones
2006-06-20 17:42   ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-20 20:24     ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-20 20:38       ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-21  6:23     ` 2.6.17-rc6-mm1 Dave Jones
2006-06-21  8:15       ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-21 18:42         ` 2.6.17-rc6-mm1 Dave Jones

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=20060608042109.GA6337@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=akpm@osdl.org \
    --cc=jamagallon@ono.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=sam@ravnborg.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