From: Ingo Molnar <mingo@elte.hu>
To: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
jbeulich@novell.com, tglx@linutronix.de
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/asm] x86: Remove dead config option X86_CPU
Date: Sat, 5 Mar 2011 09:29:18 +0100 [thread overview]
Message-ID: <20110305082918.GA32531@elte.hu> (raw)
In-Reply-To: <tip-24a2a35a18ebc4e143e86ad3fda50ee78de30d06@git.kernel.org>
* tip-bot for Jan Beulich <JBeulich@novell.com> wrote:
> Commit-ID: 24a2a35a18ebc4e143e86ad3fda50ee78de30d06
> Gitweb: http://git.kernel.org/tip/24a2a35a18ebc4e143e86ad3fda50ee78de30d06
> Author: Jan Beulich <JBeulich@novell.com>
> AuthorDate: Fri, 4 Mar 2011 14:57:48 +0000
> Committer: Ingo Molnar <mingo@elte.hu>
> CommitDate: Fri, 4 Mar 2011 16:34:33 +0100
>
> x86: Remove dead config option X86_CPU
>
> This isn't being referenced anywhere, and the selects done from
> it can be easily done together with all the other X86 ones
This broke UML ...
mm/built-in.o: In function `vm_unmap_aliases':
/home/mingo/tip/mm/vmalloc.c:989: undefined reference to `find_next_bit'
/home/mingo/tip/mm/vmalloc.c:993: undefined reference to `find_next_zero_bit'
/home/mingo/tip/mm/vmalloc.c:1006: undefined reference to `find_next_bit'
Thanks,
Ingo
next prev parent reply other threads:[~2011-03-05 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 14:57 [PATCH] x86: remove dead config option X86_CPU Jan Beulich
2011-03-04 16:00 ` [tip:x86/asm] x86: Remove " tip-bot for Jan Beulich
2011-03-05 8:29 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-08 9:24 [PATCH, v2] x86: remove " Jan Beulich
2011-03-09 11:22 ` [tip:x86/asm] x86: Remove " tip-bot for Jan Beulich
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=20110305082918.GA32531@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--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 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).