Received: by 10.213.65.68 with SMTP id h4csp776332imn; Tue, 27 Mar 2018 08:33:55 -0700 (PDT) X-Google-Smtp-Source: AG47ELsGnPeEZR4TmcAAo43iZWvor1Odb14nfnmQoDgqQJLCMsWjVBPUztrqPREqvoKlm53rRYTR X-Received: by 10.99.140.77 with SMTP id q13mr19004758pgn.44.1522164835039; Tue, 27 Mar 2018 08:33:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522164834; cv=none; d=google.com; s=arc-20160816; b=FE1RNX/8y6m7GWtp7vphy7eSC//iYy7yVZ/frctrVse8MTGaWlbqPayL0jnYBlV31T W3ZbS8A27AwWmDbixRsjgHlhl5iyXelQY0xS43qI4OlyXwBVY3hafZkguCF5/wBTZic/ 9iIz0bqqjxEhFE7zkReh1RPZJh3S1ppuN1Wpr9hLQSuWGMdVk26nx2u+6HKBvLVfev1T lJskUOK7M6LUwJvJ1J6R4iUhVPZb9Nvq8dKTjeMYi8TRPHqajUnjSluVuoNw1+1x91Id CipHChD1opxvxhQhgjJawG8My9rHyEo9ytjzXb9CgyYGGPGbnSsWqsLxbiyrEbdZZC6n uDYA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:to:from:cc:in-reply-to:subject:date:dkim-signature :arc-authentication-results; bh=DwoTfujUAOLWaHe5DCAH9b+3LrlHJKX233wYyPZZ1oE=; b=DFoEL0gfpnOwlqmA7/xS7AvgEsx/FOtRPiSKXPCU9KiKsWZ8UFYFXbhy7eMw8L3h2o 489jARmYtJfvYxsk4o+iSkrhX2EFMeN7tIiNBdtIW4hHYT7774Y1cYaKY1zLxMPSGcg7 UWrbaBtUAHQWzVrvKesKnbTtQp4aPkuJ9KEf8l7KqPrW9OjEJ7TdRaXtgw9JQh9QQ/X5 WnsRHNhaHF/oHkvztbJ4d3cO3QxutXMhQVkq9wwdpLa9kJM+5MS+h6ROT1WLCXLuKL1Z VboZQdoc0p3f1XR0iQZOvt+c7kkym1ftAXxCC9d0qZqjmLdcudxDIl4vqh4KGwpLi6BH QznA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sifive.com header.s=google header.b=Loo85IT+; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f14si1106293pfe.191.2018.03.27.08.33.40; Tue, 27 Mar 2018 08:33:54 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@sifive.com header.s=google header.b=Loo85IT+; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752618AbeC0PbN (ORCPT + 99 others); Tue, 27 Mar 2018 11:31:13 -0400 Received: from mail-pl0-f43.google.com ([209.85.160.43]:40396 "EHLO mail-pl0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752591AbeC0PbM (ORCPT ); Tue, 27 Mar 2018 11:31:12 -0400 Received: by mail-pl0-f43.google.com with SMTP id x4-v6so14295758pln.7 for ; Tue, 27 Mar 2018 08:31:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=date:subject:in-reply-to:cc:from:to:message-id:mime-version :content-transfer-encoding; bh=DwoTfujUAOLWaHe5DCAH9b+3LrlHJKX233wYyPZZ1oE=; b=Loo85IT+j1C+7eWGlfEyPAqDvuAhnJdguVtzmzPygwTaWvGJ2DXFlL8qafRaFnC4vl vKm7m2Pc7XI0JsyTlo3D0l4+5CxhC5TV6e3Z8Li3Krh1VqtFH15A3Xvm0wLH1atydQWM 0+K+kSzhlNx1J7zQhBMWryyIFDttOXYFvH5B+xbfony80MUrkAluMIyVj8UugNnBN0v4 USVPozsCy1xOxmeaJJNkOb4CuqNxYju1SMjOiERHJKQeH93nYkVTRRBo1kgOAjCPBPfI ncllj1qV/7cuIs2vQG/uqMQODJd6I7l5EuebuRtjv7SO4RaAKNOcju2zSv8Gg9mk6hrk mWQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:subject:in-reply-to:cc:from:to:message-id :mime-version:content-transfer-encoding; bh=DwoTfujUAOLWaHe5DCAH9b+3LrlHJKX233wYyPZZ1oE=; b=Gx3TvU/544MxsMcKhKjWTzXdSBO0c715cz25JswXZK7ZoI7NE2BmUvj0Qpo7Y41ny3 dT4JFcj80ntGSlHNB3OVlJra5if0VNy40RJhQ05AJprlZXU/29cO3PV6yTUVw9h64wD4 Z1LoClI0V485tfqrjeIibBPHUPiTZfgvFmJp35UroKyReraE6G8RD0t92WVF5Mu8Lcii 3/HEtrelw2n+OX1F/RBNcsk5PO/sMfs8zb+WIkN4UXaqaKhjnpXABQln5MdALraxed/N 9pqawesWbthGyz1hB4CCZSrms1dYFZPQad04Jv85H4xHyCfjJwzs2LkJRAmarw+vaZKA ucIg== X-Gm-Message-State: AElRT7EhGk6dwWaERoo/JgfwH1EutYJd04xRTvC/Cv0dqNhjclJTcp0f 2+FVgCGrWL5FSMc97A8dZ9kqaw== X-Received: by 2002:a17:902:20ca:: with SMTP id v10-v6mr46662906plg.9.1522164671446; Tue, 27 Mar 2018 08:31:11 -0700 (PDT) Received: from localhost ([12.206.222.5]) by smtp.gmail.com with ESMTPSA id j185sm3309732pgc.79.2018.03.27.08.31.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Mar 2018 08:31:10 -0700 (PDT) Date: Tue, 27 Mar 2018 08:31:10 -0700 (PDT) X-Google-Original-Date: Tue, 27 Mar 2018 08:30:43 PDT (-0700) Subject: Re: [tip:irq/core 12/13] drivers/irqchip/irq-vic.c:295:2: error: implicit declaration of function 'set_handle_irq'; did you mean 'vic_handle_irq'? In-Reply-To: CC: Arnd Bergmann , fengguang.wu@intel.com, kbuild-all@01.org, linux-kernel@vger.kernel.org, tipbuild@zytor.com From: Palmer Dabbelt To: tglx@linutronix.de Message-ID: Mime-Version: 1.0 (MHng) Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 26 Mar 2018 22:27:36 PDT (-0700), tglx@linutronix.de wrote: > On Mon, 26 Mar 2018, Palmer Dabbelt wrote: >> On Mon, 26 Mar 2018 01:07:54 PDT (-0700), Arnd Bergmann wrote: >> > On Tue, Mar 20, 2018 at 6:52 PM, Palmer Dabbelt wrote: >> > > On Tue, 20 Mar 2018 00:53:21 PDT (-0700), tglx@linutronix.de wrote: >> > > > >> > > > On Tue, 20 Mar 2018, kbuild test robot wrote: >> > > > >> > > > > Hi Palmer, >> > > > > >> > > > > FYI, the error/warning still remains. >> > > > >> > > > >> > > > Zapped the commit as well... >> > > >> > > >> > > Sorry, I got the flu at ELC and have been offline for a bit. It looks >> > > like >> > > you've kept the IRQ and RISC-V patches, I'll fix up the others are >> > > re-submit >> > > them as a separate patch set. >> > >> > Not sure which patches are in flight at the moment. To get a clean build >> > on arm32 and arm64 randconfig kernels, I needed the fixup below >> > on top of linux-next (not meant to be applied like this, just for >> > reference). >> >> Thanks, I missed these during my original patch submission. I think the >> cleanest way to submit this is to spin a whole new patch set, including those >> that are already in tip. Would it be possible to just remove my IRQ cleanups >> from tip so I can try again? > > The commits in tip right now are: > > cc6c98485f8e ("RISC-V: Move to the new GENERIC_IRQ_MULTI_HANDLER handler") > caacdbf4aa56 ("genirq: Add CONFIG_GENERIC_IRQ_MULTI_HANDLER") > > I surely can revert them, but I don't see how they would break arm or > anything else. If GENERIC_IRQ_MULTI_HANDLER is set via randconfig then set_handle_irq() is pulled in from the generic code, which conflicts with the definitions in arm, arm64, and openrisc. The RISC-V commit depends on the genirq one.