linux-kernel - Re: undefined reference to `printk'

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 27 Jun 2016 14:26:27 +0900
From:	Yoshinori Sato <ysato@...rs.sourceforge.jp>
To:	Josh Triplett <josh@...htriplett.org>
Cc:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	kbuild-all@...org, Andrew Morton <akpm@...ux-foundation.org>,
	Linux Memory Management List <linux-mm@...ck.org>,
	kbuild test robot <fengguang.wu@...el.com>
Subject: Re: undefined reference to `printk'

On Sun, 12 Jun 2016 13:38:10 +0900,
Josh Triplett wrote:
> 
> [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?

I have m32r target.
So I can testing and housekeeping.
If I'm not in other ones, I work.

> - Josh Triplett
> --
> To unsubscribe from this list: send the line "unsubscribe linux-arch" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Yoshinori Sato
<ysato@...rs.sourceforge.jp>