Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E9566C43217 for ; Fri, 12 Nov 2021 02:49:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id BF69060F59 for ; Fri, 12 Nov 2021 02:49:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234554AbhKLCvz (ORCPT ); Thu, 11 Nov 2021 21:51:55 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53672 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234495AbhKLCvw (ORCPT ); Thu, 11 Nov 2021 21:51:52 -0500 Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 692BFC061766 for ; Thu, 11 Nov 2021 18:49:02 -0800 (PST) Received: by mail-lf1-x136.google.com with SMTP id z34so18707146lfu.8 for ; Thu, 11 Nov 2021 18:49:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=dACq+SeisgPOtFcuavxVuy5MhjeTai5DO8RwpVx7m2c=; b=Fx96tFQ2JK6VrO9XjC8jFp7qrJiPRzHXwLrzyvTTPW5moGUkiXCUHVQ7BB67e6+dzX N1uc2L53iG9xqjlu805dgjxtNZ/bHdtonEAOv8TQmkx5YOYeDS6WIkr9LnMJ4NmNywOK qdrtNUkDqYq3XFWyRb/dW2/gEbAO5tROfWAtU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=dACq+SeisgPOtFcuavxVuy5MhjeTai5DO8RwpVx7m2c=; b=p2nYsWdlp0AY6ktr6R7KjSniwhQbEXe5f8nUxGzb3voHBzDS0Mm9gymKhf4jNkhXaR CojaC5rb0oponMEQXFRWruk4Rs/bSbaQVTol0VTyo5hW82vSAEIZngBqljg4Qsv9O0+Z h222km1qKr6m+hnq6Q3VHormJAnJlfrrGYywh8+STwyimbCx09lzQUcXsoaAk7/eM7Ty QimqC9fD6/w3zXu9XXF26PTdV8JDJE8UMeAQIDX10zY078uNghZot/Lycya38Xk98m3l ZT24uDoQKqFpUnqhIiPeuZn1wNRDakDBF2t3ZkoR6pl1YVnpi9ix/mLniCnImUuhIvpe mi9Q== X-Gm-Message-State: AOAM5302dcLmw/+45b4xV9JIsC9BowHx8he56D4f6XoWa1MZcsTQ6cSt WWU665r+F/ECbyZybuelFlcNnd80N0UQnhABbNM= X-Google-Smtp-Source: ABdhPJyqQztphAyyYA9w3PG9m3fBP1qSnxiD9KXcCaUSyxvTOGnD5rYscQLxzdW/q5sn2DShh3AZqw== X-Received: by 2002:a05:6512:b8c:: with SMTP id b12mr10584956lfv.99.1636685340463; Thu, 11 Nov 2021 18:49:00 -0800 (PST) Received: from mail-lf1-f42.google.com (mail-lf1-f42.google.com. [209.85.167.42]) by smtp.gmail.com with ESMTPSA id b17sm422511ljd.68.2021.11.11.18.48.59 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 11 Nov 2021 18:48:59 -0800 (PST) Received: by mail-lf1-f42.google.com with SMTP id b40so18717659lfv.10 for ; Thu, 11 Nov 2021 18:48:59 -0800 (PST) X-Received: by 2002:a05:6512:23a7:: with SMTP id c39mr10942289lfv.655.1636685339562; Thu, 11 Nov 2021 18:48:59 -0800 (PST) MIME-Version: 1.0 References: <20211111163301.1930617-1-kuba@kernel.org> <163667214755.13198.7575893429746378949.pr-tracker-bot@kernel.org> <20211111174654.3d1f83e3@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> In-Reply-To: <20211111174654.3d1f83e3@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> From: Linus Torvalds Date: Thu, 11 Nov 2021 18:48:43 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: 32bit x86 build broken (was: Re: [GIT PULL] Networking for 5.16-rc1) To: Jakub Kicinski Cc: "Rafael J. Wysocki" , Srinivas Pandruvada , David Miller , Netdev , Linux Kernel Mailing List , bpf , NetFilter , linux-can@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 11, 2021 at 5:46 PM Jakub Kicinski wrote: > > Rafael, Srinivas, we're getting 32 bit build failures after pulling back > from Linus today. > > make[1]: *** [/home/nipa/net/Makefile:1850: drivers] Error 2 > make: *** [Makefile:219: __sub-make] Error 2 > ../drivers/thermal/intel/int340x_thermal/processor_thermal_mbox.c: In fun= ction =E2=80=98send_mbox_cmd=E2=80=99: > ../drivers/thermal/intel/int340x_thermal/processor_thermal_mbox.c:79:37: = error: implicit declaration of function =E2=80=98readq=E2=80=99; did you me= an =E2=80=98readl=E2=80=99? [-Werror=3Dimplicit-function-declaration] > 79 | *cmd_resp =3D readq((void __iomem *) (pro= c_priv->mmio_base + MBOX_OFFSET_DATA)); > | ^~~~~ > | readl Gaah. The trivial fix is *probably* just a simple #include to say that a non-atomic readq() is ok done low word first. IOW, just a --- a/drivers/thermal/intel/int340x_thermal/processor_thermal_mbox.c +++ b/drivers/thermal/intel/int340x_thermal/processor_thermal_mbox.c @@ -7,6 +7,7 @@ #include #include #include +#include #include "processor_thermal_device.h" #define MBOX_CMD_WORKLOAD_TYPE_READ 0x0E Of course, it depends on the hardware. It might not matter. Or maybe it really wants the high word read first. Looking at that driver, and how it didn't use to do 64-bit reads at all, I suspect the answer is "doesn't matter". Linus