From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <owner-linux-mm@kvack.org>
Received: from mail-pf0-f197.google.com (mail-pf0-f197.google.com [209.85.192.197])
	by kanga.kvack.org (Postfix) with ESMTP id 461116B0253
	for <linux-mm@kvack.org>; Mon, 27 Jun 2016 01:26:32 -0400 (EDT)
Received: by mail-pf0-f197.google.com with SMTP id 143so380644023pfx.0
        for <linux-mm@kvack.org>; Sun, 26 Jun 2016 22:26:32 -0700 (PDT)
Received: from mail1.asahi-net.or.jp (mail1.asahi-net.or.jp. [202.224.39.197])
        by mx.google.com with ESMTP id 3si10754465pfg.32.2016.06.26.22.26.31
        for <linux-mm@kvack.org>;
        Sun, 26 Jun 2016 22:26:31 -0700 (PDT)
Date: Mon, 27 Jun 2016 14:26:27 +0900
Message-ID: <87y45ryzgc.wl-ysato@users.sourceforge.jp>
From: Yoshinori Sato <ysato@users.sourceforge.jp>
Subject: Re: undefined reference to `printk'
In-Reply-To: <20160612043810.GA1326@x>
References: <201606121058.3CeznQLn%fengguang.wu@intel.com>
	<20160612043810.GA1326@x>
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-linux-mm@kvack.org
List-ID: <linux-mm.kvack.org>
To: Josh Triplett <josh@joshtriplett.org>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, 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>

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@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

--
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>