Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp973307iob; Fri, 13 May 2022 18:12:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwkE8nalJg3XblhXCctv9nhUoyD6GnNv221Nv2HNBbdJK2sKGg0IngDUYHLJFnZOx8cJC1J X-Received: by 2002:a5d:6d8f:0:b0:20c:7fb7:d59c with SMTP id l15-20020a5d6d8f000000b0020c7fb7d59cmr6203612wrs.77.1652490769532; Fri, 13 May 2022 18:12:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652490769; cv=none; d=google.com; s=arc-20160816; b=GaLqrNAsnLu5q+t2MjcvL+LixQDnWXojnm7KXXAZehrn1bM2ihq6rU2lEsudZV5Z1t BXe+Bmfdt2JUfJiJDrQJ7HLmLaHXR2GjBoJOe7o9KBje6WHXXM+gyFyRYXnl6Xg6NNxG A44uXQYSmFfIm85OVJNVVFNaPa0tZeceR58dav8lWlng6BoyWE7MmE5CnYgPElYWOsUa T9ZhIcnC4Q9+XLtEHNUKDSCrqKqiVeIS5FmU16KPgd2Qeke1JO2OAhMi5qynDe1k4i6n ezwqm1ovZvGeCYhpYMffPzI+ItWZJxALjL+TO9Yvifoxmo7SaZ47DjH6TxS5NdOdmqj0 66YA== 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=LRZET263veJ0K1VCnlC0gP8xVLMOFLk7m3rTvB+obrc=; b=GHUVz+hQZ4i6nA8gD0xq1DTm97h42v4FoLRJzGHYhqOYbQcRE17wUgNIcuiohXRrz7 cWzIqEzyyFySYXQgl8aCMtiXpj/VYm6qiGRno//COHNYemFxDWLvK+cSOnKYdalWnNYI lPOa89ZADvclKL2mtR5FMlLThecxrToRiA9shBgDCYBIeJZ6Bd/zguESCvnX2dIOl28c SXDjYjM7aZSDLHmtJwRZO5rEjtRhLYNvvIiycaUKQcNFIgWnwox3YzLytUkF/vYZdzTu ffcytaxab3+7vB35xGGelz+ZsWR4h9j89zQi9XGj0tD9jbLcYJ4brZxr38RscwGH9Aaa gqDw== ARC-Authentication-Results: i=1; mx.google.com; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id b7-20020adfd1c7000000b00207a2a8e869si4761603wrd.1045.2022.05.13.18.12.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 13 May 2022 18:12:49 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 4A5DE39E7F8; Fri, 13 May 2022 16:43:55 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1376908AbiEMWrW (ORCPT + 99 others); Fri, 13 May 2022 18:47:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58472 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1349751AbiEMWrV (ORCPT ); Fri, 13 May 2022 18:47:21 -0400 Received: from angie.orcam.me.uk (angie.orcam.me.uk [IPv6:2001:4190:8020::34]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 69DCD4839E; Fri, 13 May 2022 15:47:19 -0700 (PDT) Received: by angie.orcam.me.uk (Postfix, from userid 500) id C79E892009C; Sat, 14 May 2022 00:47:18 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by angie.orcam.me.uk (Postfix) with ESMTP id C0C0492009B; Fri, 13 May 2022 23:47:18 +0100 (BST) Date: Fri, 13 May 2022 23:47:18 +0100 (BST) From: "Maciej W. Rozycki" To: Greg KH cc: Stephen Rothwell , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: build warnings after merge of the tty tree In-Reply-To: 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, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RDNS_NONE, SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no 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, Greg KH wrote: > > 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? > > Incremental change as I can't rebase my tree. Thanks for the guidance! Patches now posted, as a small series as the issue turned out more complex than one might have expected, see: . Maciej