From: Ingo Molnar <mingo@elte.hu>
To: linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com,
dwmw2@infradead.org, sam@ravnborg.org, tglx@linutronix.de,
David.Woodhouse@intel.com
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/kbuild] x86: Don't silently override CONFIG_64BIT in 'make oldconfig'
Date: Fri, 4 Sep 2009 16:48:57 +0200 [thread overview]
Message-ID: <20090904144857.GA12872@elte.hu> (raw)
In-Reply-To: <tip-5a8a2d13b1526e306ff2a9fe12dc9d5878d355f9@git.kernel.org>
* tip-bot for David Woodhouse <dwmw2@infradead.org> wrote:
> Commit-ID: 5a8a2d13b1526e306ff2a9fe12dc9d5878d355f9
> Gitweb: http://git.kernel.org/tip/5a8a2d13b1526e306ff2a9fe12dc9d5878d355f9
> Author: David Woodhouse <dwmw2@infradead.org>
> AuthorDate: Tue, 30 Jun 2009 12:10:21 +0100
> Committer: H. Peter Anvin <hpa@zytor.com>
> CommitDate: Thu, 3 Sep 2009 10:57:20 -0700
>
> x86: Don't silently override CONFIG_64BIT in 'make oldconfig'
-tip testing found that this commit broke the UML build:
/home/mingo/tip/arch/um/Makefile:52:
/home/mingo/tip/arch/um/Makefile-x86: No such file or directory
make[1]: *** No rule to make target `/home/mingo/tip/arch/um/Makefile-x86'. Stop.
make: *** [sub-make] Error 2
Ingo
next parent reply other threads:[~2009-09-04 14:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-5a8a2d13b1526e306ff2a9fe12dc9d5878d355f9@git.kernel.org>
2009-09-04 14:48 ` Ingo Molnar [this message]
2009-09-04 15:33 ` [tip:x86/kbuild] x86: Don't silently override CONFIG_64BIT in 'make oldconfig' David Woodhouse
2009-09-04 16:27 ` H. Peter Anvin
2009-09-04 16:38 ` Randy Dunlap
2009-09-04 16:53 ` H. Peter Anvin
2009-09-04 21:40 ` David Woodhouse
2009-09-04 22:54 ` H. Peter Anvin
2009-09-04 18:31 ` Ingo Molnar
2009-09-04 18:57 ` H. Peter Anvin
2009-09-04 19:04 ` H. Peter Anvin
2009-09-11 21:16 ` Jeff Dike
2009-09-14 23:29 ` H. Peter Anvin
2009-09-15 3:33 ` Jeff Dike
2009-09-25 9:03 ` H. Peter Anvin
2009-09-28 4:31 ` Sam Ravnborg
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=20090904144857.GA12872@elte.hu \
--to=mingo@elte.hu \
--cc=David.Woodhouse@intel.com \
--cc=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.