From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yoshinori Sato Subject: Re: undefined reference to `printk' Date: Mon, 27 Jun 2016 14:26:27 +0900 Message-ID: <87y45ryzgc.wl-ysato@users.sourceforge.jp> 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 Return-path: In-Reply-To: <20160612043810.GA1326@x> Sender: owner-linux-mm@kvack.org 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 List-Id: linux-arch.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 -- 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: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.asahi-net.or.jp ([202.224.39.197]:35591 "EHLO mail1.asahi-net.or.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751181AbcF0Fr4 (ORCPT ); Mon, 27 Jun 2016 01:47:56 -0400 Date: Mon, 27 Jun 2016 14:26:27 +0900 Message-ID: <87y45ryzgc.wl-ysato@users.sourceforge.jp> From: Yoshinori Sato 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: linux-arch-owner@vger.kernel.org List-ID: 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 Message-ID: <20160627052627.ML_xQ8fEMV0TQBgLcpjs1R5HE5jKQJvEd5rP-_EqnQU@z> 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