From mboxrd@z Thu Jan 1 00:00:00 1970 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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D3955C433EF for ; Mon, 21 Mar 2022 16:38:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1351286AbiCUQji (ORCPT ); Mon, 21 Mar 2022 12:39:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58098 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1351276AbiCUQjd (ORCPT ); Mon, 21 Mar 2022 12:39:33 -0400 Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A68CF131 for ; Mon, 21 Mar 2022 09:38:04 -0700 (PDT) Received: by mail-lj1-x22d.google.com with SMTP id 17so5705242ljw.8 for ; Mon, 21 Mar 2022 09:38:04 -0700 (PDT) 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; bh=vLuZZpUnsm9KBxk/6Ba1/rk7zP3V19U4V2RRUcKnlUU=; b=CxLg6iI6FqAS0PFMX63IExeZr6f76g1o7l9nUfGVicC1LNk5HV1MqsTRRe9CQdmMOd L12XNcMd0u/oWXZrvuZ12lN0gUP/uSoxbpWa8i3E3VOJ+CG/6Swp/FYN4Mz3gKef+Fr2 md03VSCIy+BFM1RkCswovuJY4FekLTyETX3P8= 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; bh=vLuZZpUnsm9KBxk/6Ba1/rk7zP3V19U4V2RRUcKnlUU=; b=aqUs8jylTWHKpCWPfmIQp+3jC8psRM6WSAszTe/+D9zvXmyPdZiBireaCYdjeYWY25 5wdWtdkvJlMlFPio2/Zt6XBvzdg1VY4ziglewtYunnv1ViKLXjZK9CXtZuXm3HcVL47N ZJ3bryB5jqK27H56aMALfLs7vojn7sNIurfH9xoDFdXKtiVguIdrtW+XFy3fsDuJBTYY 1lcxZBC9C4CIhBojNg2nCmDcDAEDW0UK4Efjw+f0UyHC0PPX2fGw3F5Mx6stG4Sd22o9 hSX7lNgcaLt+/jg4ia/vKONgSH9TFXXkBeUbSCZ64ChHFllibhyWnYOnxss4CwxUdWGy 4DGw== X-Gm-Message-State: AOAM531CoQpglG5tPn6jYsWgN8MQ8RqxISIQ/RUg+xblrPUYIMN3HG8O B/5MMyS10usXrbQ6C+N/M/4aSzhQVju1FPw+ X-Google-Smtp-Source: ABdhPJy1P0wMXbA8DlMRZNr8b5AO+JCKI4ddTJhroqQYWDWGh4yJRQMROV+bkWWprCy6OiBfLvJ09A== X-Received: by 2002:a05:651c:1501:b0:249:8d28:5659 with SMTP id e1-20020a05651c150100b002498d285659mr884101ljf.138.1647880678606; Mon, 21 Mar 2022 09:37:58 -0700 (PDT) Received: from mail-lf1-f44.google.com (mail-lf1-f44.google.com. [209.85.167.44]) by smtp.gmail.com with ESMTPSA id q21-20020a194315000000b0044a1e36fda4sm775823lfa.25.2022.03.21.09.37.52 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 21 Mar 2022 09:37:55 -0700 (PDT) Received: by mail-lf1-f44.google.com with SMTP id h7so8053069lfl.2 for ; Mon, 21 Mar 2022 09:37:52 -0700 (PDT) X-Received: by 2002:a05:6512:2294:b0:448:6c86:3c78 with SMTP id f20-20020a056512229400b004486c863c78mr14728551lfu.531.1647880671749; Mon, 21 Mar 2022 09:37:51 -0700 (PDT) MIME-Version: 1.0 References: <20220321140327.777f9554@canb.auug.org.au> In-Reply-To: From: Linus Torvalds Date: Mon, 21 Mar 2022 09:37:35 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: linux-next: build warnings after merge of the tip tree To: Peter Zijlstra Cc: Stephen Rothwell , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Linux Kernel Mailing List , Linux Next Mailing List , Masami Hiramatsu , Steven Rostedt , Alexei Starovoitov , "H.J. Lu" , "Edgecombe, Rick P" , Mike Rapoport , linux-toolchains , Andrew Cooper , Nick Desaulniers Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 21, 2022 at 8:46 AM Peter Zijlstra wrote: > > This landing in -next only today (after having been committed last > friday night) is another clue it should probably go next round. I went and looked at lore to get the context that I didn't get in this email that I was added to the participants for. I didn't find the context there either. Sure, I found the thread, but the whole "that x86 patch" that you refer to was never actually specified even in the full thread as far as I can tell. I see that there is an arm64 equivalent too of what you are complaining about, and I have no idea about that one either.. Mind actually giving the full details so that we don't have to go re-do the work you already did? Because right now I know something is wrong, I know the warnings, but I don't actually have any handle on the actual patches to look out for. It's presumably not in any of the pull requests I already have pending, but it would be nice if I saw some details of _what_ you are complaining about, and not just the complaint itself ;) Linus