From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756995AbcJUBAY (ORCPT ); Thu, 20 Oct 2016 21:00:24 -0400 Received: from ozlabs.org ([103.22.144.67]:35853 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753335AbcJUBAX (ORCPT ); Thu, 20 Oct 2016 21:00:23 -0400 Date: Fri, 21 Oct 2016 12:00:20 +1100 From: Stephen Rothwell To: Thomas Gleixner Cc: Sudip Mukherjee , linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Marcin Niestroj , Grygorii Strashko , Tony Lindgren , Lee Jones , Mark Brown , kernel-build-reports@lists.linaro.org, linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org Subject: Re: [PATCH] kernel: irq: fix build failure Message-ID: <20161021120020.52b3fa35@canb.auug.org.au> In-Reply-To: References: <1475775403-27207-1-git-send-email-sudipm.mukherjee@gmail.com> <57FBBA0B.9070500@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Thomas, On Thu, 20 Oct 2016 14:55:45 +0200 (CEST) Thomas Gleixner wrote: > > On Mon, 10 Oct 2016, Sudip Mukherjee wrote: > > > On Thursday 06 October 2016 11:06 PM, Sudip Mukherjee wrote: > > > The allmodconfig build of powerpc is failing with the error: > > > ERROR: ".irq_set_parent" [drivers/mfd/tps65217.ko] undefined! > > > > > > export the symbol to fix the failure. > > > > Hi Thomas, > > powerpc and arm allmodconfig builds still fails with the same error. > > Build logs of next-20161010 are at: > > arm at https://travis-ci.org/sudipm-mukherjee/parport/jobs/166321467 > > powerpc at https://travis-ci.org/sudipm-mukherjee/parport/jobs/166321473 > > I know. This is under discussion with the driver folks as we are not going > to blindly export stuff just because someone slapped a irq_set_parent() > into the code w/o knowing why. Do we have any idea if a resolution is close. This was first reported in linux-next in September 14/15. :-( -- Cheers, Stephen Rothwell