From: Josh Triplett <josh@joshtriplett.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
kbuild-all@01.org
Subject: Re: [mmotm:master 326/350] undefined reference to `tty_write_message'
Date: Tue, 25 Feb 2014 23:07:45 -0800 [thread overview]
Message-ID: <20140226070745.GA8078@thin> (raw)
In-Reply-To: <530d8dd5.N73la/TcxHdsINPu%fengguang.wu@intel.com>
On Wed, Feb 26, 2014 at 02:46:45PM +0800, kbuild test robot wrote:
> tree: git://git.cmpxchg.org/linux-mmotm.git master
> head: a6a1126d3535f0bd8d7c56810061541a4f5595af
> commit: 5837644fad4fdcc7a812eb1f3a215d8196628627 [326/350] kconfig: make allnoconfig disable options behind EMBEDDED and EXPERT
> config: make ARCH=ia64 allnoconfig
>
> All error/warnings:
>
> arch/ia64/kernel/built-in.o: In function `ia64_handle_unaligned':
> >> (.text+0x1b882): undefined reference to `tty_write_message'
Looks like ia64 is broken with CONFIG_TTY=n. Why in the world does
arch/ia64/kernel/unaligned.c call tty_write_message on the tty of the
current process? That's just *wrong*.
Would anything go horribly wrong if the tty_write_message just went
away, leaving only the printk? (Bonus: no need to sprintf first.)
- Josh Triplett
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-02-26 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 6:46 [mmotm:master 326/350] undefined reference to `tty_write_message' kbuild test robot
2014-02-26 7:07 ` Josh Triplett [this message]
2014-02-26 10:15 ` [PATCH] ia64: select CONFIG_TTY for use of tty_write_message in unaligned Josh Triplett
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=20140226070745.GA8078@thin \
--to=josh@joshtriplett.org \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).