Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755171Ab2JIJ5E (ORCPT ); Tue, 9 Oct 2012 05:57:04 -0400 Received: from mail-ia0-f174.google.com ([209.85.210.174]:48483 "EHLO mail-ia0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755032Ab2JIJ5D (ORCPT ); Tue, 9 Oct 2012 05:57:03 -0400 MIME-Version: 1.0 X-Originating-IP: [93.172.255.235] In-Reply-To: References: <20121001024544.GA12711@localhost> From: Ohad Ben-Cohen Date: Tue, 9 Oct 2012 11:56:42 +0200 Message-ID: Subject: Re: [remoteproc:for-next 6/9] remoteproc_virtio.c:(.text+0x238e7e): undefined reference to `vring_transport_features' To: Fengguang Wu , =?ISO-8859-1?Q?Sjur_Br=E6ndeland?= Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1180 Lines: 32 Hi Sjur, On Tue, Oct 2, 2012 at 10:24 AM, Ohad Ben-Cohen wrote: > On Mon, Oct 1, 2012 at 4:45 AM, Fengguang Wu wrote: >> Hi Ohad, >> >> FYI, kernel build failed on >> >> tree: git://git.kernel.org/pub/scm/linux/kernel/git/ohad/remoteproc.git for-next >> head: bec109a430e8c67bae1743f7e71898283234a77f >> commit: ec4d02d9180f407c41f8310a13b34e473c671fbb [6/9] remoteproc: Add STE modem driver >> config: i386-randconfig-b102 (attached as .config) >> >> It should be an old bug. The commit happen to be the one to trigger >> the errors because it selects CONFIG_EMOTEPROC. > > Thanks Fengguang. > > This should be fixed by a patch I pushed today to remoteproc's for-next branch. > > Though I wonder, Sjur, do we want to limit the architectures/platforms > where the STE modem driver can be selected on ? Is it ARM only perhaps ? Can you please address the above question ? Thanks, Ohad. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/