From: Josh Triplett <josh@joshtriplett.org>
To: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
kbuild test robot <fengguang.wu@intel.com>
Subject: Re: undefined reference to `printk'
Date: Sat, 11 Jun 2016 21:38:10 -0700 [thread overview]
Message-ID: <20160612043810.GA1326@x> (raw)
In-Reply-To: <201606121058.3CeznQLn%fengguang.wu@intel.com>
[Adding LKML, linux-arch, and Linus.]
On Sun, Jun 12, 2016 at 10:17:01AM +0800, kbuild test robot wrote:
> All errors (new ones prefixed by >>):
>
> arch/m32r/kernel/built-in.o: In function `default_eit_handler':
> >> (.text+0x3f8): undefined reference to `printk'
> arch/m32r/kernel/built-in.o: In function `default_eit_handler':
> (.text+0x3f8): relocation truncated to fit: R_M32R_26_PCREL_RELA against undefined symbol `printk'
As far as I can tell, there has been a patch available for this for
months, and it still doesn't seem to have been applied anywhere.
m32r is listed in MAINTAINERS as "Orphan", and has been since commit
b4174867bee83e79dc155479cb1b67c452da6476 in 2014. And that commit
in turn observed no commits from the maintainer since 2009. Looking at
the log for arch/m32r, I don't see any activity other than random fixes
by others, and based on the signoffs, all of those seem to go through
miscellaneous trees.
Is anyone using m32r? Is anyone willing to maintain it? And if not,
should we consider removing it?
- 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:[~2016-06-12 4:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 2:17 undefined reference to `printk' kbuild test robot
2016-06-12 4:38 ` Josh Triplett [this message]
2016-06-27 5:26 ` Yoshinori Sato
-- strict thread matches above, loose matches on Subject: below --
2016-09-25 3:40 kbuild test robot
2016-09-25 3:46 ` Joe Perches
2016-09-26 1:54 ` Fengguang Wu
2016-07-27 20:56 kbuild test robot
2016-07-19 9:10 kbuild test robot
2016-07-03 15:39 kbuild test robot
2016-06-26 1:19 kbuild test robot
2016-06-27 5:14 ` Yoshinori Sato
2016-06-05 0:43 kbuild test robot
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=20160612043810.GA1326@x \
--to=josh@joshtriplett.org \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).