Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp6673933iob; Wed, 11 May 2022 02:53:07 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxgEEoigw2YaGXELTi8ZDr94Su5ikYf7j2S5CrsuY92NUt3n0YDaIYHf41r+Y+zlmw+p8WM X-Received: by 2002:a05:6402:5190:b0:427:df4a:19d9 with SMTP id q16-20020a056402519000b00427df4a19d9mr28571105edd.384.1652262786919; Wed, 11 May 2022 02:53:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652262786; cv=none; d=google.com; s=arc-20160816; b=bPIgC6QG/ZdAGzHm6Pfq7dayxbSDm1yGPxXWSqMq5oKyUVjT5CXqUYjO8KR7jC0fsA v8Xk/L/qgQgfAneL+fN52BgV7H8aGUz7i1EZYPayHUmCFBu2GNlFV1+EsJxQZ1HOClwL fgPwfIQM8VRULLgTcPKKsuW81GdPN/QBfcV197GyjD7eJb0RvLPAGXEy3xK6qoSMJHBN tNr1OPzmWaVDyKeCbzdue2OY7k13GkQY+Zr9gS1zWFjY1llB4WlIlDsdttipknjNk/w+ EMCEnhzo2SnAEs3uUpJ1c09Ey8SdMmDJXOR3rYomLgcPT87ihnveiqGVhmRtiLVkN0iH 3bPA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:message-id :in-reply-to:subject:cc:to:from:date; bh=pYmDbaXbMQCZy9C9huY3B+n93m1vN7P05MUwfxj77nE=; b=Uz3nOeGp9Rq0BJpzZ1LV52PXCauatk8JMftwspmXzk/GOtHx2B1dpsLZZZtVyDYX7F b4V/vdUo/Jowd0xmEYSifJ9nfbnWUGq+9AZQu0gAJP83f3BOtX4xPry7NNbeeYNTSQ7q xp8t9SJ/0E/VeQPxcKDP3V+PN6e7WU3FEMx+3Y2yp/ITglBzUqds6PWKJWO8KDoaGH6w c5dFFDMI+lH5cW/EOS4Bf3tFoLccyejj/CFNrZXgoCU822VMNNJ1l8C9mDP+PUpxx1sx k+deqd5nb32amcUJj3RDpCuklUD302o47EHY/lO5+x/nFyMXcMZIO0XS+DmN/F6dH2gf Ytow== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id sc35-20020a1709078a2300b006f4a9fbfa5fsi1539997ejc.1008.2022.05.11.02.52.43; Wed, 11 May 2022 02:53:06 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237339AbiEJWqg (ORCPT + 99 others); Tue, 10 May 2022 18:46:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51588 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237290AbiEJWqb (ORCPT ); Tue, 10 May 2022 18:46:31 -0400 Received: from angie.orcam.me.uk (angie.orcam.me.uk [IPv6:2001:4190:8020::34]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 7E904218FEF; Tue, 10 May 2022 15:46:28 -0700 (PDT) Received: by angie.orcam.me.uk (Postfix, from userid 500) id 1AE3D9200C4; Wed, 11 May 2022 00:46:26 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by angie.orcam.me.uk (Postfix) with ESMTP id 18A549200C1; Tue, 10 May 2022 23:46:26 +0100 (BST) Date: Tue, 10 May 2022 23:46:26 +0100 (BST) From: "Maciej W. Rozycki" To: Stephen Rothwell cc: Greg KH , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: build warnings after merge of the tty tree In-Reply-To: <20220511075804.79c5b697@canb.auug.org.au> Message-ID: References: <20220511075804.79c5b697@canb.auug.org.au> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 11 May 2022, Stephen Rothwell wrote: > After merging the tty tree, yesterday's linux-next build (htmldocs) produced > these warnings: Umm, sorry about that. I wasn't even aware files under Documentation/ are meant to be processed somehow other than through eyeballs nowadays! I'll see how to fix the file up and will make the necessary corrections, but how shall I post the update? A replacement patch or an incremental change? Thanks for letting me know. Maciej