From: "Akinobu Mita" <akinobu.mita@gmail.com>
To: linux-ia64@vger.kernel.org
Subject: Re: fault-injection framework on ia64
Date: Fri, 16 Feb 2007 17:30:53 +0000 [thread overview]
Message-ID: <961aa3350702160930i63e1e64vd57130c1f05eb7f9@mail.gmail.com> (raw)
In-Reply-To: <20070215041554.8e9c92aa.akpm@linux-foundation.org>
> But if STACKTRACE depends on STACKTRACE_SUPPORT, which isn't defined on ia64,
> kconfig should disable FAULT_INJECTION altogether with my patch (as it did
> before it). I don't think that FAULT_INJECTION could be enabled before my
> patch, right?
>
> _BUT_ probably STACKTRACE_SUPPORT should be defined, with default n and no
> prompt, on ia64, or Kconfig gets confused (it should output a warning,
> like 'undefined symbol STACKTRACE_SUPPORT'). We on UML used to get warning
> when INPUT was used but not defined. Hmmm....
Really? I intentionaly removed the STACKTRACE_SUPPORT in x86_64 Kconfig, then
I did make menuconfig. But I didn't get such warning.
prev parent reply other threads:[~2007-02-16 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 12:15 fault-injection framework on ia64 Andrew Morton
2007-02-15 12:44 ` Akinobu Mita
2007-02-15 13:17 ` Andrew Morton
2007-02-15 13:25 ` Akinobu Mita
2007-02-15 19:43 ` Blaisorblade
2007-02-16 17:30 ` Akinobu Mita [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=961aa3350702160930i63e1e64vd57130c1f05eb7f9@mail.gmail.com \
--to=akinobu.mita@gmail.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox