Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp4263328ybz; Mon, 20 Apr 2020 19:43:37 -0700 (PDT) X-Google-Smtp-Source: APiQypJ9t86C0La60Xr4Dt3XWKZA9c4PXWCvjgNeC/IQsM25zf8bUU2gNN5LuSh2BFMSKYt3Q7MG X-Received: by 2002:a17:906:4c8e:: with SMTP id q14mr10189670eju.208.1587437017745; Mon, 20 Apr 2020 19:43:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587437017; cv=none; d=google.com; s=arc-20160816; b=Yb4MpOq4pQIDJOev7S47wWAX9YNowBJPso0m3JKF1C6YYezHeDW7mtPd1puO50sTxz nL6468xS79b0AOZfZYOnCt7trh/X6ptf+YGKlKbSVF5mAc/ikY1qh3y8N9UnrGH6XjDd 4GpOS8RJ0aQN/oRayUxuxE9uQR/dV5iCkCTWkaMR/Z8h+QQT0+uQTByxVTqv7OzTnsk5 hs9EPD2Wi1MweU7xtBuBjmZM5Lh3VheYn1roDAiNyEFGR4NIfWBbjR5zhzaNfzwxSzrX Vsi1ekyhmi7CwbMKFb6ER6CNWmkgnIv1gyHnLmVwEpjhH8HLxjgznGAnOoqviV5VlVNq y4tg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=4Ct3Ljnpe9/z1RjWOGjOhNcOu//CgoEvvfkkVmP0fzk=; b=P8T2wJ783Q4I5zPrxHwtduAvmNeuKqLwjVZ2lJOPQBluuxRtpzWSsQYPK0BlBbwEtp zXDUEiOda8EirN14A1kiFA8LMm36B6CFwBng6c/93fLupZ76im5ayWqkHvLPMJLi81TZ HULHpbMpKS+uKkKwrCXASXCqKki4x7HDmdLGCao9hGJBVz8kPJeCeLeXnkE6a06bQUfV ZV05cXTBRw79TiQWrWO5ULAWRMHakDF8utRwrCDypDPgctGxIVhkvIrmbkjAUkxW0Wmd XmbDYbJ67BRCPyQfqmjeuNP7J00ZOyghedsQ/851l3ahXed0BNHUQH3Ts9E2+VPs9vkv RICg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=lVCz0100; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ck10si734199ejb.431.2020.04.20.19.43.14; Mon, 20 Apr 2020 19:43:37 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=lVCz0100; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726885AbgDUCmK (ORCPT + 99 others); Mon, 20 Apr 2020 22:42:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52408 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1726024AbgDUCmJ (ORCPT ); Mon, 20 Apr 2020 22:42:09 -0400 Received: from mail-oi1-x242.google.com (mail-oi1-x242.google.com [IPv6:2607:f8b0:4864:20::242]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 26A0DC061A0E for ; Mon, 20 Apr 2020 19:42:09 -0700 (PDT) Received: by mail-oi1-x242.google.com with SMTP id 8so10818722oiy.6 for ; Mon, 20 Apr 2020 19:42:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4Ct3Ljnpe9/z1RjWOGjOhNcOu//CgoEvvfkkVmP0fzk=; b=lVCz0100nYmTmwntpZfP2eqZmfGoipnm0z2hG5RtkzMEDcqCPVtozANt/fg/Mk2MKY 1BTTVzYKxuUUpalFuwxmy7Jcakf1/n9T89vH5chgo3KODqqgh2gCyZsW5QrWNCpwkgd4 7o3lomkW05BOrZ/l0QIVQ2Tb56mOxDgvNZklK68t01Rpz0pOuV5L/yUs8A7kq/wUc1Y4 K/EDJZ78NY50cURzvmMUgYDiWtF/7Giq86tzqyGYovYI3m0pckshXen0mZ4pc8dLKta8 AkBAG3nVHgAzK2alFWhAq4ha0f/hjkS0n6FITfGUiO4CPd2xD+G+SRCh7TR8l5V5N3I5 rghA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4Ct3Ljnpe9/z1RjWOGjOhNcOu//CgoEvvfkkVmP0fzk=; b=GmQSocX8c8J01mf8saz1TxntIR2djUg7b86DoM0tFq/8cVoQwDOKsXiQjIG9E8Z+WF 6W+XsQHKMrKXHbu9lZRWUDMHfk+USZ+BvonO82/xPZmoSBotlFNAhUqlW7yi71pi44xb V7XwVqiXyQlnNU3syY+CSh+gvgM4gO8w7zWhSzDaRycTFdHLWn6TVnKQ4/1coY0Nsfgc USDsjlYMu+ytHzNNhVF2ki6oP6nshoWR8rgXiB2RTS8WERJEJCUlG2JQIPGBc0qdnxxy yYsF4d1KTHn8oLD1Q4Z88oP1A68ArnV9ozysYAPCQm83dl7JwfEYISW6t/HD9Y9w60ZX 3Fng== X-Gm-Message-State: AGi0Pua5wFKxoT8eMKlIB14cUoWPrzmFNqJgz52hoItDjEJeKd+OYxhs mFlWo+hfpFsBWHd0MNTKyW3TtFOYQxSu5pmmGGZsNg== X-Received: by 2002:a54:4f02:: with SMTP id e2mr1791089oiy.10.1587436928466; Mon, 20 Apr 2020 19:42:08 -0700 (PDT) MIME-Version: 1.0 References: <20200415104152.4d770116@canb.auug.org.au> <20200421092935.21eeb395@canb.auug.org.au> In-Reply-To: <20200421092935.21eeb395@canb.auug.org.au> From: John Stultz Date: Mon, 20 Apr 2020 19:41:56 -0700 Message-ID: Subject: Re: linux-next: build failure after merge of the qcom tree To: Stephen Rothwell Cc: Andy Gross , Linux Next Mailing List , Linux Kernel Mailing List , Stephen Boyd , Bjorn Andersson Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 20, 2020 at 4:29 PM Stephen Rothwell wrote: > > Hi all, > > On Tue, 14 Apr 2020 18:18:11 -0700 John Stultz wrote: > > > > On Tue, Apr 14, 2020 at 5:41 PM Stephen Rothwell wrote: > > > > > > After merging the qcom tree, today's linux-next build (x86_64 > > > allmodconfig) failed like this: > > > > > > drivers/soc/qcom/rpmh-rsc.c: In function '__tcs_buffer_write': > > > drivers/soc/qcom/rpmh-rsc.c:484:3: error: implicit declaration of function 'trace_rpmh_send_msg_rcuidle'; did you mean 'trace_rpmh_send_msg_enabled'? [-Werror=implicit-function-declaration] > > > 484 | trace_rpmh_send_msg_rcuidle(drv, tcs_id, j, msgid, cmd); > > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > | trace_rpmh_send_msg_enabled > > > cc1: some warnings being treated as errors > > > > > > I don't know why this error only started happening today. However > > > reverting commit > > > > > > 1d3c6f86fd3f ("soc: qcom: rpmh: Allow RPMH driver to be loaded as a module") > > > > > > fixes the build, so I have done that for today. > > > > > > Ah. I'm guessing the newly added rpmh-rsc code depends on rpmh being built in. > > > > I'll take a look at it. > > I am still reverting that commit. Yea. I've stirred up some discussion on it, but its fairly complicated. Unfortunately I suspect it will take some time to confirm and justify the change I think is needed, so I think reverting this is the best short term plan. thanks -john