From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751860AbcF0F0d (ORCPT ); Mon, 27 Jun 2016 01:26:33 -0400 Received: from mail1.asahi-net.or.jp ([202.224.39.197]:17776 "EHLO mail1.asahi-net.or.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751207AbcF0F0c (ORCPT ); Mon, 27 Jun 2016 01:26:32 -0400 Date: Mon, 27 Jun 2016 14:26:27 +0900 Message-ID: <87y45ryzgc.wl-ysato@users.sourceforge.jp> From: Yoshinori Sato To: Josh Triplett Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, kbuild-all@01.org, Andrew Morton , Linux Memory Management List , kbuild test robot Subject: Re: undefined reference to `printk' In-Reply-To: <20160612043810.GA1326@x> References: <201606121058.3CeznQLn%fengguang.wu@intel.com> <20160612043810.GA1326@x> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/24.5 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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