From mboxrd@z Thu Jan 1 00:00:00 1970 From: gregkh@linuxfoundation.org (Greg KH) Date: Mon, 5 Feb 2018 08:19:06 -0800 Subject: Add patch "arch: define weak abort()" to 4.14-stable tree In-Reply-To: <1517844358.26739.1.camel@synopsys.com> References: <1517844358.26739.1.camel@synopsys.com> List-ID: Message-ID: <20180205161906.GA17767@kroah.com> To: linux-snps-arc@lists.infradead.org On Mon, Feb 05, 2018@03:25:58PM +0000, Evgeniy Didin wrote: > Patch subject: "arch: define weak abort()" > Commit ID: 7c2c11b208be > Reason:? While building mpi.ko module with lastest stable Linux > v4.14.17 an error occured: > >ERROR: "abort" [lib/mpi/mpi.ko] undefined! > Kernel version: 4.14.x What kernel config is causing this build error? I don't see it here, nor have I seen it reported in any other built test. And what kernel version did this break on? thanks, greg k-h From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:51618 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753063AbeBEQTI (ORCPT ); Mon, 5 Feb 2018 11:19:08 -0500 Date: Mon, 5 Feb 2018 08:19:06 -0800 From: Greg KH To: Evgeniy Didin Cc: "stable@vger.kernel.org" , Alexey Brodkin , Vineet Gupta , "linux-snps-arc@lists.infradead.org" Subject: Re: Add patch "arch: define weak abort()" to 4.14-stable tree Message-ID: <20180205161906.GA17767@kroah.com> References: <1517844358.26739.1.camel@synopsys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1517844358.26739.1.camel@synopsys.com> Sender: stable-owner@vger.kernel.org List-ID: On Mon, Feb 05, 2018 at 03:25:58PM +0000, Evgeniy Didin wrote: > Patch subject: "arch: define weak abort()" > Commit ID: 7c2c11b208be > Reason:� While building mpi.ko module with lastest stable Linux > v4.14.17 an error occured: > >ERROR: "abort" [lib/mpi/mpi.ko] undefined! > Kernel version: 4.14.x What kernel config is causing this build error? I don't see it here, nor have I seen it reported in any other built test. And what kernel version did this break on? thanks, greg k-h