From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [signal:master 8/62] arch/arm/include/asm/ptrace.h:260:35: error: 'THREAD_SIZE' undeclared (firs
Date: Sat, 08 Sep 2012 12:34:01 +0000 [thread overview]
Message-ID: <20120908123401.GB24182@localhost> (raw)
In-Reply-To: <20120907235029.GB17069@localhost>
On Sat, Sep 08, 2012 at 07:47:04AM +0100, Al Viro wrote:
> On Sat, Sep 08, 2012 at 07:50:29AM +0800, Fengguang Wu wrote:
> > Hi Al,
> >
> > FYI, kernel build failed on
> >
> > tree: git://git.kernel.org/pub/scm/linux/kernel/git/viro/signal.git master
> > head: 811a6550c2567601b6ea4799a44732f7dbab4807
> > commit: 63840b3cbdf5993b776138111a6b3a0cfb745caa [8/62] arm: optimized current_pt_regs()
> > config: arm-allnoconfig (attached as .config)
>
> Ho-hum... That's solved by turning that sucker into a macro, but allnoconfig
> *still* doesn't build - we end up with no CONFIG_CPU_... defined, which
> leads to very unhappy build. Anyway, the mess with undefined symbol had
> been fixed in my tree (will push shortly), but allnoconfig is a mess I don't
> want to touch right now - too convoluted Kconfig crap for my taste...
Fair enough, arm-allnoconfig is not really working well now and let's
leave it to the arm maintainers ...
Thanks,
Fengguang
prev parent reply other threads:[~2012-09-08 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 23:50 [signal:master 8/62] arch/arm/include/asm/ptrace.h:260:35: error: 'THREAD_SIZE' undeclared (first us Fengguang Wu
2012-09-08 6:47 ` [signal:master 8/62] arch/arm/include/asm/ptrace.h:260:35: error: 'THREAD_SIZE' undeclared (firs Al Viro
2012-09-08 12:34 ` Fengguang Wu [this message]
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=20120908123401.GB24182@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@vger.kernel.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 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.